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. Keep the next round of work small enough to assess clearly.
Test both platforms where supported, including navigation, permissions, notifications, and accessible controls. A working build on one device is not enough. Check that a visitor can find the next action without guessing.
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. A written brief should explain what will change and what will stay.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities