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. Keep enough history to separate a planned test from an unrelated change.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Document responsibilities so delivery does not depend on assumptions.
Make the plan fit your market
Discuss whether users in Santa Fe need appointments, field-service access, local inventory, or delivery features. Use the actual workflow to decide whether location data is necessary; do not request device permissions merely because the app serves a local market. Check that location references reflect how the business actually operates.
Describe users, tasks, data, and acceptance criteria before choosing technology. A short working prototype can reveal workflow problems earlier than a detailed visual design. Use only the customer information needed for the agreed work.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities