Android testing & Play Store delivery
Test suites, signing and internal-test distribution, and shepherding the app through Play review.
What we build
Unit and UI test suites, automated signing and Play internal-test distribution, store screenshots and metadata, and managing the submission through review. Without this the app is finished but not shipped.
What you get
- A unit test suite covering the agreed critical paths, green in CI
- A UI test suite covering the primary user journey, green in CI
- Automated release signing in CI using a stored upload key
- An internal-test track your named testers can install from
- Store screenshots at every size Google Play requires
- The completed Play Store listing (description, categorisation, content rating)
- The build submitted to Play review, with reviewer questions answered until a decision is issued
How the work unfolds
- Set up the Google Play developer account and Console
- Write the unit and UI test suites
- Automate signing and Play internal-test distribution
- Produce store screenshots and metadata
- Submit and manage Play Store review
What shapes the price
Before you see a number, our scoping conversation asks:
- Do you already have a Google Play developer account, or should we set one up with you? First-time account setup, identity verification and the Console app record are a day.
How an engagement starts
This work builds on Android core feature build, so scope, boundaries and constraints are agreed before anything is built.
Teams often combine it with: