Product scoping
What the first version does, and above all what it does not. An app that tries everything never ships.
Looking for the right starting point?
Tell us the context and we will help you work out the next step.
Take stockServices Mobile applications
iOS and Android from a single shared codebase, from product scoping to store release, with version upkeep once the app is published.
A workshop, then a document that fixes what goes into the first version.
The main journeys put in the hands of real people before development.
At the end of every cycle, a version you can install on your phone. You follow the progress without a demo.
A small group first, then the fixes, then submission to both stores.
What the first version does, and above all what it does not. An app that tries everything never ships.
The screens linked together, usable on a real phone, before any code is written.
iOS and Android held together: a fix is written once, not twice.
The one channel that genuinely brings someone back into an app. As long as it is not overused.
Listings, screenshots, ratings, developer accounts, review. The part everyone underestimates.
The platforms change every year, and an app that stops being updated ends up being removed.
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.
Give us a few pointers about your business and your priorities.
Take stock