duo-retention
Duolingo Retention — Map of Content
Duolingo's central business bet is that retention compounds and acquisition does not. The handbook frames the company as a "forever product": every decision is judged by long-term retention, not short-term revenue. This skill packages that bet into reusable patterns.
This skill is structured as a graph: scan the descriptions below, follow only the [[wikilinks]] you need. Don't read every node up front.
Foundations
- [[references/forever-product]] — the operating premise: optimize for users who stick around for years, not quarters.
- [[references/habit-loop]] — trigger → action → variable reward → investment, the spine of every retention move.
- [[references/retention-vs-revenue]] — the explicit tradeoff Duolingo makes (and limits) between monetization and long-term return.
Behavioral mechanics
- [[references/streak-mechanics]] — the daily-counter habit engine that became the company's icon.
- [[references/streak-freeze]] — why protecting the streak is the retention move, not the gentle one.
- [[references/loss-aversion]] — the asymmetry that makes streaks work: losing hurts more than winning feels good.
- [[references/variable-reward]] — unpredictable payoffs (chests, league finishes) outperform predictable ones.
- [[references/friction-as-stickiness]] — small required actions that build identity and habit.
More from hktitan/duolingo
duo-product
Make product decisions the way Duolingo does — long-view over short-term, ruthless prioritization, ship-and-learn over plan-and-ship, dogfooding, and the "intuitive by default" quality bar. Use when the user is roadmapping, deciding what to cut, debating whether to ship, defining a quality bar for a feature, or trying to install a "product-led" culture in a team that defaults to feature factories. Source the Duolingo Handbook principles 1, 2, and 3 (Take the Long View, Raise the Bar, Ship It).
4duo-voice
Write product copy in the Duolingo voice — "wholesome but unhinged," character-driven, screenshot-worthy. Covers push notifications, error states, onboarding, empty states, celebrations, and the now-famous threat-copy that turned a green owl into a meme. Use when the user is writing any user-facing string — notifications, microcopy, errors, marketing — and wants it to feel like a person, not a product. Source the Duolingo Handbook (Make It Fun) and observed blog/marketing patterns.
4duo-design
UI patterns from the Duolingo design system — juicy motion, the character system as the emotional channel, design tokens (color/type/spacing), sound as a UX surface, accessibility as a default not a checklist, and "error-as-delight" detailing. Use when the user is designing a screen for a gamified or learning product, reviewing a design for "why does this feel flat," picking a motion system, building a character mascot, or auditing for accessibility. Source the Duolingo design system at design.duolingo.com.
4duo-growth
Duolingo-style growth that doesn't break retention — viral loops, brand-as-acquisition (the TikTok playbook), referral mechanics, localization as a growth lever, and the founder-mode marketing that turned a mascot into a meme. Use when the user is planning acquisition, building a referral system, considering paid vs. organic, evaluating a marketing channel, or trying to turn an existing brand into a growth engine. Source the Duolingo Handbook (Make It Fun) and observed marketing patterns from 2022–2025.
3duo-gamification
Add Duolingo-style play to any product — XP systems, juicy feedback, leagues, celebration moments, hearts/energy, and the anti-grind discipline that keeps gamification from turning toxic. Use when the user asks how to make a product fun, addictive, or "feel like a game," when designing rewards, levels, or progress, or when an existing system feels like a slot machine and they want it to feel like a craft. Source the Duolingo Handbook (Make It Fun) and the Duolingo design system.
3duo-culture
Build the team the way Duolingo built theirs — the Green Machine operating model, talent density over headcount, candor protocol ("focus on what, not who"), hire-slow / fire-fast, and the "no process unless it makes decisions better" rule. Use when the user is hiring, defining team rituals, debating remote vs. office, choosing a feedback model, or installing an operating system in a team that has none. Source the Duolingo Handbook (Raise the Bar + Green Machine).
3