Before you build or rebuild your app: a 15-point check

Part 1. Is the first version small enough?

Five questions on scope, including who it's for, the one thing a user must do on day one, and the list of what you won't build yet.

1. Can you say who it is for in one sentence?
2. What is the one thing a user must be able to do on day one?
3. Have at least five real people told you they want it?
4. Do you know what you will measure after launch?
5. Is there a list of what you will not build yet?

Want help cutting the scope? See MVP development

Part 2. If you already have an AI-built prototype

Six checks you can run yourself, such as: does logging out really log you out, and can one user see another user’s data by changing a number?

6. Does logging out actually log you out?
7. Can one user see another user’s data by changing a number in the URL or request?
8. Are API keys or secrets visible in the app or the browser?
9. What happens with 100 users at the same time?
10. Are there backups, and has anyone tried restoring one?
11. Can it get into the App Store or Play Store?

Items 6 to 10 are what our security audit tests
Item 11: App Store rejection help

Part 3. Choosing who builds it

Four questions to ask any team, including who owns the code and accounts.

12. Did they ask you hard questions before quoting?
13. Will you own the code, the accounts and the app store listings?
14. Can you talk to the people who actually write the code?
15. What happens after launch?