New Old Glide

Just a curious thought I had. We had a moment in time when we had to check all our (classic) Apps to make sure they still ‘worked’, especially as regards CSS implementation, because the (classic) Apps were going to inherit, or be moved to a ‘new computational model’; ie. the one that (new) Apps (pages) uses. That being the case, why is it so difficult to get features that were in the (classic) Apps, but are now employing the “new computational model” that the (new) Apps uses, implemented?

In other words, if it is in the (new) (classic) Apps, shouldn’t it be relatively easy to move the feature to the (new) Apps? The background code is the same, right? Well, that’s what we were told, at any rate. It seems to me it would be a trite thing to apply features from the (new) (Classic) Apps to the (pages) Apps since they use the same backend.

Well, that was just a thought I had. I am a coder, so sometimes adapting to no-code ways is difficult for me. If I need a new feature, i simply add it myself. Not used to begging. Weird being on the other side of the fence…

1 Like

There is a big difference in features for classic and new apps… containers!
also, monetizing system and updates count…
at the end… when nobody knows what and why… is the money! :crazy_face:

Yes I’m not talking about new features in the new apps. I’m talking about features in the classic apps being moved over to the new apps. Since it’s the same backend it should be relatively easy to do that, right?

I assume you’ve read the below article, yes?

Why would Glide continue to add features to a product they intend to sunset? Especially when they’ve already signalled their intent. Any effort they spend on adding features to Classic Apps now would ultimately be wasted effort, no matter how small.

As an active user and somebody that builds Apps for others, that’s certainly not something I would want to see them doing. I would much rather see them focussing 100% of their efforts on extending and improving the flagship product.

1 Like

You completely missed my point. I’m not talking about adding features to classic apps. I’m talking about features that exist in classic apps. That should be relatively easy to move to the new Apps, that is considering if they both use the same backend. And making it easy to move from a classic app to a new app. It’s fine for apps that are 1 or 2 tabs. My main app is a very complex one and I would love to see how they intend to migrate it. Waiting till the end of the year for the migration feature is very painful. Seems to me that should be the number one priority being as most of their templates are apps. And presumably most of the apps in the field are classic. Kind reminds me of the old car commercials. Chrysler was the big car expert. They spent years becoming the big car expert according to their commercials. Then the fuel embargo came. And they said we have become the small car expert overnight. And nobody believed them. But now i’m showing my age.

1 Like

Oh, my apologies. Yes, I did misunderstand. I thought you were suggesting back-porting new features to Classic Apps.

Okay, so to talk to your actual point - providing legacy Classic Features in new Apps.

Glide have addressed this, and in fact it’s covered as an FAQ point in the article that I linked to:

The above is probably a little out of date now. There was a big push for the past few months where we saw many of those components drop. I know that’s slowed down a bit now, as I believe they are trying to balance porting features/components from Classic Apps with adding new features and integrations, etc.

But as far as I’m aware, we can still expect to see pretty much everything ported over - except those items explicitly listed.

1 Like

While Classic and New Apps do use the same backend…the front end is quite different. The front end for components need to be rebuilt to work with a new set of stylesheets, as well as scale to a wider range of screen resolutions, and adapt to a new set rules for how they flow on the screen. I think it’s a lot more that just copying and pasting some code. It’s a new frontend redesign of each component.


If “link relations” refers to link lists, I use those all over the place. What a pity. Never had much use for payment buttons, as I built my own. But the biggest issue I have right now is that for every single thing that people ask how to do, someone comes along with CSS. That’s not no-code or even low-code. Should not be that hard. If I have to learn a programming language, I would look for something a little more powerful, and one that doesn’t tie me to a platform. Make it easy, like it used to be.

How would I build something like this (from Classic App) in the new App model?
Note that when I select it, I get a list of editable items:

That looks like a List Relation component, yes?

That’s one that hasn’t made it into the new Apps. Not sure if it’s planned, but I suspect not. But I think you could simulate a similar flow with a collection easily enough. Perhaps start with a Collection and limit it to 1 item, and then use a Title Bar action for the “See more” part.

Something like this, for example: