← Blog
Series · 5 postsVisit myplaytab.com

Building MyPlayTab

Building a group scoring app from scratch. The decisions, bugs, and why one phone shouldn't be the bottleneck for ten players.

Part 1
4 min read

Why I built MyPlayTab

A scoring artifact I lost by clicking back turned into the design question this whole app answers.

Part 2
5 min read

Who gets to score the match? Keeping every court in sync on PlayTab

Multiple courts, multiple phones, one score that's always right — and the bug that taught me an "obviously unique" sort wasn't.

Part 3
4 min read

One rule, forty AI sessions: how PlayTab stayed one app instead of several

A header color got reverted because a technically-correct fix looked worse. That's the point, not a mistake.

Part 4
4 min read

The login bug that only hit people who'd already logged in before

A real account got bounced back to onboarding as if it had never been set up. It only ever happened mid-login, never after.

Part 5
5 min read

Building the bill-splitter I actually needed for a padel group

Two apps in one, so nobody opens Splitwise after a session. What got built in on purpose — and the one bug three sibling tables had already fixed.