Deprecation of Classic Apps begins Monday, June 30th ⚠️

Announcements
1

Classic Apps will be fully deprecated on Monday, June 30th.

Classic Apps will no longer be accessible or editable once deprecated.

This follows the discontinued support for Classic Apps we announced two years ago (March 2023), when we recommended switching to New Glide Apps for all builds.

Use the migration tool to safely recreate your app as a New Glide App.

You can read more about how to use the tool and FAQs in our Glide doc:

If you do not migrate your Classic App by June 30th, it will be automatically migrated for you.

Once migrated, links to your Classic App will redirect to your New Glide App.

If you no longer use your Classic Apps, you can safely delete them from your team.

Questions? Comments? Please leave them in this thread.

4 Likes
5

Yikes. I have some work ahead of me this summer.

1 Like
6

Have you tried the new migration tool?

7

Yeah, this is NOT going to be fun! Just a 3 month countdown and much work to do for our single long term production legacy app. We found the conversion tool did not work for us, so this is going to be a complete rebuild. :face_with_crossed_out_eyes:

8

Yes. It works okay for a couple simple apps, but not for a few of my large complex apps that depend on:

  1. Card/Tiles Inline Lists that have all the tags/overlays/etc.
  2. CSS via Rich Text components (I know this was never supported).

At least it’s in the summer when I’ll have more free time to rebuild.

1 Like
10

Is this april fools? :rofl::rofl::rofl:

2 Likes
11

Yes the migration tool works really well but when the app is complex there is still work to be done by checking every aspect of the app.

2 Likes
12

After a further review of the Glide migration tool today, our larger “Legacy” app did in fact migrate over to the new apps platform with “most” of the elements intact. Our earlier attempts were unsuccessful but it appears that Glide has in fact made the tool better.

Now instead of rebuilding from scratch, we can simply clean up areas that were impacted by Classic Only features. Thank you Glide for the nudge to take another look at the migration tool. We don’t think this is going to be as bad as originally anticipated and our clients will certainly appreciate the new version of their app once rolled out. :grin:

7 Likes
13

That’s great to hear!

1 Like
15

This will be a good opportunity to tidy up the clutter, reduce digital waste and when needed try the new migration tool. I’m kind of excited!

1 Like
16

Aug 31 would be a better date. Just sayin’

17

Because you need more time? Have you tried our new migration tool yet?

18

Here is a question that I should know the answer to but am just not sure so seeking opinion and thought from our Glide Expert community…

  1. We have a published Classic App with about 300 Users. This classic app has its OWN CUSTOM domain (not using the Glide URL).

  2. We have successfully migrated the build of this Classic app over to a New Glide app. Nicely done Glide Team!

  3. We want to roll out the new version of the app with the LEAST possible negative impact to this existing User base.

What might be the best way to do this so the existing User base fires up the NEW app vs. the Old one? Keep in mind that these Users have already downloaded the OLD app to their phones so it’s NOT simply having them access the re-mapped URL in their browsers to load in the new instance of the Glide app.

Will ALL of these Users need to access the SAME Custom URL once the New version of the app is mapped to the existing domain URL and then RE-DOWNLOAD the new app to their phones OR will the new app fire up if they click on the OLD downloaded app icon on their devices?

Anyone done a migration and re-rollout like this? Advice much appreciated! Thanks! :smiling_face_with_three_hearts:

19

I can’t say this with 100% confidence as I haven’t tried it myself, but an “installed” app isn’t much more that a glorified bookmark that opens a shell of the browser and loads the website url in that browser shell. I would assume that remapping your custom domain would be all that needs to be done and for users that have the app “installed”, it will just load the new version of the app.

I think what gets “installed” is pretty basic as most of the content and UI for the app is downloaded dynamically. The install mostly contains the app icon and the url for the app. Worst case, the app icon may not change.

I’m sure someone has actually gone through this already to confirm or not.

5 Likes
20

This is correct. If you remove the custom domain from the Classic App and set it up for the New Glide App, the users should open the New Glide App when they click the app tile on their devices. As Jeff pointed out, your device is simply storing a bookmark (i.e., URL).

4 Likes
21

Oh this is awesome then. Yes, we do have a slightly updated icon but if that does not update that will be okay. We just wanted to make sure that the existing icon DID NOT break leaving those users without the app instance or a path to the new version. Thank you for confirming this for us! :smiling_face_with_three_hearts:

3 Likes
22

I believe those users with the app already installed will keep the “old” icon (they would have to install the app anew for the old icon to be replaced by the updated one), whereas new users who perform a fresh install of the app will be seeing the updated icon.

1 Like
23

Yes, I have. And it works pretty much as others have described. Worst case, some users may find they have to load the App a couple of times.

1 Like