Year in Review Design: How to Build a "Wrapped" Experience
How to design a personal year in review like Spotify Wrapped: choosing stats, story structure, motion, sharing, performance and privacy.
Core Takeaway
A year in review works when it tells each person a short story about themselves: a few surprising stats, revealed one at a time, with motion that makes each reveal feel earned and a final card made to share. Pick stats that flatter and surprise, design for the extremes of your data, keep it fast on phones, and be careful with sensitive data.
Why recaps work
Recaps turn data people already generated into a story about them, and they are made to be shared. Spotify Wrapped, Strava's Year in Sport and LinkedIn's Year in Review all use the same structure: full-screen cards, one idea per card, tap to advance, a shareable summary at the end.
Choose the stats
Good recap stats are personal, positive and a little surprising.
- Totals that feel big: minutes, kilometres, lessons
- Rankings and percentiles, where you can compute them honestly
- A "personality" or label derived from behaviour
- One unexpected detail: first item of the year, most active day
Design for every user, not the demo
The mockup shows a power user. Plan for someone with three data points, for a name that is very long, and for zero values. Decide which cards are skipped when data is thin, and write copy that still feels generous.
Motion and pacing
Each card is a small reveal: build anticipation, show the number, let it land. Counting-up numbers, charts that draw in and characters that react all help. Let people tap to skip ahead, keep each card short, and respect reduced-motion settings with simpler fades.
Sharing, performance and privacy
Design the final card at the exact aspect ratio of the platforms people share to, and render it as an image they can save. Preload the next card while the current one plays. Never put sensitive data on a shareable card by default, and let people hide cards before sharing.
Building this in ExodeUI
ExodeUI, which we make, can power each card as a component with number and text inputs that your recap data fills in, and a state machine for the reveal. Because the design lives in one .exode file, designers can change the motion after launch without new code, and it plays on web, iOS and Android runtimes.
Key Principles to Remember
- One idea per card, tap to advance, a shareable ending
- Pick personal, positive, surprising stats
- Design for thin data, long names and zero values
- Preload cards, allow skipping, respect reduced motion
- Keep sensitive data off shareable cards
Frequently Asked Questions
Sources
- The Role of Animation and Motion in UX — Nielsen Norman Group
- prefers-reduced-motion — MDN Web Docs