Launches: Track App Store Submissions

When your version is ready to ship, the next step is submitting it to an app store. In TestApp.io, a Launch represents one submission of one version to one store. Launches give you a structured way to track the progress of every store submission from start to finish.

What Is a Launch?

A Launch is a record that tracks the submission of a specific version to a specific store. For example, submitting v2.1.0 to the Apple App Store is one Launch, and submitting that same version to Google Play is a separate Launch.

Each Launch has its own status, attached checklists, and progress tracking — giving you clear visibility into where every submission stands.

Creating a Launch

Open your app in TestApp.io and navigate to the version you want to submit.
Click New Launch.
Select a publishing destination — the store you are submitting to (e.g., iOS App Store, Google Play).
Your Launch is created in Draft status, ready for you to prepare the submission.

Launch Flow

Every Launch moves through four statuses that mirror the real-world submission process:

Draft — The initial state. You are preparing the submission: reviewing builds, filling in store metadata, and completing checklist items. No submission has been made yet.
In Progress — You are actively submitting to the store. This means you have started the submission process in the store's developer console.
Submitted — The submission is complete and you are waiting for the store to review and approve it. This is the review queue stage.
Released — The app is live in the store. The submission has been approved and is available to users.

Update the Launch status as you progress through each stage. Every status change is recorded so your team has a clear timeline of the submission.

Attaching Playbooks

One of the most powerful features of Launches is the ability to attach Playbooks — reusable release checklists that ensure nothing is missed during the submission process.

When creating or editing a Launch, look for the option to attach a Playbook.
Select one or more Playbooks relevant to this submission (e.g., the iOS App Store Submission playbook for an App Store launch).
The Playbook items appear within your Launch, ready to be checked off.

Playbooks bring consistency to your release process. Instead of relying on memory or ad-hoc checklists, your team follows the same verified steps every time.

Tracking Progress

Once Playbooks are attached to a Launch, track your progress by checking off items as you complete them:

Checkbox items — Mark as complete when verified (e.g., "Screenshots updated for all device sizes").
Text fields — Fill in required information (e.g., "Release notes for this submission").
Required items — Items marked as required must be completed before the Launch can proceed. This prevents incomplete submissions.

The Launch view shows you at a glance how many items are completed versus remaining, so you always know how close you are to being ready to submit.

Multiple Launches per Version

Most apps ship to more than one store. TestApp.io supports this by allowing you to create multiple Launches for a single version:

Create one Launch for the Apple App Store.
Create another Launch for Google Play.
Create a third for TestFlight if you are running a beta program.

Each Launch tracks its own status and progress independently. This means your iOS submission can be in review while your Android submission is still being prepared — and you can see both at a glance from the version dashboard.

Tips

Create your Launches as soon as the version enters Testing, so your team can start completing Playbook items in parallel with QA.
Use platform-specific Playbooks to ensure each store's unique requirements are covered.
Keep Launch statuses up to date so your whole team has real-time visibility into submission progress.
Review the submission history on your publishing destinations to learn from past releases.

Need help? Contact us and we'll get back to you shortly.