Keep permissions proportionate
Ask only for access needed by a defined feature. Explain the reason at the appropriate time and provide a useful path when a user declines an optional permission. Record the date, reason, and owner of important changes.
Test navigation and task flow with intended users. Feedback on a simple prototype can prevent expensive revisions later. Agree who can make decisions before the schedule is set.
Make the plan fit your market
Discuss whether users in Boulder 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.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Check access rights before giving another supplier an account login.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities