Testing, release and support
An app is not finished when it reaches the store. We test before release, handle the submission process and keep the app up to date as platforms change.
How we approach it
Every project runs automated tests in continuous integration, from unit tests to end-to-end checks on real devices. Before release we go through a written checklist covering permissions, privacy declarations, crash reporting and store metadata. After launch, Google and Apple raise their requirements each year; we plan target SDK updates, dependency upgrades and fixes as a support arrangement agreed with you.
What is included
- CI pipelines with automated tests
- Testing on physical Android and iOS devices
- Crash reporting and release monitoring
- Store submissions and staged rollouts
- Yearly platform requirement updates
What you receive
- Test reports for each release
- Release checklist and notes
- Monitoring dashboards you can access
- Support terms written into the proposal
Timelines and pricing are quoted per project after a discovery call.
Common questions
What happens if a release causes a crash?
Staged rollouts let us pause a release early. We then fix the cause and publish an update.
Do you support apps you did not build?
Yes, after an initial audit so we understand the code and its risks.
How are support hours arranged?
They are agreed per project and written into the proposal.
Ask about testing, release and support
We reply from [email protected]. Send any documents to that address after your first message.