I’m preparing the first release for our app (MVP with key features done, full version still in progress). We’ve uploaded the build and got it approved for Closed Testing. Now our goal is to go through a “real” production-area review (i.e., the same review process our public release will go through) but we don’t want the app to become publicly visible yet.
Questions:
What’s the best track and workflow if we want review now but keep public visibility off?
With “Managed Publishing” turned on in Play Console, can we promote to Production track (or choose Open Testing) and then not hit “Publish changes” until we’re fully ready? Or does the system require the app to go live once review is approved?
Are there known pitfalls for first-time production releases with Managed Publishing (many posts say this may be unsupported).
So the goal is after approved closed testing to add more features but first: go through a better "real production ready review", so that we do not wait until production release date and fix potential review blockers now before adding new features. I am worried that once we promote first closed testing to production, not be able to create new closed testing build until that production build is published (and potenitaly visible to users).
Appreciate any real-world experiences or best practices from developers who have done this. Thanks!