Lorixen.
EN

Writing an App Brief: Screens, User Roles and Data Before You Ask for Quotes

Short answer: An app brief that produces comparable quotes describes who uses the app (user roles and what each may do), the handful of screens that carry the main journeys, the data the app stores and where it comes from, the systems it must connect to, and what is deliberately left for later. Add practical details developers always need: which platforms, whether it must work offline, who owns the Apple and Google developer accounts, and how you will judge success. Four to six pages is enough. The worked example below, a booking app for a cleaning company, shows the level of detail that helps without turning into a technical specification.

Why app briefs need more than a website brief

A website brief is mostly about pages, content and look. Apps add people logging in with different rights, data created on phones in the field, notifications, offline moments in a basement flat, and two app stores with their own accounts and review rules. If the brief skips these, each developer fills the gaps with their own assumptions, and quotes become impossible to compare.

The template sections

Use these headings in this order.

  1. Background: the business, the problem, and why an app rather than a website or existing software.
  2. Goals: two or three measurable outcomes.
  3. User roles and permissions: who uses it and what each role can see and do.
  4. Key journeys and screens: the main tasks, step by step, with the screens involved.
  5. Data: what is stored, where it originates, who can edit it.
  6. Integrations: payment, calendar, accounting, CRM, maps.
  7. Platforms and devices: iPhone, Android, tablets, a web admin panel.
  8. Offline and notifications: what must work without signal, which events trigger messages.
  9. Must, should, later: a prioritised feature list.
  10. Accounts and ownership: store accounts, domain, hosting, source code.
  11. Budget range and timing: honest numbers help developers propose the right scope.
  12. Open questions: things you do not know yet.

Worked example: Brightway Cleaning

Brightway (a made-up company) runs domestic and end-of-tenancy cleaning in Bristol with twelve cleaners. Bookings arrive by phone and a website form, schedules live in a shared calendar, and cleaners receive job details by text message.

Background and goals

  • Customers book and pay for regular and one-off cleans in under three minutes.
  • Cleaners see their day's jobs, access notes and check in and out on site.
  • Office staff stop retyping bookings into the calendar.

User roles and permissions

Role Can do Cannot do
Customer Book, reschedule, pay, rate a clean, see own history See cleaner phone numbers or other customers
Cleaner See assigned jobs, access notes, check in and out, upload photos See prices or reassign jobs
Office manager Create and assign jobs, manage cleaners, issue refunds Change company settings
Owner Everything, including pricing and reports Nothing restricted

A table like this answers half of a developer's security questions before they ask.

Key journeys and screens

Customer booking:

  1. Choose service (regular, one-off, end of tenancy).
  2. Enter postcode and property size.
  3. See price and available slots.
  4. Add access notes (key safe code, pets).
  5. Pay by card or save card for regular cleans.
  6. Receive confirmation.

Cleaner day:

  1. Open today's list in order of time.
  2. Tap a job for address, map link, notes and checklist.
  3. Check in on arrival, check out when finished, with optional photos.

Office:

  1. Dashboard of today's jobs and unassigned bookings.
  2. Drag a booking to a cleaner.
  3. Handle a cancellation and refund.

Sketch these on paper or in a simple wireframe tool. Boxes and arrows are fine; the purpose is to show flow, not design.

Data

  • Customers: name, email, phone, address, access notes. Access notes are sensitive, so only the assigned cleaner should see them, and only on the day.
  • Bookings: date, time, service, price, status, assigned cleaner.
  • Cleaners: name, phone, working areas, availability.
  • Check-ins: timestamps and optional photos.
  • Payments: handled by the payment provider; the app stores only references.

Note where data lives today (calendar, spreadsheet) and whether you want it imported.

Integrations

  • Card payments with saved cards for regular customers.
  • Accounting software receiving paid invoices.
  • Calendar sync for the office, at least one way.

Platforms, offline, notifications

  • Customer app on iPhone and Android, or a mobile web version for customers if budget is tight.
  • Cleaner app must show the day's jobs without signal, since some flats have none.
  • Notifications: booking confirmation, reminder the day before, "cleaner on the way", job assigned (for cleaners).

Must, should, later

  • Must: booking with payment, cleaner job list with offline access, office assignment, reminders.
  • Should: ratings, photos at check-out, accounting sync.
  • Later: referral credits, multiple cities, live cleaner location.

Developers can then price "must" firmly and estimate the rest separately.

Accounts and ownership

State that the business will own:

  • The Apple Developer Program account, enrolled as an organisation, which requires a D-U-N-S number.
  • The Google Play developer account, registered to the company.
  • The domain, hosting and database accounts.
  • The source code repository, with the developer invited as a collaborator.

Asking this in the brief filters out suppliers who prefer to keep control.

The questions developers will ask anyway

Answer these upfront and you save a round of emails:

  1. How many users do you expect in year one, roughly, per role?
  2. Is there an existing system the app replaces or must work alongside?
  3. Do you have brand guidelines and a logo in vector format?
  4. Who will write the in-app text and store listings?
  5. Who tests the app before release, and how much time can they give?
  6. What support and updates do you expect after launch?
  7. Are there legal requirements, such as data protection documents or accessibility needs?
  8. What is the deadline, and is it fixed by an event?

FAQ

How long should an app brief be?

Four to six pages, plus sketches. Long enough to remove guesswork, short enough that suppliers read all of it.

Do we need wireframes before asking for quotes?

Rough sketches of the main screens help a lot. Polished designs are not needed; that is usually part of the project.

Should we include a budget?

Yes, a range. Without it, one supplier quotes a basic version and another a deluxe one, and you cannot compare them.

What if we do not know which features we need?

Write down the problem and the people involved, and mark features as "unsure". A good developer will suggest a discovery phase to settle them.

Once your brief is drafted, we are glad to read it and point out gaps before it goes to suppliers; send it over whenever it is ready.

Sources

WhatsAppBook a call