Can I create a dashboard via Glide?

Ask for Help
1

Hi everyone,

I’m exploring the possibility of using Glide to create a dashboard and wanted to check if it’s the right tool for my needs.

Here’s a quick overview of what I’m looking to build:

A portal for landlords and tenants
It should have two separate dashboard interfaces:

  • One for landlords
  • One for tenants

Would Glide be suitable for this use case? Any guidance or suggestions would be greatly appreciated!

2

When it comes to functionality, flexibility, speed of development, I think Glide is a wonderful platform to build real estate or property management apps.

How many users do you have in mind? Are you building this for yourself, a small company, a big company or as a SaaS solution? Have a look at Glide’s pricing page and see if your project, your budget and Glide’s pricing are aligned.

Overall though, Glide is perfectly suited to your project.

2 Likes
3

Thank you for your feedback.
I am currently wanting to build a prototype. The users would be around 5,000-8,000 maximum for now.

Which plan do you suggest I take?

4

At 5-8k users, I see 2 options:

  1. A public-facing application on the Maker plan. Users would be limited to using personal email addresses only. This would not be suitable for a business setting due to the constraint on email addresses.
  2. A business portal on the Entreprise plan. You could contact Glide’s sales team to discuss pricing.
5

Alright, got it,
And like I mentioned earlier, I would have to create 2 interfaces - one for landlords and another for tenants.

Would I be able to do that through the maker plan?

I would like to use the maker plan for now as I am just making a prototype. I can go on with an upgraded version once I test my prototype in the market.

6

You could build two separate applications (separate interfaces) syncing to the same tables. This is powerful because you can work with a single source of truth for your data and build multiple interfaces on top.

Or you could build one single application (one single interface) and define roles within the application which would drive what data is downloaded to devices (for security) and what is displayed on screen (for personalization).

I don’t really have an opinion on which path to pursue, I suppose it depends on how different the two interfaces would be. If the apps are totally different, I think you could build two separate apps. If the apps are similar enough and have a lot in common with only a few screens or components specific to a role, then I think you could build a single interface with roles. Personally I find roles a little tricky to work with, they are set at the row and column level and I find it easy to get confused.

The Maker plan is ideal for prototyping, sound choice.

1 Like