Module 05 finally gave us a fixture that reproduced the Asok handoff. We had been blaming the image pipeline for a pause that was radio all along.
Flagship programme
Field Benchmark Mastery
Six modules that teach Mobile Performance Benchmark Analytics as a reporting craft: you leave able to defend a number in a launch review, and to withdraw it when the trace does not support it.
Modules
01
Trace literacy
Open a capture without drowning. You learn which threads matter, which clocks lie, and how to annotate a trace so a teammate can replay your argument next week.
02
Cold start decomposition
Split process birth, class load, first draw, and first useful interaction. The homework is a three-slice chart, not a single TTFD trophy.
03
Jank budgets under thermal load
Run the same scroll after a 12-minute soak. We compare a cool lab phone with one that has been in a Bangkok bag, then set a budget product can actually keep.
04
Battery attribution without folklore
Pair battery historian output with radio traces. You practise saying “this wake is radio, this one is a misplaced alarm” without guessing.
05
Carrier-aware network fixtures
Replay Thai 4G jitter, a 5G-to-4G handoff, and hotel Wi‑Fi that advertises high bandwidth with poor latency. Lab stopwatches finally disagree usefully with the field.
06
Reporting without vanity scores
Write a one-page launch note: what was measured, what was excluded, what would falsify the claim. Stakeholders get a ledger, not a slogan.
Learning outcomes
- Publish a cold-start report with three named slices and exclusion rules.
- Set a jank budget that still holds after thermal soak on mid-range hardware.
- Attribute a battery regression to radio, CPU, or a misplaced wake with paired traces.
- Build one carrier fixture from a Thai field capture and document its limits.
- Refuse a vanity score in writing when the trace cannot support it.
Informational pricing
This page does not process payment. Seats are invoiced after a note to the desk.
฿24,500
Bench Lead seat: six live sessions, office hours, and access to the teaching trace archive. Trace Reader notes-only access is listed on pricing. Studio Residency is a separate on-site week.
Instructor
Waranya Srisuk
Wan ran drive-test crews before she ran classrooms. She still prefers a trace that smells like traffic to a synthetic benchmark that only works in air-conditioning. Learners meet her in office hours with their own captures; she marks what the trace cannot prove as carefully as what it can.
Questions we actually get
Do I need to be an Android specialist?
You should be comfortable opening a profiler and reading a stack. We do not teach Kotlin from zero. Product partners can join Frame Timing for Product Teams instead.
What does this course not cover?
We do not teach native game-engine profiling (Unity or Unreal) in any depth. The lab stays on mobile app runtimes and webviews. If your bottleneck lives inside a game loop, this syllabus will leave that work untouched — that is a real limitation, not a “coming soon” slide.
Are the traces from Thailand only?
Teaching captures are mostly Thai carrier logs plus a smaller set from travel weeks. You may bring your own region’s traces to office hours; we will not pretend a Bangkok fixture is universal.
Is there a certificate?
You receive a completion note listing modules finished and the protocol you submitted. We do not sell badges. The useful artefact is the protocol itself.
Voices from this syllabus
★★★★☆
Dense, occasionally dry, and the homework volume is real. I used the launch-note template from module 06 the following Tuesday.
Ask about this programme
Tell us your runtime (Android, iOS, webview) and whether you need a Bench Lead seat or notes-only access. We reply within two working days.