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. Agree whether the evidence supports keeping, changing, or stopping the approach.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Separate essential work from optional additions in the proposal.
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. Use only the customer information needed for the agreed work.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Agree how new requests will affect cost and timing.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities