# Feature Request – "Update Mode" 🔄 **URL:** \ **Category:** Feature Requests\ **Created:** [March 12, 2025, 12:26pm UTC](https://community.glideapps.com/t/feature-request-update-mode/80681 "2025-03-12T12:26:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Vladislav\_N](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/vladislav_n/32/84363_2.png) [@Vladislav\_N](https://community.glideapps.com/u/Vladislav_N)\ **Post date:** [March 12, 2025, 12:26pm UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/1 "2025-03-12T12:26:39Z")
When developing and updating apps in **Glide** , it’s crucial to make changes without users experiencing glitches or unstable versions. 📌 **What does “Update Mode” do?** ✅ When activated, **all active users** are automatically redirected to a screen displaying: _“Please wait, the app is updating…”_. ✅ New users who try to access the app during this time are also redirected to the same screen. ✅ Once the update is complete, the app becomes accessible again. 🔧 **Why is this useful?** ✔ Ensures **a smooth and error-free update process** for users. ✔ Improves **user experience** by preventing them from encountering broken or incomplete features. ✔ Provides **more control** over app availability during critical updates. 📣 **What do you think? Would you like to see this feature in Glide?** 👇 Share your thoughts in the comments! 🚀 ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [March 12, 2025, 4:30pm UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/2 "2025-03-12T16:30:03Z")
It is possible by using a config table and visibility conditions on screens. But I agree that there should be a native maintenance feature. ---
**Author:** ![iPomidor](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ipomidor/32/82073_2.png) [@iPomidor](https://community.glideapps.com/u/iPomidor)\ **Post date:** [March 13, 2025, 6:09am UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/3 "2025-03-13T06:09:45Z")
Yes, you are right; there are many ways to do this. However, the manual method does not guarantee a 100% success rate since we do not have a list of active users. I am sure that this feature will bring only positive emotions to developers. ---
**Author:** ![iPomidor](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ipomidor/32/82073_2.png) [@iPomidor](https://community.glideapps.com/u/iPomidor)\ **Post date:** [March 13, 2025, 6:10am UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/4 "2025-03-13T06:10:38Z")
+1 ---
**Author:** ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)\ **Post date:** [March 14, 2025, 5:29am UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/5 "2025-03-14T05:29:43Z")
Not sure I like this. Triggering an unnecessary loss of service when manual visibility conditions can be used instead is not the best UX. Perhaps a better suggestion would be a new sandpit feature in the main Glide menu where you view your Apps in a given plan. I envision it would possible to generate a cloned sandpit-version of any published app. I could then work on the clone, which would not be published. When ready, I could switch the 2 Apps as a way to instantly publish the updated version to users. ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [March 14, 2025, 11:03am UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/6 "2025-03-14T11:03:12Z")
Some changes need to be on maintenance… Like changing database structure. Database structure isn’t affected by the manual publishing. ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [March 14, 2025, 11:03am UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/7 "2025-03-14T11:03:53Z")
I did use a duplicate app to do a v2. But it is a nightmare when it comes to excel tables. ---
**Author:** ![idevnva](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/idevnva/32/87851_2.png) [@idevnva](https://community.glideapps.com/u/idevnva)\ **Post date:** [May 10, 2025, 9:28pm UTC](https://community.glideapps.com/t/feature-request-update-mode/80681/8 "2025-05-10T21:28:27Z")
You create a duplicate and make a new version, but how do you deal with the fact that when you create a new Column in Data, the user is thrown into the application to the main screen of your application?