An app we take on has a task someone repeats. We design that task before we design a tour of the product. If the network drops, the brief already says what the screen should do.
We choose the stack for the job. Cross-platform is the default when the product does not need a platform-only capability. When it does, we say so at the start.
What a brief can include
- Flutter or React Native when a shared codebase fits
- A single path that works in one hand
- Offline and sync called out in the brief
- A build a stakeholder can install

