GuideThe one-page brief
Answer these seven questions in a sentence or two each. It is enough for any good studio to respond usefully.
- Who is this for, specifically? Name a type of person and a situation.
- What do they do today instead, and what annoys them about it?
- What is the single thing your product lets them do that they cannot do now?
- How will you know, three months after launch, that it is working?
- What must be true on day one, and what could wait?
- What constraints exist: dates, budgets, systems you must connect to?
- Who decides, and how quickly can they decide?
ComparisonNative or cross-platform?
Cross-platform (one codebase for iOS and Android) suits products built mainly from lists, forms, accounts and content. It is usually cheaper to build and maintain. It is the wrong choice when the product depends on cutting-edge device features or very demanding graphics.
Native (separate Swift and Kotlin code) gives the deepest access to each platform. It is the wrong choice when the budget only stretches to one good app, not two average ones.
Web app suits occasional use and broad reach. It is the wrong choice when people need it offline or expect push notifications on every device.
GlossaryStore review terms
- TestFlight / internal testing
- Private distribution to named testers before public release.
- Metadata rejection
- The listing, not the code, needs changing. Often quick to resolve.
- Data safety / privacy details
- Forms declaring what data the app collects and why.
- Staged rollout
- Releasing to a percentage of users first.
- Demo account
- Login details reviewers use to reach gated features.