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 a change log so later results have context.
Test navigation and task flow with intended users. Feedback on a simple prototype can prevent expensive revisions later. Document responsibilities so delivery does not depend on assumptions.
Make the plan fit your market
Discuss whether users in Tempe 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. Describe the offer clearly for people comparing providers in Tempe.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. 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