Flagship review
Release readiness review
A ten-working-day reading of how your iOS or Android build behaves on mid-range devices and Malaysian mobile networks before you ship a store update.
Who it is for
Product owners, release managers, and engineering leads who already have a candidate build — TestFlight, internal Android track, or a staged flavour — and a date they cannot move. The review is written for people who must decide whether a listing goes live, not for teams still choosing a programming language.
Result you leave with
A bound findings note (PDF and a shared folder) that names screens, device models, and network conditions. Each finding has a severity, the trace or timing that supports it, and a recommended next action owned by your team. We do not rewrite your code. We do not ship a substitute build.
Scope
Included:
- Intake call (45 minutes) to agree the build, the three user journeys that matter, and the devices we will borrow or that you will post to the studio
- Cold-start timings on at least two Android API levels and one current iPhone, recorded from icon tap to first interactive frame on the agreed home surface
- Crash and ANR cluster reading from the console exports you provide, plus reproduction on our bench where the cluster still occurs
- One commute-style network pass on a Celcom or Maxis SIM in Kuala Lumpur traffic, timed against the same journeys on studio Wi-Fi
- A findings workshop (90 minutes) with whoever will actually change the screens
Excluded:
- Feature design, copywriting, or store-listing creative
- Load tests against your backend at volume we do not control
- 24-hour on-call during the store rollout
- Rewriting native or web code inside your repository
Provider
Aisha Rahman leads the review. Wei Ming Tan runs the device bench. Priya Nair writes the findings note so a non-engineering stakeholder can read the first three pages without a glossary.
Process and timeline
Day 1–2: access, privacy constraints, and a freeze on which build we measure.
Day 3–7: timings, crash reproduction, and the network pass.
Day 8–9: draft note.
Day 10: workshop and a 48-hour window for factual corrections (wrong screen name, wrong device). Severity calls stay ours unless the trace was incomplete.
Location and delivery
Work happens at Level 8, 24 Example Avenue, Kuala Lumpur 00000, or on a video call if devices stay with you. Posted devices should arrive with a charger, a test account that is not a real customer, and a note of any MDM that will lock the phone.
Preparation
You provide: the build, crash console exports for the last 14 days, a list of rooted or jailbroken restrictions, and written permission to collect timings that may include approximate GPS during the commute pass. We do not need production admin rights.
Constraints
We will not install packet-capture certificates on a device that holds live customer payments. If your compliance team forbids that, we time the screens from the outside and say so in the note. Public holidays in Malaysia pause the ten-day clock.
Price basis
From RM 18,400 for one store listing (iOS or Android) and three journeys. A second listing in the same fortnight is quoted separately. Travel inside the Klang Valley is included; a day on-site in Penang or Johor Bahru is billed as a visit (see Rates).
Next step
Write to us with the listing URL, the freeze date, and whether the phones can travel to the studio. Intake is scheduled after we confirm the build is actually installable.