# App requirements document template

From Spacewalk · https://spacewa.lk/guides/app-requirements-template/

## 1. The app in one sentence

Describe what the app does and for whom, in one sentence.

- What would you say if someone asked what the app is for?
- Which word would a user type into an app store or search engine to find it?

Answer:

## 2. Who will use it

The people who will use the app, and the situation they are in when they open it.

- Are they customers, staff, or both?
- Where are they and what are they doing when they use it?
- What do they use today instead: a spreadsheet, paper, another app?

Answer:

## 3. The main task

The one job the app must do well, and how you will know it does.

- What does a user need to finish in a single visit?
- What should be different for them after the first week of use?

Answer:

## 4. First release

The features the first release (often called the minimum viable product, or MVP) cannot launch without, in order of importance. Keep later ideas on a separate list.

- Which features would you remove last?
- Which ideas can wait until people are using the app?
- Is anything deliberately out of scope?

Answer:

## 5. Platforms and devices

Where the app needs to run on launch day.

- iPhone, iPad, Android phones and tablets, a web browser, or a mix?
- Does it need the camera, location, notifications or other device features?

Answer:

## 6. Data, accounts and connection

Where information is stored, whether people sign in, and what happens without an internet connection.

- Does each person's data stay on their device, or is it shared through a server?
- Do users need an account? Which sign-in methods?
- Which tasks must still work offline, and how should changes sync later?

Answer:

## 7. Payments and integrations

Anything the app must connect to, and how it will make money.

- Subscriptions, one-off purchases, ads, or free?
- Existing systems: a website, database, payment provider, accounting or stock system?
- File import or export: spreadsheets, PDFs, CSV?

Answer:

## 8. AI features

If the app uses an AI model, a few examples of the input and the answer you would consider useful. Write "None" if it does not.

- What will the user give the model: text, a photo, a document?
- What should a good answer look like?
- What happens when the answer is wrong or incomplete?

Answer:

## 9. Ownership and handoff

Who will own each account and asset after launch, and who supports the app.

- Who holds the Apple Developer and Google Play developer accounts? Apple allows only one Account Holder (https://developer.apple.com/help/app-store-connect/manage-your-team/overview-of-accounts-and-roles) per developer account.
- Who owns the source code, domain, server and app store listings?
- Who writes the privacy policy and the App Store privacy details (https://developer.apple.com/app-store/app-privacy-details/)? Apple asks for the practices of third-party code in the app as well.
- Who fixes bugs and updates the app after launch?

Answer:

## 10. Constraints

Dates, budget, rules and anything else that limits the project.

- Is there a launch date, and what depends on it?
- A budget range, if you have one.
- Regulations or security requirements in your industry. For mobile app security, the OWASP Mobile Application Security Verification Standard (MASVS) (https://mas.owasp.org/MASVS/) is a common reference.

Answer:

## 11. Open questions and attachments

What you have not decided yet, and anything that shows the idea.

- Decisions you want help with.
- Sketches, screenshots, a current spreadsheet, or apps you like and why.

Answer: