# How do you work with staging?

**URL:** <https://community.glideapps.com/t/how-do-you-work-with-staging/55033>\
**Category:** Ask for Help\
**Created:** [November 27, 2022, 1:44pm UTC](https://community.glideapps.com/t/how-do-you-work-with-staging/55033 "2022-11-27T13:44:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [November 27, 2022, 2:25pm UTC](https://community.glideapps.com/t/how-do-you-work-with-staging/55033/4 "2022-11-27T14:25:18Z")

</div>

Yes. I actually have one client that insists on this approach for most new features. I talked a bit about that below…

> [@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-do-you-work-with-staging/55033)._
