Journal · 7 min · Studio desk
Feature adoption on mixed platforms
A feature that exists on iOS, web, and a desktop plugin is three features wearing one name. App Analytics tools will still offer you a single adoption rate. Take it and you will brief a room that cannot assign work.
Define adopted
Opening a screen is not adoption. Completing the job the feature was built for is closer. Write that job in one sentence and map it to events that exist on each platform. If desktop cannot emit the completion event, you do not have mixed-platform adoption; you have mixed-platform curiosity.
Do not average the join key
If identity does not stitch across clients, you cannot say “users.” You can say “sessions on iOS” and “accounts on web.” In a midlands publisher case on the Voices page, Experiment Measurement Lab stopped a test until a join key existed. That decision looked like delay. It was cheaper than a quarter of noisy lifts.
Flags and exposure
Adoption among people who never saw the feature is a ghost number. Exposure must be an event or a flag check you trust. If the flag lives in a vendor the analytics tool cannot see, say “unknown exposure” in the brief. Unknown is allowed. Hidden is not.
The Signal Atlas page on this site is the longer method: surfaces, jobs, and windows on one sheet. Use it before you ask for a lift.