Control the maintenance burden
Frameworks, libraries, devices, and operating systems change. Document dependencies and update responsibilities so ongoing compatibility is part of the plan rather than an unexpected expense. End each review with a named next step.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Agree how new requests will affect cost and timing.
Data and permissions
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Check the rights to photographs, quotations, and licensed material.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Keep the scope specific enough to check at each review.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities