
Golf League App
Turning the friction of running a golf league into one connected product for playing, scoring, and coordinating.
0→1 Product Design · Design Engineering · Independent Product
I designed and built the working React application end to end, defining the product model, information architecture, interaction patterns, scoring flows, and shared scheduling states.
AT A GLANCE
ROLE
Lead Designer and Builder
TOOLS
Cursor · React · TypeScript · GitHub · Figma
TIMELINE
June 2026–present
PARTNERS
Independent project informed by golfers and league participants
SCOPE
Personal golf activity · League play · Round setup · Scoring · Handicaps · Makeup scheduling
WHAT I OWNED
Product definition · Information architecture · Interaction design · Visual design · React implementation · Iterative refinement
CHALLENGE
Golf has a familiar rhythm, but the information behind a round can become complicated quickly. The same player may move between casual rounds and league matches while course selection, tees, holes, handicaps, formats, teams, and scheduling all change the context.
Putting everything on screen at once would make a simple round feel administrative. Hiding too much would leave golfers without the information they need.
STRATEGIC SHIFT
The product needed to organize itself around the golfer’s next meaningful action rather than around the underlying data model.
A simple interface needs a clear underlying model.
The design work became less about reducing the number of options and more about making the relationships between rounds, players, teams, courses, and scheduling states explicit enough that the interface could stay simple.
MY ROLE
Coordination requires more than a date field
Scheduling is a progression from suggestion to agreement. Who proposed a date, who confirmed it, and what remains unresolved are all part of the experience.
Familiar language reduces cognitive load
Round, tee box, foursome, and makeup date give golfers a familiar mental model even when the underlying configuration is complex.
Building creates faster feedback
Implementing the experience exposes relationships between screens and states that are easy to overlook in isolated design files.
KEY DECISIONS
Decision 1 — What belongs on the home screen?
The home screen could easily become a dashboard of everything in the product. I organized it instead around three immediate questions: How have I been playing? What is coming up? Is there anything I need to resolve?
Decision 2 — What is the organizing context for league play?
Rather than making players assemble information from standings, schedules, rosters, and scoring screens, the weekly match became the primary context. Format, date, teams, foursome, and scoring all connect back to that moment.
Decision 3 — When is a makeup match actually scheduled?
A proposed date is not the same as an agreed date. I modeled scheduling as a progression from proposal to individual confirmations to shared agreement, with a date locking only when all four players confirm the same proposal.
HOW I WORKED
The current working application establishes a connected model for personal and league context, configurable round setup, scoring, and group coordination.
Makeup scheduling now has explicit shared state rather than relying on a loosely coordinated conversation, and the product provides a concrete basis for usability testing and further refinement.
Adoption, time savings, and usability improvements are not yet established outcomes; validation with golfers and league participants is the next step.
WHAT CHANGED
The current working application establishes a connected model for personal and league context, configurable round setup, scoring, and group coordination.
Makeup scheduling now has explicit shared state rather than relying on a loosely coordinated conversation, and the product provides a concrete basis for usability testing and further refinement.
Adoption, time savings, and usability improvements are not yet established outcomes; validation with golfers and league participants is the next step.
LEARNINGS
Coordination requires more than a date field
Scheduling is a progression from suggestion to agreement. Who proposed a date, who confirmed it, and what remains unresolved are all part of the experience.
Familiar language reduces cognitive load
Round, tee box, foursome, and makeup date give golfers a familiar mental model even when the underlying configuration is complex.
Building creates faster feedback
Implementing the experience exposes relationships between screens and states that are easy to overlook in isolated design files.
CONTRIBUTIONS
Product Design
Product definition · Information architecture · Personal and league workflows · Round setup · Makeup scheduling
Interaction Design
Contextual navigation · Configuration flows · Proposal and confirmation states · Player and team context
Design Engineering
React development · Reusable interface components · Working interaction implementation · Iterative refinement
Visual Design
Golf-focused visual identity · Information hierarchy · Interface consistency · Component styling