The protocol, step by step.
Every engagement follows the same written method. You can stop after any step and keep everything produced so far.
Brief and hypothesis
A structured conversation about what you are trying to change and how you would know it had worked. We write a one-page hypothesis: who the product serves, the behaviour it should produce and the measure we will watch.
Record produced: Hypothesis sheet
Controlled scope
We split the idea into what must be in the first release and what can wait. Each item gets an estimate and a risk note. Variables we cannot control — third-party APIs, store policy, data access — are named early.
Record produced: Scope register with risks
Prototype
Clickable prototypes tested with a handful of representative users. Findings are written up and the design is revised before engineering begins.
Record produced: Prototype and findings
Build in short cycles
Fortnightly cycles with a working build at the end of each, delivered to TestFlight or a Play internal track. Code lives in your repository from day one.
Record produced: Builds, changelog, test results
Release
Store submission, review responses and a staged rollout where the platform allows it. We check privacy disclosures against what the app actually does.
Record produced: Release checklist and notes
Observe and maintain
After launch we watch crash reports and feedback, agree a maintenance rhythm and keep the lab notebook current so any future team can pick it up.
Record produced: Maintenance log