Daily trivia inside World App
I designed a daily trivia game for 30,000+ verified users inside World App. The challenge was making something people come back to every single day, in under 60 seconds.
Quizzly shipped in two months, reached 30,941 players, and was featured as a “must play” app inside the World App ecosystem.
I owned the entire design process, from product concept through final UI, working directly with developers to ship it.
A one-minute game
Most trivia apps try to keep you playing for 20 minutes. I wanted Quizzly to take less than one.
That constraint shaped every design decision. The entire experience needed to fit inside a tight loop:
- Open the app
- Answer 10 questions
- See your score
- Check the leaderboard
I tested different question counts early on. Five felt too quick, players didn't feel like they earned their score. Fifteen dragged. Ten was the threshold where it still felt fast but the result carried weight.
Each question appears alone on screen with four answers. No progress bars, no timers, no distractions. The interface disappears so the questions can do their job.
Designing the daily loop
A short game is easy to forget. The real design problem was giving people a reason to open Quizzly again tomorrow.
The leaderboard was the answer. I designed it to reset regularly so new players always have a real shot at ranking. This turned a solo experience into a quiet competition, players checking back not just to play, but to see where they stand.
I also built a difficulty curve into each quiz. Early questions are confidence builders. By question seven or eight, players are genuinely thinking. That tension between “I know this” and “wait, do I?” is what makes a score feel earned.
Categories span general knowledge, geography, science, and sports. Enough variety that the quiz never feels repetitive, even after weeks of daily play.
Shipping inside an ecosystem
Quizzly doesn't live on its own. It runs inside World App, which meant designing for someone else's container. Every screen had to load fast, feel native to the host app, and work within constraints I didn't control.
I worked in short loops with the dev team. Instead of long handoffs, I would design something, test it inside the actual ecosystem, adjust, and ship. This let me catch issues that only surface in context, like how the interface felt when opened mid-scroll inside World App.
The two-month timeline forced hard decisions. I cut a friends-only leaderboard, a streak notification system, and custom avatars. Each one was a good idea on its own, but none were essential to the core loop. Shipping something focused mattered more than shipping everything.
What happened
The daily loop worked. Players return consistently, and the leaderboard reset keeps competition fresh week after week.
If I were to revisit it, I'd add the social features I cut: friend challenges and shared scores. The foundation is there. The core just needed to ship first.
