Quick answer
“An app like another app” is a starting point, not a specification. Explain which part of the reference matters and what your users should accomplish. Describe the first-time journey, the repeat-use journey and the staff work behind the scenes.
Practical scope
State whether you need iPhone, Android or both. List login methods, profiles, payments, subscriptions, location, camera, notifications and any existing systems to connect. For each feature, include a simple acceptance test: for example, “a customer can change an appointment and receive a revised confirmation.”
Ask vendors how they will handle design prototypes, test devices, store submission, crash reporting and support after release. Confirm ownership of developer accounts and source code in the contract. An initial release should focus on the smallest set of features that solves the user's main problem reliably.
What to define before requesting proposals
- Target users and their first and repeat journeys
- Platforms, devices and accessibility needs
- Accounts, payments, notifications and admin tools
- Analytics, testing, app-store release and support
Questions to ask service providers
- Is the backend included in the proposal?
- Who owns developer accounts, code and release access?
- How are device issues and store rejections handled?
How to assess the answers
A reference app is not a specification. Describe the user outcome and mark which reference features matter so vendors do not quote different products.
Include the staff side of each feature
A fictional booking app may let customers reserve a place, but staff also need to change availability, see payment status and handle cancellations. Include these administration requirements in the same brief. Specify which external services are required rather than describing every feature as part of the app.
Write testable requirements
- A confirmed booking appears once in the staff view.
- An unconfirmed payment does not display as paid.
- A failed transfer is visible to the responsible staff member.
- Support staff can investigate a reported problem using an agreed record.
Is store submission the end of the project?
Define completion in the contract. Submission, approval, release, staff handover and post-release defect support are separate milestones; ask who handles each.
App first-release requirements sheet
Copy these items into your brief, adapt the requirements and assign an owner and status. Examples illustrate planning decisions, not customer case studies. Fill cost fields with HKD quotations you obtain and state the billing period.
| Decision / item | Information to provide | Acceptance / comparison check |
|---|---|---|
| Main user task | User, action, input and result | Demonstrate a completed journey rather than isolated screens |
| Supporting systems | Backend, staff tools, data owner and connections | Vendor identifies everything outside the app interface |
| Release and access | Platforms, developer accounts and release owner | Confirm who handles submission, rejection and later updates |
Download the editable worksheet (CSV)