Testing and store release

A release is only finished when it installs cleanly on real phones and passes store review. We test, prepare and publish with that in mind.

How the work runs

Automated tests cover the flows that must not break, and they run on every change. Manual testing then focuses on what automation misses: layouts on small and large screens, dark mode, larger text sizes, interrupted network and upgrades from older app versions with real data.

Store releases involve a lot of paperwork that changes often. We keep checklists for Google Play and the App Store, prepare data safety and privacy declarations with you and roll updates out in stages, watching crash reports before reaching everyone.

What's included

  • Test plan for the main user journeys
  • Automated unit, UI and integration tests
  • Manual testing across screen sizes and OS versions
  • Upgrade testing with data from earlier versions
  • Crash reporting setup
  • Store declarations and staged rollout

What you receive

  • Test plan and results for each release
  • Crash and stability summary after rollout
  • Store submission checklist
  • Release notes in the agreed languages

Languages behind it

Timelines and pricing are quoted per project after a discovery call.

Questions people ask

Do you test apps built by other teams?

Yes. We start with the most used flows and report issues with steps to reproduce them.

What is a staged rollout?

The update reaches a small share of users first. If crash reports stay clean, it expands to everyone.

Ask about testing and release

Ask about testing and release

Tell us about the product and where it is today. We reply by email, usually with a few questions first.

Prefer email? Write to [email protected]. You can also send any documents there.

You will get an automatic copy of your message by email.

This website currently sets no cookies and stores nothing in your browser, so there is no consent to give or withdraw. If that changes, we will ask you first.

Read the Cookie Policy