Designing a Family Leaderboard With My Daughters as QA

Designing a Family Leaderboard With My Daughters as QA

12 November 2026

Math Buddies is getting a family leaderboard. A weekly XP and accuracy race across profiles, parent-gated, local only, derived at render time from the streak history the app already keeps. No new storage, no accounts, no server. It was my daughters' pick from three options, and it was designed in one of our weekly family build sessions, with the girls as QA.

This post is about how we designed it, what the rules are, and why the constraints matter more than the feature.

What we cover

  • Why a leaderboard, and why this one
  • The rules we set
  • How it works under the hood
  • What the family session decided
  • What we are watching for

Why a leaderboard, and why this one

The idea came from the girls. They wanted to race each other, not just practice alone. A leaderboard turns solo practice into a family event, and a weekly race gives the week a shape: practice during the week, see where you stand on Sunday.

It beat the other two options on the table, an iOS home-screen widget and printable certificates, because it is social. A widget is private. A certificate is a one-time reward. A race is something the whole family does together, every week.

The rules we set

Four rules, set before any code:

  • Weekly. The race resets every week, so a bad Monday does not ruin the month, and a new player is never hopelessly behind.
  • XP and accuracy, not just XP. Speed alone would reward rushing. Accuracy keeps the race honest: fast and sloppy loses to steady and right.
  • Parent-gated. A parent turns it on. Kids do not opt themselves into a competition, and a parent can turn it off without a fight.
  • Local only. No accounts, no server, no data leaving the device. The leaderboard lives on the family iPad, where the family is.

The local-only rule is the one I care about most. A kids app should not need a server to run a family race. The data is already on the device. Use it there.

How it works under the hood

The leaderboard is derived at render time from per-day streak history. That is the elegant part: nothing new is stored. The app already tracks streaks per day per profile, so the weekly race is a view over data that exists, not a new system to maintain.

No new storage keys, no migration, no sync logic. The leaderboard reads the streak history, adds up the week, and shows the standings. When the week resets, the view resets, because the data it reads is per-day by nature.

That simplicity is a feature. A leaderboard that needs a backend is a leaderboard that can break, leak, or cost money to run. This one cannot, because there is nothing to run.

What the family session decided

The design happened in a family build session, the weekly meeting where the girls decide where Math Buddies goes next. They are the app's QA, and they test everything before it ships.

What came out of the session was the shape of the race: weekly, across profiles, with accuracy counting as much as XP. The girls wanted it to feel like a race, not a report card. That distinction drove the design more than any technical decision. A report card ranks you. A race invites you to try again next week.

I wrote about how those sessions work here: Building Math Buddies With My Daughters as QA. The short version is that two girls, ages 8 and 11, are better QA than any test plan I have ever written.

What we are watching for

Three things, once it ships. Does the weekly reset keep it friendly, or does someone start dreading Sunday? Does accuracy keep the race honest, or do the girls find a way to game it? And does the race make practice more fun, or does it make practice feel like a chore with a scoreboard?

If the answer to that last one is chore, the feature comes out. A leaderboard that makes math less fun is a leaderboard that failed, no matter how well it is built.

Final thoughts

A family leaderboard is a small feature with big rules. Weekly, parent-gated, local only, derived from data that already exists. The constraints are the design. Take them away and you have a different feature, and not a better one.

The short version: a weekly XP and accuracy race across profiles, parent-gated, local only, and derived from streak history the app already keeps, designed with the girls in a family build session.

/blog/2026-11/designing-family-leaderboard-my-daughters-qa austin.amento.dev