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.
Test navigation and task flow with intended users. Feedback on a simple prototype can prevent expensive revisions later. Separate production, approval, and publishing responsibilities.
Make the plan fit your market
Discuss whether users in Providence 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. Explain any real service-area limits that affect customers in Providence.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Keep private account details out of public briefs and examples.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities