Library Adoption Signals
Learn to design, interpret, and ritualize application analytics for developer library engagement — from first import to multi-version habit.
Modules
About six weeks at a steady pace; Atlas Circle adds live clinics between modules.
Questions before events
Map decisions your library team actually makes, then derive the minimum signal set.
Event vocabularies
Naming, versioning, and deprecation so history survives API churn.
Arrival, fit, and habit
Separate funnels for install success, API fit, and repeated productive use.
Quiet failures
Instrument swallowed errors and retries without turning SDKs into spyware.
Adoption scorecards
Build a board executives can read in three minutes without losing nuance.
Weekly rituals
Facilitation scripts, decision logs, and when to stop measuring.
Learning outcomes
- Publish a versioned event catalog for one library
- Define “first productive use” for your domain
- Ship an adoption scorecard with explicit limitations
- Run a 45-minute weekly review that ends in decisions
- Explain sampling and privacy trade-offs to non-engineers
Informational pricing
Self-paced access aligns with Pulse Desk (₩420,000 / seat). Live studio delivery is part of Atlas Circle. No checkout on this site — contact us to enroll.
Instructor · Sora Kim
Former DX lead for a widely used Korean open-source HTTP stack. Sora designs Studio Circle critiques and hosts Gangneung office hours.
FAQ
Do I need a production warehouse already?
Helpful but not required. We provide CSV-backed exercises. Moving to BigQuery or Snowflake is illustrated, not mandated.
Is this suitable for mobile SDKs?
Concepts transfer, but crash symbolication and store analytics are out of scope. Treat that as a real limitation — bring a mobile specialist if those are your primary surfaces.
How much time per week?
Plan five focused hours: one essay, one studio task, and peer critique.
What language is instruction in?
Primary materials and live clinics are English. Optional Korean office hours are available for Atlas Circle and Observatory Lab.
Course reviews
“The quiet failures module changed how we triage support. We still argue about PII redaction — in a good way.”Ravi · Singapore
Sora’s scorecard critique was blunt: our first draft celebrated volume. Second draft told a release story. That sting was useful.Elena V. · Developer experience manager