# How can I temporarily disable an app?

**URL:** <https://community.glideapps.com/t/how-can-i-temporarily-disable-an-app/50280>\
**Category:** Ask for Help\
**Created:** [September 27, 2022, 4:47pm UTC](https://community.glideapps.com/t/how-can-i-temporarily-disable-an-app/50280 "2022-09-27T16:47:31Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [September 27, 2022, 5:33pm UTC](https://community.glideapps.com/t/how-can-i-temporarily-disable-an-app/50280/6 "2022-09-27T17:33:52Z")

</div>

Yes. In fact I have a client that insists on doing this every time we add new features to his app.

So we make a copy, build the new features in the copy, publish that so he can test, then once he is happy we swap the URL’s over and delete the original.

I talked a bit about this in the below post:

> [@Best practices for rolling out and maintaining a Glide App](https://community.glideapps.com/t/best-practices-for-rolling-out-and-maintaining-a-glide-app/48264/6):
>
> I do this for one of my clients. They insist on being able to test new features in a “staging” app before anything goes live. So I developed and documented my own process for managing this. This is what it looks like: It’s fiddly, and the switchover process is fully manual. Usually takes me about 30-60 mins to deploy a new “production” version.

---

_[View the full topic](https://community.glideapps.com/t/how-can-i-temporarily-disable-an-app/50280)._