I somewhat agree with the petition: we need a Maker plan with APIs. You can’t create good apps that aren’t connected. They could create a new plan that includes the benefits of Maker and the use of APIs; that would be great. I hope more people join this petition.
2 Likes
I totally agreed that Maker plan can help this. Anyway, if I would like to calculate the distance from any new customer locations to current location of taxi drivers. How to handle this?
I tried to use single value from new customer location to driver location to calculate the distant. But there are so many new customers coming. How to solve this?
If you use Radar’s “Track once”, how do you store the live location of each driver (I assume it only writes the location once), to be able to do the distance calculation thing?
I can put only the current location in user table by push current location button. Are there any better solutions?
I would like to get the lastest location when they deliver customer and get that location data back.
So every time a driver delivers, you can have a button to trigger writing the location through Radar to a field in the Users table for drivers, let’s call it “Last coordinates”.
Assuming you store users in the same table, you can have a distance column, from the user’s location to that “Last coordinates”. Does it work?
To get the lastest location is ok. But I face bigger problem from calculating bulk of new coming customers simulateously. How to solve this problem?
The distance column would only calculate based on the signed-in user’s location, so that information lives on the user’s device. You don’t need to worry about multiple users calculating at the same time.
Awesome. Thank you.
1 Like
Just following up on this to see if any Glide folks have some insight about the future of custom domains in the Explorer plan. I put together a quick comparison of the plan I’m on, versus the Explorer plan versus the Maker plan, and while I would be giving up quite a few features with higher limits if I were to switch to Explorer (number of published apps decreases, as do the number of editors I can share my app with), the remaining features and function are negligible for my specific use case (more rows, more storage, etc.). The same goes for the Maker plan.
Obviously, I can’t speak for anyone else who is in a position similar to mine, but hopefully someone can help clarify a question for me (and potentially anyone else who is curious): the ability to utilize a custom domain is included in the legacy Starter plan, which costs $25 a month. It is NOT included in the Explorer plan - which costs the same - and the only way to keep using my custom domain if I want to switch from my current plan is to bypass the Explorer plan entirely and upgrade to the Maker plan, for $50 a month. This isn’t a financially responsible decision for me to make just so that I can manipulate the CSS in my app (which I want) and continue using my custom domain (which I need). Have there been discussions about possibly revisiting a Custom Whitelabeling fee like there used to be way back when? Or perhaps, even better, adding custom domains to the Explorer plan so that they are included in the regular charge?
2 Likes
Looks like a solid option for small teams or solo devs. Nice to see more flexible pricing!
1 Like
looks like you are trying to introduce a new pricing plan to your users, but it seems like you forgot to include the actual features of the Explorer plan. the text just mentions that it makes powerful features more accessible, but does not specify what those features are or how they differ from the free plan. give that a try.
You can find all the features of the Explorer plan on Glide’s pricing page.
One notable difference between the Free plan and all other paid plans: on the free plan you can create as many drafts as you like but you cannot publish your projects.
2 Likes
This is still a bad move, especially for schools and groups.
Existing apps are fine, but free users can’t publish new ones anymore. That messes up a lot of real-world uses—think classes, workshops, clubs, and training where people constantly need to make and share new apps.
For teachers, this means their lesson plans and how they usually do things just won’t work. You can’t teach the same class next semester, get new students set up right, or let folks build and publish their own stuff without them immediately hitting a paywall.
Even though they didn’t take anything away, the way people used to work completely changed overnight. Stuff like this should come with clear warnings and special thought for education, because it totally changes how Glide works for learning and community groups.
It makes it tougher to suggest Glide for classes and beginner programs, which is a bummer since it’s otherwise a really good fit for that space.
1 Like