Work / Handy Golf

A golf web app grew into an ecosystem

What started as a relatively small golf product expanded into apps for golfers and coaches, a content library, and coach website templates. I designed the different parts as they emerged, keeping them connected across platforms, audiences, and visual themes.

Role
Head of Design
Scope
Product design across the ecosystem
Period
2023 — 2026
Platforms
iOS · Web
Tap to enlarge ↗ Four product surfaces across iOS and web.
2+ years One designer across every surface
4 surfaces Golfer app, Coach app, HowTo Library, and Coach Website Template
One ecosystem A shared visual language adapted to each environment
THE BEGINNING

A simple idea for learning golf

The project started with a relatively simple idea for a golf web app: a structured way to learn through lessons, series, and other golf content.

Tap to enlarge ↗ The original web app, before practice tools, coaching, and the content library were added.

Designing While It Was Moving

The product was still taking shape while I was designing it. New platforms, audiences, features, and needs kept appearing along the way, so the design had to evolve with them without losing sight of what was already there. I was the only designer on the product, and there was no process to fall back on. Plans were rewritten most months. The structure underneath had to hold, because every new surface started from it.

THE REFACTOR

I stopped adding to the library

After one year of additions, the component library needed a different approach. I drew a line across the components page, kept the old system on one side because the shipping app still depended on it, and built the new one on the other. That boundary stayed in place for months. Every component that crossed it was rebuilt.

The activity card was one example. Nine variations had accumulated, each with its own structure. I rebuilt the component around three shapes, three background options, and 13 shared properties, allowing the same card to adapt to different states.

Tap to enlarge ↗ A 21,381-pixel divider across the components page, with OLD on one side and NEW on the other.
Tap to enlarge ↗ Nine variations on the old side. Three shapes and three backgrounds on the new one.
THE EXPANSION

From web app to native

The web app became a native iOS experience, expanding from structured learning into practice tools, games, swing analysis, and recording.

Tap to enlarge ↗ The native app introduced a new way to explore the learning content.
Tap to enlarge ↗ Recording, games, swing analyzer, and practice tools were added alongside the existing learning content.
A NEW CHARACTER

Coaches found a place in the product

The Coach App gave coaches a place to create their own services — from in-person lessons and swing analysis to online lessons — and define how and where they worked. They could also create their own website directly from the app.

The coach app runs on the same component library as the golfer app. Thirty-seven semantic tokens sit under both, and five carry a different value: three backgrounds and two text colors. The text values are adjusted to hold contrast against the coach’s darker background.

Tap to enlarge ↗ Five of thirty-seven semantic tokens change value between the two apps. The rest are marked same.

A site built from connected pieces

I designed three interconnected flows within the Coach App: Coach Profile, Services, and Website Management.

Each serves a distinct purpose. Coach Profile gives coaches a public presence in the Golfer App while also providing information for their websites. Services lets coaches manage their offerings for the Handy Golf marketplace and choose which ones to publish on their websites.

Website Management brings these pieces together, allowing coaches to shape their websites without duplicating content. When information needs updating, contextual shortcuts take them directly to the flow where it’s managed.

Each flow works independently, but together they form a connected system.

Tap to enlarge ↗ Website assembly process inside the app, no design knowledge or special skills to build
Tap to enlarge ↗ Website management flows
CONTENT LIBRARY

Learning became part of the product itself

The HowTo Library connected golf problems with the tools that could help solve them. A golfer could discover a fix on the web and see how Handy Golf could help, or find the same guidance directly from the relevant feature inside the app.

Tap to enlarge ↗ The library covers both feature guidance and golf instruction, organized across four content types.
THE ECOSYSTEM

How everything connects

Four connected surfaces, each with its own role, platform, and audience.

Tap to enlarge ↗ One set of foundations under two libraries, and the surfaces that come off them.
Tap to enlarge ↗ The mobile design system and component library, shared by the golfer and coach apps.
Tap to enlarge ↗ The web design system and component library, shared by the content library and the coach website template. The type scale is identical in both files, item by item.
RESULT

What shipped, and what didn’t

The golfer app is on the App Store, now as a paid app. The free version that preceded it passed five thousand downloads. It carries lessons, drills, games, and the first version of the marketplace.

The HowTo Library is live on the web.

The coach app and the website template were designed in full and built in part. They haven’t been released.