Daily Streaks System Implementation in Mobile Applications
Streaks are one of the most powerful retention mechanics in mobile apps. Losing a 30-day streak hurts. That's exactly what keeps users returning even when the direct app value has dropped. But implementation is full of subtle bugs that break everything.
Main Technical Complexity — Time and Timezones
The critical question to solve upfront: by what time should we count a "day"? Options:
User's Local Time. Streak doesn't break if user is in Tokyo and server in UTC. Requires storing timezone and recalculating "today" on each check. Timezone changes (flights) can create artifacts.
UTC Midnight. Simpler technically, but unfair to users in UTC-5 — their "yesterday" ends at 7am UTC, not midnight in their time.
Rolling 24-Hour Window. Not "today" but "within last 24 hours from last action". Fairest approach but breaks intuition of "daily" streaks.
In practice, most successful apps (Duolingo, Headspace) use local time with stored user_timezone. Detect TimeZone.current at first launch, save to server.
Data Model
user_streak:
user_id UUID
current_streak INT
longest_streak INT
last_activity DATE -- store DATE, not TIMESTAMP
updated_at TIMESTAMP
last_activity is date in user's timezone, not UTC timestamp. This is key. On streak check:
today = current_date_in_user_timezone(user.timezone)
days_since = today - last_activity
if days_since == 0: streak active, nothing (already marked today)
if days_since == 1: streak continues, current_streak += 1
if days_since > 1: streak broken, current_streak = 1
Atomic update via SQL with RETURNING — protection from concurrent requests.
Freeze and Streak Recovery
Losing a streak is painful. Some apps offer "streak freezes" (streak freeze): user can skip a day without losing the series. Increases retention on missed days.
streak_freeze is separate resource user gets as reward or buys. On broken streak check: is there active freeze for yesterday. If yes — don't break streak, consume freeze.
Streak recovery (paid feature in some apps) is technically simpler, ethically spottier. If implementing: streak_restore_purchase, set new last_activity = yesterday, current_streak = pre_break_value.
Notifications
Reminder before midnight (e.g. 9pm local time) — "You haven't completed task today, X-day streak at risk". These notifications are highly effective but need personalization: user who's always active at 8am shouldn't get reminder at 9pm.
On iOS: UNUserNotificationCenter with UNCalendarNotificationTrigger. Calculate time in user timezone. Update trigger on activity — if user already completed today, cancel today's reminder.
Visualization
Flame icon with number is standard. On Flutter: AnimatedFlipCounter for smooth count increase. Weekly grid of days (like GitHub contribution graph) — shows last 7/30 days history. Powerful: empty cells visually "call" to fill them.
Milestone Notifications
7 days, 30 days, 100 days — special events with animation. Integrate with achievements: milestone streak = auto-unlocked achievement.
Timeline Guidelines
Basic system with streak, notifications and milestones — 1–2 days (client) + 2–3 days (backend). With freezes, recovery, personalized reminders and achievement integration — 1–2 weeks. Pricing is calculated individually.