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

**URL:** <https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082>\
**Category:** Archived Announcements\
**Created:** [March 31, 2025, 8:56pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082 "2025-03-31T20:56:45Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Anthony\_Kelly](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/anthony_kelly/32/15104_2.png) [@Anthony\_Kelly](https://community.glideapps.com/u/Anthony_Kelly)\
**Post date:** [April 11, 2025, 8:57am UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/24 "2025-04-11T08:57:52Z")

</div>

Yes Jeff I tried the migration tool. It sort of works. Many of the fields have to be re-mapped, as the tool just seems to guess. Also you need to add back things like Sorting, Grouping and Filtering. Also if you use user filtering, this field needs to be re-mapped aslo. The detail page did more or less work, some tweeking to the formatting was all that was needed.

One thing I don’t like about the new app. - my app is a list (about 500 items), it you click on an item, it will go to as it shoud to the detail of that item, but when it returns to the list - to goes right back to the start, and not to the item that was clicked on.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [April 11, 2025, 3:30pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/25 "2025-04-11T15:30:15Z")

</div>

> [@Anthony\_Kelly](#):
>
> One thing I don’t like about the new app. - my app is a list (about 500 items), it you click on an item, it will go to as it shoud to the detail of that item, but when it returns to the list - to goes right back to the start, and not to the item that was clicked on.

This has been discussed a lot in the forum, but not sure if they have a fix for that in the pipelines.

---

<div class="post-metadata">

**Author:** ![Anthony\_Kelly](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/anthony_kelly/32/15104_2.png) [@Anthony\_Kelly](https://community.glideapps.com/u/Anthony_Kelly)\
**Post date:** [April 12, 2025, 8:03pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/26 "2025-04-12T20:03:27Z")

</div>

Thanks, but actually, I have now found a solution. Open detail page as an overlay or a slide-in works.  
Now all I need is for the grouping header (which is the date) to freeze until the next date appears - like on the classic calendar list!

---

<div class="post-metadata">

**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\
**Post date:** [April 28, 2025, 1:15pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/27 "2025-04-28T13:15:06Z")

</div>

DJP

Did my first migration and it is great to have the data moved and the overall structure in place. Yet I agree with Robert sentiment below. There is a lot re-design in just the cases outlined below in 1 and 2 (plus floating buttons).

In the end - the UI change is sufficient to require time/energy/creativity and then grunt work to re-design how the App should behave under the new Glide design UI. The migration tool does a fine job but the UI changes require a lot of effort depending how “clever” your Classic app is. From what I see it is not a weekend migration…so Glide developers need to be prepared to invest some time.

Regards

> [@Robert\_Petitto](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [April 28, 2025, 4:12pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/28 "2025-04-28T16:12:56Z")

</div>

Appreciate the feedback!

---

<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:** [April 29, 2025, 10:33pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/29 "2025-04-29T22:33:16Z")

</div>

@DJP Migrate worked fairly well. The biggest issue I had was that many images stored in Glide’s cloud storage didn’t migrate over. The filenames were reference correctly, but they were referencing a different folder/bucket it seemed.  
https://www.loom.com/embed/ff6a566f2e714cb29b82c05537ddc7cb

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [April 30, 2025, 2:54pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/30 "2025-04-30T14:54:38Z")

</div>

Great report! Will investigate

Can we get app IDs and support links?

---

<div class="post-metadata">

**Author:** ![Jean\_Claude](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jean_claude/32/54947_2.png) [@Jean\_Claude](https://community.glideapps.com/u/Jean_Claude)\
**Post date:** [April 30, 2025, 3:57pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/31 "2025-04-30T15:57:54Z")

</div>

Hi yes I tried it’s not working on my side please can you assist?

---

<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:** [April 30, 2025, 4:05pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/32 "2025-04-30T16:05:02Z")

</div>

Next time it happens I will. I’ve already migrated all the links.

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [April 30, 2025, 4:28pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/33 "2025-04-30T16:28:48Z")

</div>

Can you provide the app IDs? This would still help us debug

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [April 30, 2025, 4:29pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/34 "2025-04-30T16:29:31Z")

</div>

Can you explain what is not working? Have you read our [Glide Doc](https://www.glideapps.com/docs/classic-apps#classic-app-migration-tool-walkthrough)?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [April 30, 2025, 4:36pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/35 "2025-04-30T16:36:56Z")

</div>

> [@Migration to New App – Urgent & Sensitive Request](https://community.glideapps.com/t/migration-to-new-app-urgent-sensitive-request/81631):
>
> Hi there wonderful people I need urgent help to migrate to the new app. When I follow the steps it just loads and times out I have some really sensitive data set close to 25000 lines however it’s an issue syncing the data. Any help please?

---

<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:** [April 30, 2025, 5:13pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/36 "2025-04-30T17:13:19Z")

</div>

> [@DJP](#):
>
> Can you provide the app IDs? This would still help us debug

Old app: px5CcPhmLia5ABlKXY5Q  
New app: vYhkhDlbGJ5V7TkLvdFc

These app ids are also the cloud storage buckets. So probably why it failed after migration.

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [April 30, 2025, 5:27pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/37 "2025-04-30T17:27:42Z")

</div>

What provisions are in place for clients who invested significant funds in the development of Classic Apps? Will Glide offer refunds or cover the cost of hiring an Expert to transition these projects to the new platform? Additionally, how will the time and resources spent on advertising and distributing URLs be addressed?

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [April 30, 2025, 7:12pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/40 "2025-04-30T19:12:42Z")

</div>

Have you tried our migration tool already? We have found that most customers can easily migrate to New Glide Apps using the tool

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [April 30, 2025, 8:11pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/42 "2025-04-30T20:11:54Z")

</div>

The issue lies in the substantial amount of work required to rebuild these apps, which ultimately do not look or function like the original versions. Who will compensate for this disruption, along with the many other challenges it creates for clients and developers alike?

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [April 30, 2025, 8:26pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/43 "2025-04-30T20:26:28Z")

</div>

What is Glide’s legal position regarding potential liability when clients begin taking legal action against developers for products they paid to have developed, along with ongoing subscription fees, only to find that these apps suddenly stop functioning due to platform changes?

---

<div class="post-metadata">

**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\
**Post date:** [May 1, 2025, 4:36pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/44 "2025-05-01T16:36:52Z")

</div>

We understand that migration can be difficult, so we created a migration tool to make the transition as seamless as possible. Once you use the tool, let us know about your experience.

The Glide team announced that Classic Apps are no longer supported over 2 years ago in March 2023 ([Glide Doc)](https://www.glideapps.com/docs/classic-apps) and made New Glide Apps the officially supported product.

With all software platforms, new products / features are released and older products / features can be deprecated. Your subscription entitles you to access to the platform and its current capabilities but not the guarantee that all features will be supported into perpetuity. We do our best to minimize disruption, but sometimes features will be deprecated. We appreciate your understanding.

If you do not wish to continue using Glide, I am happy to offer you a refund for your latest billing period and cancel your subscription.

---

<div class="post-metadata">

**Author:** ![HTML](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/html/32/87893_2.png) [@HTML](https://community.glideapps.com/u/HTML)\
**Post date:** [May 1, 2025, 5:08pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/45 "2025-05-01T17:08:50Z")

</div>

I canceled my Glide subscriptions a long time ago and currently use the platform only for small internal projects on the free plan, quick tasks that can be completed in a few minutes. For all other work, I build full-code applications on my own server. My concern is for clients who hired me to create Glide apps, despite my strong recommendation against using the platform. Now they are coming back, frustrated about the money they have lost.

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [May 1, 2025, 5:38pm UTC](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082/46 "2025-05-01T17:38:35Z")

</div>

> [@HTML](#):
>
> My concern is for clients who hired me to create Glide apps, despite my strong recommendation against using the platform. Now they are coming back, frustrated about the money they have lost.

If you strongly recommended against using the platform, were concerned for your clients and yet still built apps for them on Glide, then you either offered services against their best interest or weren’t all that convinced that Glide wasn’t the right choice for them.

When Apple doesn’t support a product after a few years or your Samsung light bulb blows, you don’t return to the company surprised the product doesn’t work anymore. I’m not saying it’s right, but we’re all accustomed to products and services not lasting forever.

Glide is somewhat of a black box that offers a fully integrated platform. They could pull the plug tomorrow and apps hosted on their platform would be gone. That’s part of the deal and what you sign up for when using Glide.

[Previous page](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082.md?page=1)

[Next page](https://community.glideapps.com/t/deprecation-of-classic-apps-begins-monday-june-30th/81082.md?page=3)
