C · 06 Digital Products & Technology
An app people can figure out without a manual.
The problem
Apps get expensive when the plan is vague. Features keep getting added, the design changes halfway through, and the first version takes twice as long as expected. Most of that can be avoided by agreeing on the smallest useful version first and building that well.
What's included
- Working out the core features for the first version
- Screen designs and a clickable prototype you can test before development
- Development for Android and iOS
- Backend, logins and integrations the app needs
- Testing on real devices
- Publishing to the Google Play Store and Apple App Store
How the engagement works
- Discovery sessions to agree on what the first version must do
- Designs and prototype for approval
- Development in stages, with test builds you can install
- Release, then fixes and improvements after launch
Deliverables
- App designs and prototype
- Android and iOS apps
- App store listings
- Source code and documentation
What we'll need from you
- A clear idea of who the app is for and the problem it solves
- Someone who can test builds and give feedback regularly
- Developer accounts for the app stores, or help setting them up
How we measure success
- Whether the first version shipped with the agreed features, on schedule
- Downloads, sign-ups and how many people keep using the app
- Crash reports and app store ratings