# Rollout strategy

**URL:** <https://community.glideapps.com/t/rollout-strategy/4729>\
**Category:** Ask for Help\
**Created:** [February 18, 2020, 11:11pm UTC](https://community.glideapps.com/t/rollout-strategy/4729 "2020-02-18T23:11:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Eden](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark_eden/32/340_2.png) [@Mark\_Eden](https://community.glideapps.com/u/Mark_Eden)\
**Post date:** [February 18, 2020, 11:11pm UTC](https://community.glideapps.com/t/rollout-strategy/4729/1 "2020-02-18T23:11:20Z")

</div>

What a fabulous tool your team has developed 👍 Incredibly intuitive, simple and yet still powerful. It appears that changes that we make – either to the UI or to the data itself – are deployed or rolled out to our app users in close to real-time, which is amazing. However, in the cases where we are prototyping or trying things out before making them “live”, has anyone identified a good process? Is it simply copying the app?

---

<div class="post-metadata">

**Author:** ![Mark\_Eden](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark_eden/32/340_2.png) [@Mark\_Eden](https://community.glideapps.com/u/Mark_Eden)\
**Post date:** [February 19, 2020, 12:08am UTC](https://community.glideapps.com/t/rollout-strategy/4729/2 "2020-02-19T00:08:59Z")

</div>

I subsequently found the below thread, which essentially covers the “ask” that I was trying to convey:

> [@Maintenance Mode](https://community.glideapps.com/t/maintenance-mode/3758):
>
> Just a simple check-box or switch from within the Glide Dashboard-Editor that when selected turns all screens and tabs within the accessible version of the app invisible and a message that says something like “We are doing some work on the app and will return shortly”… ideally a custom message. This wouldn’t affect the editor dashboard for the app, and would therefore allow you to do major upgrades to your own app without any of your users using the app while you’re doing that sensitive work. A…

---

<div class="post-metadata">

**Author:** ![Sandro\_Brito](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/sandro_brito/32/552_2.png) [@Sandro\_Brito](https://community.glideapps.com/u/Sandro_Brito)\
**Post date:** [February 19, 2020, 9:30am UTC](https://community.glideapps.com/t/rollout-strategy/4729/3 "2020-02-19T09:30:39Z")

</div>

I am not sure if this is something glide intended or if they advise but the way I’ve done it before was 2 fold:

- First I create a copy of my app and fiddle with the copy until it’s right and replicate the changes into the normal app.
- If the changes to the app require quite a bit of restructuring of data, (or quite a bit of work that can’t be done in maybe under an hour) I work on the duplicate app and swap the URLs. The saved webapps on people’s homescreens will point to the new one.

One note with this last approach is, if you app is live and people are creating content or something, make sure to import the content the users inputted right up to deployment of the new version. You don’t want to have users lose their data.

---

<div class="post-metadata">

**Author:** ![Heena\_Mirchandani](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/heena_mirchandani/32/33315_2.png) [@Heena\_Mirchandani](https://community.glideapps.com/u/Heena_Mirchandani)\
**Post date:** [November 14, 2021, 4:04pm UTC](https://community.glideapps.com/t/rollout-strategy/4729/4 "2021-11-14T16:04:09Z")

</div>

Hey, I would wish to know, how did you Swap URLs?

---

<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:** [November 14, 2021, 9:51pm UTC](https://community.glideapps.com/t/rollout-strategy/4729/5 "2021-11-14T21:51:01Z")

</div>

Change the url of the original app to something random. Then change the url for the new app to the url that used to be on the original app.
