duo-gamification
Duolingo Gamification — Map of Content
Duolingo's Make It Fun principle isn't a sprinkle of rewards on top of a serious product. It's the load-bearing decision: a low-motivation activity (studying) was wrapped in mechanics borrowed from games until learners showed up daily without willpower.
This skill is structured as a graph: scan the descriptions below, follow only the [[wikilinks]] you need.
Feedback layer (where "juicy" lives)
- [[references/juicy-feedback]] — the bouncy, sound-rich response to every correct answer that turns a checkbox into a moment.
- [[references/celebration-moments]] — bigger payoffs at session/level/streak boundaries; how often, how loud, how to keep them surprising.
- [[references/character-reactions]] — Duo, Lily, Eddy: characters as the emotional channel for feedback.
Progression layer
- [[references/xp-system]] — the abstract currency that lets every action contribute to a single forward-motion metric.
- [[references/progression-design]] — units, sections, paths: how the visible structure of progress shapes effort.
- [[references/ramp-up-difficulty]] — flow-state pacing: never too easy, never a wall.
Constraint layer (where "fun" gets serious)
More from hktitan/duolingo
duo-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.
3duo-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).
3duo-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.
3duo-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.
2duo-retention
Duolingo-style retention engineering for any product — habit loops, streaks, leagues, churn diagnostics, day-N drop-off, and the discipline of building a "forever product." Use when the user asks how to keep users coming back, debug churn, design a streak system, time push notifications, run a leaderboard, or shift a product's metric from acquisition to retention. Source the Duolingo Handbook (Take the Long View) and blog data posts; translate every pattern to the user's actual product.
2duo-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).
2