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 dated records rather than relying on memory at the next review.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Name an owner for each task so requests do not get lost.
Make the plan fit your market
Discuss whether users in Temple 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. Base local references on service coverage and customer needs, not invented examples.
Describe users, tasks, data, and acceptance criteria before choosing technology. A short working prototype can reveal workflow problems earlier than a detailed visual design. Confirm permissions before sharing customer information or assets.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities