One-click submit to both stores.
Connect App Store Connect and Google Play Console once, then submit to both stores from one screen. Pre-submission validation, status tracking, automatic retries — no more dashboard pinball.
Everything you need. Nothing you don't.
One release, two stores
Hit submit once and both App Store Connect and Google Play Console receive the binary, metadata, and screenshots in parallel.
Pre-flight validation
Compliance score, metadata completeness, screenshot coverage all checked before the submit button enables. Don't find out after review what's missing.
Status tracking
Live review status across both stores. Slack + email notifications on state changes. No polling, no dashboard-refresh tax.
Track-aware uploads
TestFlight, Internal, Alpha, Beta, and Production tracks all selectable. Phased release % rollouts for Play Store supported.
From "ready to ship" to "in review".
- 01
Connect stores
Link App Store Connect via API key (we never ask for password) and Google Play via service account JSON. One-time setup.
- 02
Pre-flight
Compliance score ≥ 90, metadata filled in both locales you care about, screenshots present for every required device class. All checked before submit enables.
- 03
Submit
Single action. Both stores receive the binary + metadata simultaneously. Upload progress shown in-line; failures surface with actionable error messages, not store-speak.
- 04
Track to live
Submission status syncs automatically. You're notified on every state change — waiting for review, in review, pending developer release, ready for sale, or rejected with guidance.
Why submission is not a one-line problem.
Apple's App Store Connect API and Google's Play Developer API share the word 'submit' and nothing else. Different auth models (API key with key ID + issuer vs service account JSON), different phased-release semantics, different ways to tie a binary to a specific release, different rejection-status taxonomies. Most tools pick one and ignore the other; Stora implements both natively.
Uploads fail. Often. Apple's API times out around 2% of the time under normal conditions and up to 15% around releases (when everyone is pushing at once). Google's is slightly better but has its own bad days. Stora auto-retries transient failures with exponential backoff and distinguishes them from real errors (wrong bundle ID, invalid entitlement, asset mismatch) that need your attention.
Post-submit, the status stream is where most teams lose visibility. Both stores send state changes via webhook but neither is a first-class subscription. Stora polls safely, deduplicates, and emits a clean stream of state transitions you can wire into Slack, email, or your own system.
Who benefits most from unified submission.
Frequently asked.
- Do you store my App Store Connect password?
- No — we never accept passwords. ASC integration uses the App Store Connect API key (key ID + issuer ID + private key), stored encrypted at rest in a per-project enclave.
- Can I schedule submissions?
- Yes — schedule a submission for a future time or trigger it off a successful CI run. Useful for coordinating marketing launches with store review timelines.
- What if my build fails Apple's binary validation?
- The pre-flight step runs the same validation locally (via altool equivalents) before you submit. If it would fail at Apple, you see the error before pressing submit. Saves the 2-day round-trip.
- Can I submit just to one store?
- Yes — each release object has a platform field. iOS-only or Android-only releases skip the other store entirely.
- Does this support phased rollouts on Play?
- Yes — configure the rollout percentage (5%, 10%, 50%, 100%) per release. Increase or halt the rollout from the same screen.
Ready to ship?
Connect your GitHub repo and let agents handle the rest. Your next release, out the door in minutes.