Product scoping
What the first version does, and above all what it does not. An app that tries everything never ships.
What we do Mobile applications
Area 03
Building mobile applications
iOS and Android from a single shared codebase, from product scoping to store release, with version upkeep once the app is published.
iOS + AndroidPush notificationsStore release
In the project
What we put in place
Clickable prototype
The screens linked together, usable on a real phone, before any code is written.
One codebase, two stores
iOS and Android held together: a fix is written once, not twice.
Push notifications
The one channel that genuinely brings someone back into an app. As long as it is not overused.
Store release
Listings, screenshots, ratings, developer accounts, review. The part everyone underestimates.
Version upkeep
The platforms change every year, and an app that stops being updated ends up being removed.
Our approach
The steps that move the product forward
Scoping and boundaries
A workshop, then a document that fixes what goes into the first version.
Tested prototype
The main journeys put in the hands of real people before development.
Two-week cycles
At the end of every cycle, a version you can install on your phone. You follow the progress without a demo.
Beta, then release
A small group first, then the fixes, then submission to both stores.
- Indicative timeline
- 3 months minimum
- Steps
- 4, from scoping to delivery
- Deliverables
- 6 items itemised in the quote
Use cases
When this area makes the difference
Businesses whose customers come back often, for whom a website is no longer enough.
Field teams that work offline and send data back.
Founders who want a first testable version, not a finished product.
Bearings
The questions worth asking before starting
A shared codebase in the vast majority of cases: the same budget produces two apps instead of one. Native is justified when the app depends on heavy hardware features, and we say so during scoping.
Yes, Apple and Google charge for theirs. They are opened and paid for in your name, not ours: that is what keeps the app yours.
Fixes, compatibility updates and new versions are handled on request. Nothing is committed to in advance.
Also worth a look
Does this format answer your challenge?
Give us a few pointers about your business and your priorities.
Take stock