Start with the user's task
Define the problem a user needs to solve before listing screens or features. Check the current process, the devices involved, and the places where an app would remove real effort. Save a baseline before replacing an existing approach.
Test both platforms where supported, including navigation, permissions, notifications, and accessible controls. A working build on one device is not enough. Choose a decision maker who can resolve conflicting feedback.
Make the plan fit your market
Discuss whether users in Portland 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. Use verified business information when addressing the Portland audience.
Describe users, tasks, data, and acceptance criteria before choosing technology. A short working prototype can reveal workflow problems earlier than a detailed visual design. 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