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.
Check maintained packages, permissions, licenses, and required device features. Dependencies need an upgrade and support plan. Separate production, approval, and publishing responsibilities.
Make the plan fit your market
Discuss whether users in Albuquerque 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. Make practical service details easy for customers in Albuquerque to find.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Agree a secure handover process for accounts and source files.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities