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. Keep enough history to separate a planned test from an unrelated change.
Explain camera, location, and notification requests in context. Check the user journey when access is declined or later changed. Give the team a clear route for questions and corrections.
Make the plan fit your market
Discuss whether users in Arlington 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.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Keep a record of permission for any customer story used publicly.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities