Push Notifications

Characters become relationships, not just voices. Duolingo's cast — Duo, Lily, Oscar, and others — isn't a stylistic choice; it's a relationship-building system. Each character has a recognizable voice and a recurring posture toward the user. Lily writes with sass. Oscar narrates as if writing in a diary: "Dear diary, my apprentice is ignoring me. AGAIN." Duo signs personally: "Hi, it's Duo." Over weeks of practice the user develops something that resembles a relationship with each character. They recognize the voice, anticipate the tone, and open the push because they're curious what Oscar has to say this time. That feeling of "someone I know" is what makes the push convert. Generic brand voice can't manufacture it.

Real-friend pushes activate real social pressure. The second layer is actual users — friend streaks, friend quests, league rivals, peer cheers. The relationships behind them are real: a streak partner who'll be disappointed if the user no-shows, a rival who overtook the user's rank, a peer who reacted to a milestone. Real social pressure outranks self-motivation, and Duolingo wires it into the notification engine. The same delivery system fires both layers, but real-friend pushes carry the heaviest pull because the consequence is visible to someone the user knows. The pattern travels: any app with a real social graph can route pushes from a person, not a brand. The pull is always stronger when it does.

Routine notifs and save notifs split the day. Duolingo's notification system runs two named slot types, codified internally: *routine notifs* and *save notifs*. Routine notifs are the gentle, on-cadence pushes that fire around the user's habit window — a partner nudge, a casual Duo greeting, a low-stakes reminder that names the anchor and steps back. Save notifs are reserved for the moment something is about to be lost — the 10pm streak saver, the last-chance league promotion, the friend streak about to drop. Two slots, two purposes: the routine keeps the channel warm, the save catches imminent loss. Most apps blow this distinction by treating every push as urgent, which fatigues the channel inside weeks; Duolingo holds urgency back for the save and keeps the routine quiet. The discipline is in the split — and in the cap that holds it: two pushes a day, max.

Behavior triggers the cycle, not the clock. Every push has to clear a behavioral or state trigger to fire — there are no scheduled broadcasts. Routine notifs read the user's revealed habit window: they practiced at 6pm yesterday, the push fires at 5:30pm today. Save notifs read the state of the user's commitments: the streak about to expire, the league cycle about to close, the reward about to lapse. Earlier versions of the system asked users to pick their own reminder time, and the result wasn't users getting their preferred time — it was users missing their notifications because, as the team has put it, "life always gets in the way." The fix wasn't smarter user input; it was throwing user input out and reading actual behavior instead. Behavioral and state signals replace the wall clock because they're the only signals that predict whether the user can act on the push when it arrives. A push the user can't act on is wasted reach, and wasted reach is how a channel slowly burns out.