Discovery & technical scoping
What the engagement includes
- User journeys and prioritised feature list
- Screen and interaction requirements
- Integration and access requirements
- Development, testing and support scope
Mobile app discovery & technical scoping
Define the app before committing to development.
Clarify who will use it, the tasks it must support and whether an app is the right approach.
This engagement defines the app and a delivery path. Production development requires a validated platform or delivery partner and a separately agreed development, testing and support scope.
App journey
Define the task before defining screens.
Move through the discovery chain to see what an app brief needs to make visible.
Name the person, context and access conditions.
Different users may require different journeys, permissions, devices and accessibility support.
Define the outcome the user must complete.
Start with essential tasks and the exceptions that would block a successful journey.
Design screens around decisions and feedback.
Each screen should make the next action, current status and error recovery understandable.
Identify what is captured, retrieved and shared.
Record validation, ownership, privacy, integrations and offline needs before estimating development.
Plan releases, administration and user support.
Clarify platform accounts, monitoring, issue ownership, updates and long-term maintenance.
Scope control
Agree the scope first.
Production development requires a validated platform or delivery partner; it is not part of the startup website package.
The accepted quotation records deliverables, inputs, review points and support. Review the delivery controls.
Example discovery output
Illustrative journey: user identifies a request → enters the agreed details → reviews the summary → receives a status or a recoverable error. Discovery records the screen requirements, roles, data and integrations. It does not imply a supported native app or app-store release has already been delivered.