# Saying Goodbye to Glide

**URL:** <https://community.glideapps.com/t/saying-goodbye-to-glide/85597>\
**Category:** General\
**Created:** [November 29, 2025, 9:52pm UTC](https://community.glideapps.com/t/saying-goodbye-to-glide/85597 "2025-11-29T21:52:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lemusa](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lemusa/32/92080_2.png) [@Lemusa](https://community.glideapps.com/u/Lemusa)\
**Post date:** [November 29, 2025, 9:52pm UTC](https://community.glideapps.com/t/saying-goodbye-to-glide/85597/1 "2025-11-29T21:52:39Z")

</div>

First of all, this is intended to be constructive. I figured my experience might be useful to others, and maybe give Glide something to think about when it comes to retaining users like me.

I get that Glide is primarily aimed at organisations building internal tools. For that purpose it’s a solid platform. But it also has real potential for people trying to build and monetise public-facing apps.

I built a roster/pay calculator on Glide. The learning curve was pretty manageable – I came in with a strong spreadsheet background, some HTML/CSS, and only a touch of JavaScript. The platform is intuitive enough, and there’s plenty of material online to get started.

Key features of my app were:  
• User profiles with their role, scale etc  
• Users enter their rostered shifts by fortnight or within a monthly calendar  
• They pick the pay fortnight they want  
• The pay page calculates gross, deductions, net, and penalty breakdowns  
• A subscription layer (via PayHere/Stripe) to unlock features (primarily, more than one fortnight of shifts)

Functionally, Glide handled all of that really well. Load times were good, and even with some table limitations I could get the layout looking how I wanted.

Where things got difficult was administration. Not having a true admin view – especially the ability to export all user-specific data – made troubleshooting far more painful than it needed to be.

My main blockers were:

1. Price – $60/month isn’t ideal for a small/startup app.
2. Row limits – never hit them, but had to design around them from day one.
3. Custom domains – should really be available on every paid tier.
4. No built-in testing branches or maintenance mode.

After mulling it over, I started looking at alternatives. Eventually I ended up doing it the hard way – rebuilding everything in React with Supabase on the back end and Vercel hosting. With a lot of help from AI, I got it done in about two months of evenings. The end result performs better, looks cleaner, and right now costs me nothing to host ~250 users. As the app grows, the hosting costs will grow with it, which feels far more reasonable.

My takeaway is this: if I hadn’t built the first version on Glide, I never would have attempted a full-stack build. Glide taught me the logic and helped me shape the idea, but the limitations eventually pushed me to outgrow it.

So genuinely — thanks for the start, and goodbye 🙂

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [November 30, 2025, 6:56pm UTC](https://community.glideapps.com/t/saying-goodbye-to-glide/85597/2 "2025-11-30T18:56:27Z")

</div>

Best of luck with your endeavor! Happy to have had you in the community!

---

<div class="post-metadata">

**Author:** ![UseSoft](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/usesoft/32/92490_2.png) [@UseSoft](https://community.glideapps.com/u/UseSoft)\
**Post date:** [December 1, 2025, 10:53am UTC](https://community.glideapps.com/t/saying-goodbye-to-glide/85597/3 "2025-12-01T10:53:09Z")

</div>

Oh.. you went the right way. Full-stack is the best right now, especially with AI help, you can build unlimited apps for free or just a little spending for a great servers below $5/month.

---

<div class="post-metadata">

**Author:** ![Myles\_Chaput](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/myles_chaput/32/62176_2.png) [@Myles\_Chaput](https://community.glideapps.com/u/Myles_Chaput)\
**Post date:** [December 3, 2025, 9:30pm UTC](https://community.glideapps.com/t/saying-goodbye-to-glide/85597/4 "2025-12-03T21:30:57Z")

</div>

there are limitations for some of us low coders using full stack, I love how Glide is a UI that I can edit, and the backend I can feed it information, its certainly pricey, which is why it has a specific use case. I just tried to build a similar app with Replit, and the Replit AI prompt charges to build a somewhat usable interface, were priced astronimcally! I spend $100 worth of engineering, and have little to show for it usefulness wise…. Glide still has a place in my heart.
