App store release with team coaching
We are preparing a major launch and don't want publishing to rely on one person: how do we secure the release and make the team autonomous afterwards?
On quote - Timeline: On quote
Publishing an app involves several steps and often requires adjustments before and during the stores' review. We support your team in preparing the launch, we list the points to fix with suggested solutions, and we follow the exchanges with Apple and Google alongside them until acceptance. We document the process as we go and pass on the practices your developers need to handle the next releases by themselves.
For example, Your team is launching its first large-scale app, A first submission generated correction requests that are hard to interpret, You want your developers to handle the next releases on their own...
What's included
- Creation and configuration of the Apple and Google accounts
- Store listing preparation: ASO visuals and help writing copy that meets the stores' requirements
- Technical and functional requirements audit
- List of points to fix, with suggested solutions, and support for your team while they fix them
- Preparation and submission of the app
- Follow-up on Apple and Google reviews and analysis of feedback or rejections, until acceptance
- Documentation of the release process
- Knowledge transfer to the team
What's not included
- Fixing the code in place of your team
- Development of new features outside the scope
- Full redesign of the app
- Ongoing maintenance and post-launch checks
- Management of subsequent releases after the engagement
- Fees charged by Apple or Google
- Ongoing acquisition
Prerequisites
- App close to production
- Technical team available during the engagement
- Access to the relevant environments and tools
- Identified contacts on your side
Frequently asked questions
Why on quote?
The scope depends on your team's size, the state of the app and the number of stores involved. We define it together during a first call.
Do you fix the issues yourselves?
No. We list the points to fix, with suggested solutions when the issue lends itself to it, and we support your developers while they work through them. That is what makes the team autonomous afterwards.
How is this different from the App store release?
The App store release, we do it for you. Here, we do it with your team, and we stay until they can do it again on their own.
Where does the engagement end?
When the app is accepted by Apple and Google. Post-launch checks and subsequent releases are not included.