Studio services / No. 06
Mobile app development
An app earns its place on a phone by doing something useful there. We start with the task a person needs to finish on the move, then design for the screen, connection and device permissions they actually have.
Discuss your project ↗
01 / The brief
Who it’s for
Product teams launching a mobile service or replacing a mobile workflow that breaks away from a desk.
Start with a mobile website if users only need occasional access to information. An installed app makes more sense when repeat use, camera access, offline records or notifications are central to the experience.
02 / Scope
Inside the work
Platform brief
Decide whether shared code or separate native builds fit the device features, release cadence and team maintaining the app.
Offline and recovery flows
Specify what is saved locally, when changes sync and how the interface handles conflicting edits or expired sessions.
Release preparation
Test on agreed physical devices and prepare permissions, signing, store assets and a handover to the account owner.
03 / Discovery
Where we start
Show us the most frequent task, the oldest device you need to support and what must still work if the connection drops halfway through.
See how we work ↗04 / Field notes
Before you start
Do we need separate iOS and Android apps?
Not always. A shared React Native or Flutter build can fit similar journeys on both platforms. Prototype the hardest device integration before choosing.
Who should own the app store accounts?
The business should normally control its publisher accounts and grant the delivery team the access it needs. Include signing access, release notes and update responsibilities in the handover.