MOBILE APP PROJECT BRIEF
Free planning worksheet from Codent — https://codent.ca
Guide and worked example: https://codent.ca/blog/mobile-app-project-brief

Write short answers. "Not sure yet" is useful too.
Keep passwords, customer records, and confidential system details out of this brief.

1. THE PROBLEM
Who will use the app?
What task is difficult today, and how do they do it now?
What should become easier after the first release?

2. ONE COMPLETE USER JOURNEY
When [situation], a [user] needs to [task], so they can [result].
How does the journey start, and what counts as finished?
What must happen if the connection fails or the user makes a mistake?

3. FIRST RELEASE
The three essential features:
-
-
-
Features that can wait:
-

4. PLATFORMS AND ACCESS
iPhone/iPad, Android, browser, or desktop?
Is a guest mode enough, or do users need accounts?
Which tasks must work offline?
Who needs an admin view, and what must they be able to change?

5. DATA, PAYMENTS, AND CONNECTIONS
What information needs to be stored?
Who may read, edit, or delete it?
Existing services or APIs to connect (names only):
Any subscriptions, bookings, purchases, uploads, or notifications?
Any data that must move between devices?

6. BUDGET, DEADLINE, AND SUCCESS
Budget range and currency (include whether taxes and ongoing costs are inside it):
Target date, and why that date matters:
What could move to a later release if needed?
How will you judge whether the first release is useful?

7. EXISTING WORK AND HANDOVER
Do designs, an app, a website, or source code already exist?
Who controls the repository, hosting, and app-store accounts?
Who will maintain the app after launch?
What documentation and access need to be handed over?

BEFORE ACCEPTING A PROPOSAL
[ ] Deliverables and exclusions are explicit.
[ ] The main workflow and acceptance checks are described.
[ ] Design, backend/admin work, and testing responsibilities are clear.
[ ] Integrations, data migration, and store submission are included or excluded.
[ ] Source-code ownership, accounts, licences, and handover are agreed.
[ ] Third-party fees, hosting, taxes, and ongoing support are separated.
[ ] Changes to the scope have an agreed review and pricing process.

This is a planning worksheet, not a quote or a contract.
To discuss a project with Codent: https://codent.ca/contact?service=custom-app-development