Plan for interrupted use
Connections fail, sessions expire, and users leave tasks unfinished. Decide what happens to pending work and show clear recovery steps instead of assuming every action succeeds immediately. Keep a change log so later results have context.
Define what happens to entered data when a request fails or a session expires. Users should not lose work without clear feedback. Document responsibilities so delivery does not depend on assumptions.
Make the plan fit your market
Discuss whether users in Memphis 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. Explain any real service-area limits that affect customers in Memphis.
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Keep a record of permission for any customer story used publicly.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities