Specification 01
Mobile development
iOS, Android and cross-platform apps that survive OS updates, team changes and shifting requirements.
01.1
What you receive
| Deliverable | Contents |
|---|---|
| Architecture note | Native vs cross-platform choice with rationale and risks |
| App in test tracks | TestFlight and Google Play internal testing from the first sprint |
| Automated checks | Unit tests for business logic, CI build on every change |
| Dependency ledger | Libraries, licences and next review dates |
| Successor handbook | How to build, sign and release the app without us |
01.2
Quality criteria
- Cold start on a reference device — target agreed before development and measured
- Crash-free session rate tracked in each release report
- Dynamic type and screen readers (VoiceOver, TalkBack) supported
- Minimum OS version recorded in writing with the trade-off explained
01.3
When native, when cross-platform
Native (Swift, Kotlin) makes sense when deep OS integration, heavy graphics or background work matter. Cross-platform (e.g. Flutter or React Native) fits when one team and identical features on both platforms are the priority. We write a comparison note for your case rather than choosing by habit.
01.4
What maintenance includes
- Testing against iOS and Android betas before the autumn OS release
- Updating the Android target API on Google Play's schedule
- Quarterly dependency and licence review
- Crash report with a prioritised fix list
Mobile development
Tell us the context — we will reply with questions and a first step.
Discuss a task