Thoughts on Glide

As they say on social media, “All you had to do is disappear and we’d never think of you again!” Well, yes, I could have. But I wanted to take a moment and share some thoughts I have had over the last 14 months.

I just canceled my Legacy Non-Profit Plan. I have a dozen or so Apps on free plans that I will continue to develop and maintain until it is no longer feasible. They consume so few resources that I am hopeful.

I also have half a dozen Classic Apps on free plans that “are no longer supported”, and some features in them have begun to be non-functional. So those will probably have to be abandoned.

On the new Apps, there are features that don’t work right on mobile, but work correctly in the builder.

I have my main Classic App, which until today was run on the Legacy Non-Profit, but henceforth will run on a free team until I can find an alternate solution. I have waited for at least a year and a half for a promised, “we will have a tool to port your classic app to the new apps format; just be patient”. Then there was the note (from an exert user) that doubted it would happen. Every time I have pushed, I would get a note in the forum from an actual Glide person stating, “Well, it will happen, but if you need it now, get to porting:.”

Even an 80% port to the new App format would have been acceptable to me, to get me going, as many of the screens operated in the same way; and to be honest, have no special features or experimental code.

Even on the other front – “feature requests” – I see so many feature requests with votes and ++++11111, even coming from experts, that are completely ignored by Glide “because it doesn’t fit with our business model”.

“Why don’t you report the bugs to Glide?” Well, long story short, I spent most of my career advancing the development of a language that was quite popular in its heyday, and I often pushed the limits of that language and often felt that I was a beta-tester rather than a developer. I did not want to get in that situation with Glide, especially seeing the slow response to things that really matter to me.

During my time in this community, I feel I have made a positive impact, and I truly enjoy developing with Glide. I know management says they have not switched gears, “Look at our original business statement”, but based on the templates available, the tutorials galore, and the Showcase Apps, etc., it did seem that Glide was a good fit for me, and those tracks have certainly changed.

So I am not leaving the community, but I have to set my eyes on the future and so I will be a lot less active here. The one development product that could possibly replace Glide for my main app (Appgyver), is a much bigger learning curve, which is why I went with Glide to begin with – although it is also more powerful than Glide. But I’ve never been afraid of learning, so I shall do a deep dive into Appgyver very soon.

Thankful for the friendships I’ve made here, and good luck to you all!

David Gabler

3 Likes

THIS.

1 Like

Hey @David_Gabler. This tool just got released today :smiley:

Hope this works for you and you reconsider your decision :smiley:

1 Like

@David_Gabler

I do agree that Glide has changed as they try to find their footing in the market. I also agree that their often shifting pricing and commitments can seem arbitrary but when you are a unique product that appeals to a wide variety of users/builders it is always hard to find the right value proposition.

Glide has always been a small team DELIVERING big things. I believe they were less than a dozen folks back in 2022 when they were delivering amazing capabilities. And moving from a Classic App builder to a full blown web development solution was like changing the tires of car while driving 80 MPH down the highway. Opening up a new market while satisfying existing users (mostly :slight_smile: ). Truly remarkable.

I reviewed tools every 6 months given my early frustrations with Glide and their changing ‘model’/capability…but in the end they continuously deliver value (I remember May 2023 whey Query came out!) overriding the frustration of things like forced migration from Classic Apps (which I did) and moving to Big Tables (which should have been turn-key from the beginning).

The only tool I see matching Glide in the near future is AI - (Replit, Bolt.New, Cursor) and I am confident @david and team will innovate with AI.

Good luck David - it was always good reading when you posted. I will be interesting to see how Appgyver matches Glide and I hope you post on your progress.

Matthew

3 Likes

Beat me to it :sweat_smile:

2 Likes

Hahaha I read this post just MOMENTS before Brett announced about the tool on Slack.

That’s very well said, Sir! I didn’t realize Query was rolled out that long ago.

1 Like

The Query column was basically the result of a weekend hackathon that Mark & Jason had. Remember when Mark posted the video demonstrating it? Probably one of the biggest game changing features we’ve ever had. Every now and then I find myself in an old App that was built before we had the Query column - riddled with templated relations :man_facepalming:

3 Likes

Can we crowdfund another weekend hackathon? :laughing:

2 Likes

Thanks. Weird that it would be released the same day I put the hammer down (which I had been contemplating for three months).

It (the tool) does work very well to convert all my simple Classic Apps (fewer than five screens/functions).

The BIGGEST reason it did not work for my main Classic App (the reason I got involved in App Dev. to begin with), is the lack of floating buttons, and it expanded literally ALL my lists to be the full detail, instead of the short abbreviations, and then click for detail.

Pretty sure this can be tweaked, but with all the other things, and the fact I’ve already cancelled my legacy and they probably won’t let me re-start it, I’ll just continue on down the road with something else. I cannot go from paying $25/mo for an App used by a dozen people to $60/mo for the same App (I am the one paying for it as a non-profit).

Glide will continue to be useful to me for my free Apps, which are all used for just myself and immediate family. And at least now they will all be new Apps instead of Classic Apps (with the exception of this main App, of course)

Here is an example (Classic):

New App:

It was mentioned in the expert slack about a week or so ago, but the day of your post was the first day that I had actually seen it pushed out to preview.

This can be addressed with a Truncate Text column. That’s neither here nor there now, but just mentioning for anybody else that may be running into this in the future.

2 Likes

Yes, I am aware of that, and I do that in my new Apps, but never had to do it in a Classic App, and this App would require more than fifty new columns to address them all.

Yes, I have “slacked off” on checking the expert slack in the last few months.