Custom map

The Mobile KPI Atlas

A public sketch of how Logicauditgrid stacks mobile performance KPI frameworks. It is not a vendor scorecard. It is a way to keep health, start-up, session, retention, and store signals from collapsing into one vanity number.

Team sketching a framework on a whiteboard

How to read it

Lower layers may veto the layer above.

If crash or silent failure is on fire, retention theatre is not a strategy. If cold start misses the budget on 4G, store conversion will lie. The Atlas is a veto stack, not a balanced scorecard.

Store loop Listing conversion, ranking, screenshot honesty, Thai metadata. Only meaningful if first open completes.
Retention map Cohorts by job, not blended DAU. Explicit festival and payday windows.
Session health Job completion versus foreground time versus background pings.
Device health Crash, ANR, hang, silent failure, cold start. Separate rooms. No composite index.

Rooms on the atlas

Crash-free sessions

Useful as a floor, dangerous as a north star. Must be paired with silent failure (uploads that die without a crash) especially on dual-SIM devices common in Thailand.

ANR & hang time

ANR rate answers “did the OS notice?” Hang time answers “did the human notice?” Putting only ANR on an exec slide hides jank that never trips the watchdog.

Cold start / TTI

First paint is not interactive. Budgets should cite the network they were measured on. Commute 4G in secondary cities is a better default than the studio office.

Job completion

The session metric that usually belongs on the Monday slide. Define the job in the event contract. “Opened the app” is not a job.

Retention by job

Split searchers from posters, riders from drivers, readers from writers. Blended day-7 is how Bangkok volume hides provincial supply collapse.

Store conversion

A product loop, not a marketing sidecar. If the listing promises two taps and the first screen needs a 12MB download, the KPI is a complaint in disguise.

What the Atlas refuses

No composite “health scores.” No DAU as a weekly ritual by default.

Composite indices hide vetoes. DAU can be a research question; it is rarely the sentence you should say first on Monday. If your board still leads with either, the studio will spend week one taking them off the slide — not decorating them.

The Atlas is taught in full inside Signal Architecture Studio and sketched in Field Ledger notes.

Use it

Print it. Argue with it. Then enrol or don’t.

You are welcome to adopt the veto stack without becoming a student. If you want faculty to mark your live board against it, request a Cohort Bench seat or a War Room.

See programmes   Write to the studio