Start with the user's task
Define the problem a user needs to solve before listing screens or features. Check the current process, the devices involved, and the places where an app would remove real effort. Use the findings to update the brief for the next stage.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Agree which tasks are included and which need a separate quote.
Requirements that can be tested
Describe users, tasks, data, and acceptance criteria before choosing technology. A short working prototype can reveal workflow problems earlier than a detailed visual design. List the required outputs before setting the delivery schedule.
Separate essential tasks from later features. Build the smallest release that can be used and evaluated, with explicit exclusions and a change process. Record the decision as well as the numbers behind it.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities