retention-streak-mechanic-design

Overview

A streak tracks how many consecutive periods (usually days) a user performs a core action. When designed correctly, streaks leverage human psychology—specifically loss aversion—to turn a casual user into a power user. This skill focuses on the "bend, don't break" philosophy used to scale Duolingo to 9 million+ users with year-long streaks.

Core Principles

• Identify the "Unit of Use": Define the smallest, most comprehensible action that counts as engagement. (e.g., Doing one lesson, not earning 50 points).
• The Seven-Day Threshold: Focus disproportionately on getting users from Day 0 to Day 7. Loss aversion significantly peaks after one week of consistency.
• Sanctity vs. Flexibility: Balance "Streak Freezes" (insurance) with "Perfect Streaks" (rewards for zero freezes) to keep the mechanic meaningful.

Implementation Workflow

1. Define the Action and the Cycle

Identify the specific behavior you want to habituate.

• Set the frequency: Match the natural frequency of the value proposition. While Duolingo uses daily, a fitness app might use weekly streaks.
• Simplify the requirement: Avoid complex goals early on. Move from "Reach a specific XP goal" to "Complete one unit of content."