Case study · Side project
Juice Bros
The problem
Juice Bros is a pickleball media brand with a podcast. It needed a website, and I'm the only engineer on it.
That made scope the problem: a deliberately tight MVP that one person could ship, with content structured so the site could grow without a CMS.
What I did
I scoped a deliberately tight MVP, chose the stack and built the site. I integrated the podcast's YouTube feed and a Beehiiv newsletter.
On top of that I built a suite of free web tools for pickleball players, the Player tools below.


Approach
The stack is Next.js App Router, TypeScript, Tailwind, shadcn/ui and Vercel. I modeled content as typed data, so the site can grow without a CMS.
I built the tools for my own play, and they live on the same site as the show.
Player tools
Booking Buddy
Poll your group on a time, then keep everyone's court bookings in one place. Needs an account. These are its public entry screens.

Desktop width 
Phone width Pickle Point Pal
Keep score and track serves like a referee: the three-number score call, server one or two, and side-outs, with every tap undoable. No sign-up. The phone view is held sideways, as it's meant to be.

Desktop width 
Phone width Match Mixer
Paste your player list and get a doubles round robin where nobody partners the same person twice. No sign-up, and nothing you type is kept on a server.

Desktop width 
Phone width On Deck
Live court rotation for club socials: players scan a sign to join the queue, and it calls the next foursome as courts free up. Organizers need an account, players don't. These are from the demo night, which needs no sign-up.

Desktop width 
Phone width Drum Roll
Spin a wheel to pick a name, or add prizes and run the whole raffle. No paper tickets. No sign-up.

Desktop width 
Phone width
Outcome
Juice Bros is live. I built it, I run it, and I'm its only engineer. I built the Player tools for my own play.
The live site is the proof, and the source is public.
