Adoption Signals
The flagship: instrument first-use, set an adoption floor, and write a readout a product council can refuse or fund.
Open the syllabusEvening studio · Asoke, Bangkok
Prove a feature was taken up, not merely shipped.
Devtracebase is a small school for app analytics practitioners who need a durable way to measure feature adoption. We work from production event streams, cohort windows, and the awkward middle between first tap and habitual use.
2,180practitioners taught since the Asoke studio opened
71%of alumni still use the event map template after six months
38Thai product teams in the last Bangkok evening intake
“The ‘exposure versus trial’ module stopped our squad from celebrating a banner click-through that never became a second session.”
“I still disagree with how strict the habitual-use window is for a monthly billing product, but the taxonomy audit alone paid for the seat.”
Studio programmes
Three rooms, one measurement problem
Each programme is built around feature adoption measurement inside live apps. Browse the catalogue or go straight to the flagship.
Event Taxonomy for Mobile Teams
Name events so exposure, trial, and habit can be reconstructed later without a forensic project.
See all programmes
Cohort Windows After Regional Launch
Read Thailand and SEA cohort curves when store timing, language packs, and payment rails do not land together.
See all programmesHow the room works
We teach with your production questions, not a toy demo app.
- Bring one live feature. If you cannot name it on day one, we help you pick a bounded surface.
- Map exposure, trial, and habitual use in the actual event stream, including the gaps.
- Write a one-page readout with an adoption floor and a recommendation the council can argue with.
What you leave holding
A signed-off event map, a cohort recipe you can rerun after the next release, and language for saying “this feature did not cross the floor” without turning the meeting into theatre.
Classes meet in Asoke on weekday evenings. Remote seats exist for teams outside Bangkok, with the same critique cadence.
Why teams sit with us
Measurement that survives the next redesign
Adoption, not activation
Activation rate for the whole app hides whether a new surface was actually taken up. We separate first-open health from feature-level uptake.
Floors, not trophies
Every flagship student sets a pre-agreed adoption floor. Missing it is a result, not a failure of storytelling.
Thailand-aware telemetry
LINE deep links, dual-language clients, and delayed payment methods change when “exposed” even begins. We treat that as part of the instrument, not a footnote.
From the journal
Recent notes on uptake
Why activation rate is a poor proxy for feature adoption
A high first-week activation can sit next to a feature nobody returned to.
Instrumenting first-use without drowning in noise
Three events, not thirty, if you want trial to remain readable.
Reading Thailand-market cohort curves after a regional launch
Store date and language pack date are rarely the same day.
Ask for a seat, or send the feature you cannot yet measure.
Replies usually go out within two working days. Evening visits to the Asoke studio are by appointment.