18birdies
A speculative visual refresh for the top-rated golf GPS app closing the gap between genuinely excellent tech and an interface its own reviewers call cluttered.
4.9★ across 245,000+ reviews and Apple's pick for best golf app but recent reviews keep flagging the same thing: UI bloat and clutter.
One dominant number per screen, a calmer color system, and a mark that reads as instrument, not feature dump.
A new mark and color system, two redesigned core screens, and one marketing asset applying it.
The opportunity
18Birdies earns its reputation honestly: accurate GPS across tens of thousands of courses, a well-reviewed AI coach, and a devoted base of reviewers. Apple has called it the best app for golfers, and it holds a 4.9-star average across more than 245,000 App Store reviews.
But reading through recent reviews turns up a consistent second note underneath the praise: the app has grown noisy. "UX bloat and UI changes" sits alongside pricing as the most common complaint theme, and specific reviews back it up: one described the premium tier as cluttered with extras that complicate simple tasks; another called a basic layout choice rushed and messy.
None of this is a technology problem. It's a hierarchy problem and a hierarchy problem is a design problem.
Scope note: this concept focuses on visual and information hierarchy. It doesn't try to solve the subscription-price complaints also common in reviews that's a business-model question a brand refresh can't answer on its own.
My approach
This is a self-directed concept, not client work; I have no relationship with 18Birdies LLC. I picked it because the gap between "excellent data" and "exhausting interface" is a common one in sports-tech apps, and it gave me a real, sourced problem to design against instead of an invented brief.
Audit
No access to real users, so this leans on public evidence rather than invented research.
The tech earns trust; the interface spends it
A 4.9-star average across 245,000+ reviews, yet "UX bloat and UI changes" is a top recurring complaint theme.
Premium feels like "more," not "better"
Paid features stack on top of the free layout rather than simplifying it; reviewers describe the premium tier as cluttered.
Small layout choices compound
A front/back distance readout split awkwardly across the top and bottom of the screen reads as careless rather than intentional to at least one reviewer.
Competitors are leaning minimal too
Newer entrants pitch themselves as the stripped-down alternative, both a visual gap and a positioning opening.
Positioning
Audience: golfers already paying for precision, the ones who bought the premium tier for the data, not the social feed.
For golfers serious enough to pay for better data, 18birdies becomes the calm, precise layer between you and the course, not one more app shouting for attention.
Identity system
Clean and modern, built around one idea: the number is the product, so the number gets the attention.
Mark & wordmark
Color
Type
Space Grotesk, 600–700 reserved for numbers and headlines. The data is the product, so it gets the distinctive face.
Inter, 400–600 every label, button, and line of body text. A quiet workhorse that recedes behind the numbers.
Applying it
Two of the app's highest-traffic screens, redesigned against the specific complaints above.
Icon, in context
Addresses: front and back distances read as one line, not split top and bottom and one dominant number instead of five competing ones.
Addresses: one headline number per screen instead of a wall of simultaneous stats.
One marketing asset
A square promo tile applying the new system: the kind of thing that would run as a social post or App Store feature graphic.
More birdies.
Reflection
What I'd want to validate next
This concept is built from public reviews, not direct research. Before touching the muscle memory of an app with 245,000+ reviews, I'd want to test the simplified on-course screen against the current one for task speed, not just stated preference.
An open question
Whether "calm and precise" reads as premium to golfers who associate value with visibly getting more for the subscription or whether it undercuts the sense of getting your money's worth. I don't think reviews alone can answer that.
No users were affected and no code shipped; this is a design exercise, built to practice turning a real, sourced problem into a considered system.
Want to talk through how I'd validate a concept like this with real users?
I'm glad to walk through the audit, the trade-offs, or where this would need real research before it could ever ship.
Get in touch