Describe the product in one sentence
Template: “[Who] can [do what] in order to [gain what]”. If the sentence will not come, the task is not yet defined.
Resources
Founder cheat sheets
Short and to the point: what to know before, during and after building an app.
Found: 12
A “not in version one” list
Write down everything you want and strike out all but three features. Keep the rest on a separate list.
Minimum touch target size
Buttons and links on phones should be at least roughly 44 by 44 pixels, otherwise people miss them.
Write copy before design
Real copy changes layouts. Placeholders hide problems with line length and translation.
Screen states
For every screen consider: loading, empty, error and success.
Native or cross-platform
Cross-platform is often cheaper to start; native gives more control. Ask what maintenance looks like in a year.
Who owns the domain
The domain should be registered to you. Check who can access the registrar panel.
Developer store accounts
Register Apple and Google accounts to the company. Verification can take time — start early.
Privacy policy
Both stores require a published privacy policy describing the data collected.
Store screenshots
Show the benefit, not the settings menu. Check size requirements for each device.
Who is responsible after launch
Decide where users report problems, who reads those messages and how you respond.
Backups
Find out where data copies live and how to restore them. Test a restore at least once.
Check yourself
These tips are collected into an interactive readiness checklist.
To the checklist