Iām a new Glide user and very interested in the new Apps features! When I create an app, however, it seems to have all the old āPagesā functionality. I see everything how it is in the āGlide Pagesā section of this help doc page: Adding, Editing, and Forms
Any ideas? Iāve logged out, cleared site data etc., but I seem to be stuck on āPagesā 
CSS have never been officially supported, so that is a risk you always have to take into account. Iām not sure if Classic Apps will ever lose that, though, it still exists as a ālegacyā product, but from now on focus should be solely on new Glide Apps.
I think that might be the case, but Andy knows better.
Itās Glide Pages that is renamed to Glide Apps. The old āGlide Appsā is now called āClassic Appsā.
Yes, I understand. When I create a new app I donāt see the new āAppā functionality, I see the old āPagesā functionality. I cannot access the new functionality.
What specifically are you expecting to see?
As an example from the āAdding, Editing, and Formsā help doc, I expect to see an āAdd Formsā tab in a List Screenās configuration pane, and āEdit Formā tab in a Details Screenās configuration pane.
Instead I see the interfaces as described lower on the page, in the āGlide Pagesā section.
This suggests to me that Iām seeing the older āPagesā experience, and not the newer āAppsā experience.
Css is a standard in the real world and seeing that :
1.Its being phased out or is about while it needed to be established from free to Gotha plansā¦;
2.Its only in the 2 hundreds and half plan?..
i feel with mixed feelings here.
We can say all and they have all the rights but we all know that shouldnāt be like this.
For me , seeing that even Classic Apps is happening and Pages are becoming App makes only a great confusion and doesnāt make me feel stable while developing , not forgetting that while Glide is a great mental exercise we cannot export any code and i really donāt want to hurt anyone here that i profoundly respect but not giving any API to the Starter plan while is common practice all everywhere on Product Hunt even in the free plans , no CSS makes me really perplexed and this while AI is exploding and giving out knowledge to people for coding by their own in a way we can only define as Revolutionary ā¦while i know that to withstand a real world application you need a great Infrastructure , we are in the SAAS,IAAS,PAAS world after all.So thanks all for the replies, last , the chatbot Glide uses OpenAI so they are aware about it, lets see if NEW APPS bring back some old good classic such as CSS for common people, or at least finally a proper Builder editor in order to customize our Frontend finally because its about time.I really hope so, Glide as a start is great and with 2 API would a perfect starting Crud for React,Vue,Solid ( the .jsx family ) and Flutter.
Yes I can see that but it has no bearing on my current Classic Appā¦ There is no option for me to add any of the integrations to this app.
Is it possible to downgrade back to the Grandfathered Pro Plan? Moving my app over to a new team has been a big cost that I simply cannot justify right now.
Integrations are not available for Classic Apps. In fact none of the new features will be made available for Classic Apps, as they will eventually be phased out. To take advantage of integrations and other new features you will need to migrate your Classic App to the new (Pages) App.
No, I donāt believe there is any option to do that.
Is there a safe way to migrate my Classic App to Pages without messing it up? My app is currently live and I donāt want my users to be negatively impacted
There is no direct migration method available yet, so the best way at the moment is to use the āNew App from dataā option. This will create a new version that includes all of your computed columns. Youāll then need to build out the user interface, and once done you can replace your old Classic App with the new version.
If I do this, will the data remain in my Classic App or will it just move over to the new app?
Your data will remain where it is.
When you create the copy, you will have a choice between āCopy Sheetā and āKeep Existing Sheetā.
Have a read below to understand the options.
I think you are confused by the very recent change to the new naming convention. What you are seeing at the top of the document is the OLD Classic Apps (formerly called Apps). At the bottom of the document is the NEWER Apps (formerly called Pages). It looks like the documentation hasnāt fully been updated to reflect the name change yet, but anything you see regarding Pages IS the new experience going forward.
Classic Apps (formerly called Apps) are being phased out in favor of Apps (formerly called Pages), and someday the documentation will be updated to reflect that there is only one product.
If you created your Glide account prior to March 23rd, then you would still have the ability create a Classic App. If you created your account after March 23rd, then you do not have the ability to create a Classic Apps. Even is you can create Classic Apps, itās recommended to create Apps (formerly Pages) going forward and Classic Apps will eventually be converted to Apps.
Trust me, you want this as Pages (now called Apps) is the only product receiving updates and getting new features going forward. Classic Apps are going away.
With that said, the concept of adding, editing, and forms is similar in both products. There might be subtle differences, but you can manipulate data the same in Apps as you could in Classic Apps. Now if you are having a specific issue figuring how to do something in Apps, you are welcome to start a new thread to ask for any help specific to your project.
ahhhahaha okay yeah, that makes sense. documentation is all over the place but thatās to be expected to some extent (if far from ideal)
The feature Iām missing that is now exclusive (it seems) to āGlide Classic Appsā is the default inline edit mode ā it looks like in those apps you could turn on an edit button in the top-right corner of a details view; tapping that would replace the view with a similar-looking edit screen. In the new āGlide Appsā I have to create an action button that lives somewhere on the page, not in the corner, and the edit view is a form in a modal drawer that doesnāt look like the details view. There also isnāt a floating button option in āGlide Appsā.
It also seems that (some? all?) videos in āGlide Universityā were made using the old āGlide Classic Appsā system, which threw me off even more. It seems like a lot of that info is now inaccurate
That said, expectations successfully reset, thanks so much for your time!
Classic Apps had screen styles that could be List Only. What this means is that you could have a list on the screen but no other components. Because of that, it did make more sense to have an Add button at the top right of the screen because that Add button could only pertain to the single list. With the new Apps, there is no such thing as a List Only screen. All screens are detail screens, so you could have multiple lists mixed with multiple other components.
As for the Edit button, that pertains to the current detail screen, so you can edit only the row you are viewing.
I would argue that the new way is a lot more flexible in many ways, but that is my own personal opinion. Within each individual collection on the screen, you can enable an Add button, or you can enable edit buttons directly on each item.
If you are viewing the details for an item, you have some options including using an Action Row component to display an Edit button, or adding actions to various components.
Itās not exactly in the corner, but you also have to consider how it will look on a larger screen as well.
You just need to be willing to think outside the box a little bit and play with your options. You may not get exactly what you want, but I think you can usually get something that works just as well and in some cases might be better in the long run.
You will always have to design Add screens, Edit Screens, and Forms independently. They will not automatically follow your design of a Detail screen.
This is coming. Itās on Glideās immediate roadmap.
The Glide Docs team is working hard. It takes time to reshoot and edit new videos on a platform that is ever changing. There is a lot of material for them to relearn as well. Yes, I understand itās confusing, but itās a transition process. Itās only been a week since they officially locked down Classic Apps and officially changed the names of the products. Before that, itās been a few months of transition and I foresee it continuing into next year before everything is 100% Apps.
Confusing time to be a new user Iām sure.
amazing, thanks again for your efforts here. I feel much more comfortable with Glide now!
Hiā¦ itās already April, is there any update for āHorizontalā ?
Thatās sounds very bad, especially with the current limitations (buttons, no floating buttons, limited graphical options for place object, missing elements in lists compared to the previous version) ā¦ and I used also the content=āā option to translate default buttons in different languages.
Iām looking forward to this feature.
For your Buttons you can translate it with scripts even in page. And for graphical option you have supported CSS in page with a Business account (Not supported with classic apps)
