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 the original result alongside the updated version.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Set a review deadline and identify the person responsible.
Make the plan fit your market
Discuss whether users in Atlanta 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. Keep contact and availability details current for the Atlanta market.
Describe users, tasks, data, and acceptance criteria before choosing technology. A short working prototype can reveal workflow problems earlier than a detailed visual design. Agree how sensitive material will be shared and stored.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities