Method
Five stages, one named reviewer, a memo you can file.
This is the path we use for security, privacy, accessibility, performance, store-readiness, and release-readiness work. The depth changes. The order does not.
-
Intake
You send a short note: which review you want, the platforms, a target week, and whether a date is already public. We reply with whether we can take it and what artefacts we need. No booking is made until both sides agree in writing.
-
Scope
We lock journeys, roles, device set, and out-of-scope items. If you cannot provide a jailbroken or rooted handset and you still want that depth, we say so here. The scope note is the document we work from, not the original email.
-
Device week
Builds are installed. Accounts are used. Notes are taken as reproductions, not as impressions. You can be in the studio on Jalan Padi Ria for part of this, or we work from the artefacts and a daily written check-in.
-
Findings workshop
The memo is walked through with the people who will fix items. Severity is explained in the context of your journeys. We do not present a leaderboard. We do agree which items you want retested.
-
Retest
Patched builds come back. We re-run only the agreed items unless a fix clearly creates a new problem in the same journey. The retest note is short and dated.
What we need from you before day one
- Current iOS and Android artefacts, or a TestFlight / internal-testing link that will stay valid for the week
- Test accounts for each role in scope, with a way to reset them
- The privacy notice and store listing drafts if those reviews are included
- A list of the journeys that move money, health, identity, or location
If something cannot be provided, we shrink the scope rather than guess.