Role
Senior Product Designer
When
Oct 2024 to 2026
Team
Designers in US and India, 3 PMs, in-house engineers
Built with
A hardware partner and a 3D studio
Tools
Figma, Claude Code, Cursor, Adobe CC

Led end-to-end UX across a 7-product golf ecosystem: hardware, software, and the design system connecting them.

From 2024 to 2026, I led product design at Blue Tees Golf, building the team while unifying seven products through a shared design system and closer collaboration with product and engineering.

The result was one visual language across apps and devices, anchored by a 590+ component library shared by the Rainmaker iPad app and device screen. I led the app from first flow to its June 2026 App Store launch, with the product, system and team growing together.

$500K+Pre-sale revenue.PGA Show 2026, B2C.
100k+App downloads.GAME companion app.
590+Components built.Adopted by 5 designers.
+22%Engagement.From 10+ UI animations.
2xFaster pipeline.About -45% design, -25% handoff, -40% turnaround.
01 · Products

Seven products, designed in isolation

Blue Tees Golf was scaling from a single rangefinder into a full connected ecosystem, launch monitor, GPS speaker, watch, handheld, and mobile app. But each product was being designed in isolation. There was no shared interaction language, no cross-device UX consistency, and no unified data model tying shot tracking across hardware and software.

The product lineup on one ring: Ringer handheld GPS, Playmaker+ watch, Player Pro speaker, Captain rangefinders, and the Rainmaker launch monitor with its app

Defined the UX strategy that turned seven standalone products into a connected ecosystem. Every screen, flow, and interaction across the lineup traces back to a single design system and a shared information architecture. So a golfer moving between the watch, the speaker, and the app never has to re-learn the interface. This wasn't inherited; it was built from scratch, working directly with the founder to align product, engineering, and brand around one coherent experience standard.

02 · Principles

Three rules I held to.

  1. Show lessThe question was never which metrics to show. It was how few.
  2. Readable from the mat, in the sunType sized focused on metrics. Solid shapes, white on black, so nothing disappears in the sun.
  3. One role, two screensA tile asks for a role, like card surface. Each screen answers with its own value.
03 · The system

One design system for every screen

The device's own screen has no text rendering and can only animate brightness. Every word on it is an image, in five languages. The iPad app has glass, motion and a 3D scene. Both had to feel like one product.

  • Audit scope127
  • Bluesbefore 7, after 1 plus shades
  • Type sizesbefore 30, after 15
  • Coloursbefore 24, after 13
  • Button setsbefore 12, after 6
  • Library590+

I audited every product first: 127 colours across nine palettes. The Game app went from 30 type sizes to 15 and from 24 colours to 13. Seven blues became one, #1444EC, plus its shades, shared by the app chips and the device states. Twelve button sets became six. The type scale moved onto 4 px steps, each size used by a real component. A tile now asks for a role, like card surface, and each screen answers with its own value, so the look can change without touching how anything works. At the My Bag handoff, 72% of the duplicate components went away.

01 · Tokens Principle 03

One tile, two screens

Standard screens

Custom-sized screens

Session screenorganisms laid out with real datasurface/card, white 10%

NOW PLAYINGNSNITIN S
CARRY255YARDS
TOTAL267YARDS
BALL SPEED142.5MPH
CLUB SPEED95.5MPH

Screens

The device's practice dashboard: CARRY 255, TOTAL 267, BALL SPEED 142.5 and CLUB SPEED 95.5 tiles under the header row

Practice dashboardorganisms laid out with real datamain_background

Metric tile gridmolecules grouped into one regionradius/card, radius/lg · 12px

CARRY255YARDS
TOTAL267YARDS
BALL SPEED142.5MPH
CLUB SPEED95.5MPH

Organisms

The device's tile grid on its background: CARRY, TOTAL, BALL SPEED, CLUB SPEED

Readout gridmolecules grouped into one regionLevel 4 · #5F6B84

TOTAL tileatoms joined to do one jobstatus/highlight

TOTAL267YARDS

Molecules

The device's status bar: player badge, signal, Bluetooth and batteryThe device's TARGET mode labelThe device's TOTAL tile: 267 yards

Readout, status bar, labelatoms joined to do one jobHighlight - 2 · #275BE4

Label, value, chip, toggle, tagthe smallest parts, built from tokenstext/subordinate, white 50%

TOTAL267YARDSDR NS7W SESSIONS

Atoms

Icon, badge, chip, glyphsthe smallest parts, built from tokensLevel 3 · #3C465F

Colour, type, space, radiusnamed values, no interface yetblue/500 · #1444EC

Aa267

Sub-atomic (Tokens)

AaAaAa

Colour, type ramp, grid, radiusnamed values, no interface yetHighlight - 1 · #0641DD

The same five layers build both products, from tokens up to a finished screen: standard screens (the iPad app) on the left, custom-sized screens (the device) on the right, drawn smaller than the iPad. Each note names the role an element asks for and the value its product answers with, from the Rainmaker library and the device library. The device has no font engine, so every number on its screen is a PNG cut from its type styles.
02 · Sun Principle 02

If you can't read it in the sun, it isn't finished

Testing screens outside started on Playmaker+, our first watch. On different days, the thin outline icons disappeared in the sun. I moved them to solid shapes, white on black, and it became the rule on every product.

Sun 100%
Brightness 100%
Outline, before 1.0 : 1
Thin outline hazard icons beside the distances 116, 134 and 160
Solid, after 1.8 : 1
Solid hazard icons: bunker 127, water 214
  1. Contrast under glareIcon lines on black: 1.0 : 1, under 3 : 1WCAG 1.4.11, 3 : 1
  2. Hairline strokesAbout 3 px lines, the first the glare takesLegibility: stroke weight
A simulation of glare, not a photo. The same reflected sunlight and the same screen brightness fall on both screens of a pair, and the pictures stay sharp: the glare lifts the black, flattens contrast and lays a reflection across the glass. The figure beside each name is a WCAG contrast ratio of that screen's white against its ground. The real test was outside.
03 · Icons Principle 02

Every icon, redrawn solid

We pulled the icons off the app and watch screens into one audit and sorted them into stroke and solid. Many symbols had been drawn both ways. The stroke versions were the ones that disappeared in the sun tests, so solid became the rule across products.

Sun 0%
Stroke 334 : 1
  • Slope, stroke
  • Green view, stroke
  • Humidity, stroke
  • Elevation, stroke
  • Temperature, stroke
  • Round timer, stroke
  • Devices, stroke
  • Settings, stroke
Solid 334 : 1
  • Slope, solid
  • Green view, solid
  • Humidity, solid
  • Elevation, solid
  • Temperature, solid
  • Round timer, solid
  • Devices, solid
  • Settings, solid
Eight symbols from the audit, each in its stroke and its solid drawing, exported from the Style Guide file: slope, green view, humidity, elevation, temperature, round timer, devices and settings. The same glare simulation as above; toward full sun the stroke set goes first.
The device's design system, played like a type specimen: two cuts of Roboto, its glyphs, 17 text styles, 25 colours, its solid icons, one tile and one screen.
04 · Languages

Every word is an image, in five languages

Each label is an image in a fixed slot. Pick a language and both screens change, the device screen and the Launch App prompt. Each blue box is sized to the longest label in that slot across the five languages (the dashed line is the real slot); the pink marks the room the chosen word leaves inside the box.

Choose session type
Launch App prompt
Language sets both screens
English

English sits inside every box. TARGET has the least room, 6 px each side.

ENTRAÎNEMENT is the longest Practice label, so it sets that box and leaves nothing. The title leaves 8 px each side.

German sets two boxes: the title, and GESCHWINDIGKEIT in Speed. Both leave nothing.

ターゲット is the longest Target label, so it sets that box. 練習 is the shortest Practice label and leaves 45 to 46 px each side.

Swedish stays well inside every box, from 19 px in Target to 66 px in the title.

French runs to three title lines, so the text block sits higher than in the other four.

German still fits in two title lines.

Japanese mixes the Latin brand name with kana on one line.

Swedish fits the English layout, two lines and two lines.

Two screens from the hardware file in the five languages the device ships with. Every word is a slice the device loads, so a label that is too long can't wrap or shrink on its own.
05 · Calibration

Coaching a physical task with a screen

Before a session, the device has to sit at the right tilt, about 5 ft from the ball and level with it. Its screen has no text to explain that, so a side view does: an arc that turns from red to yellow to green as the tilt comes into range, and an arrow for the way to move it. Two more screens set the distance and the height. I tested it outside in direct sun, from five feet and from one.

Final design brighter greys, a bigger curved arrow
The level and calibration screens exist only on the device, not in the iPad app. The loop is drawn from the Figma layers of the final screens: the arm, the marker on the arc and its colour move between the five tilt states the design specifies. Option 2 was picked from four, then given brighter greys and a more curved, bigger, uniform arrow.
04 · Interface

The calls that shaped the app

The lead story · Rainmaker app, iPad and iPhone
01 · Show less Principle 01

23+ metrics, customized for each level of golfer

Rainmaker measures 23 things about a shot. Coaches teach that a golfer can work on about six at a time, and the iPad stands about five feet away on a range mat. So the question was never which metrics to show. It was how few.

I built the screen from tiles, in layouts of 1, 2, 4, 8 or 16, with any metric in any tile, and sized the type for the distance, not for the grid. Try it. Step back to the mat and see what you can still read.

You are

Numbers are about 17 px tall at the screen.

Flow: switching tile layouts and stepping back to the mat.

Working prototype: click to interact. On the iPad, tap the layout pills above the tiles and the clubs on the right.

The user can also customize which metric they want. This enables them to focus on improving their specific gaps, such as:

  • Club Path and Face Angle
  • Smash Factor (Ball Speed divided by Club Speed)
  • Spin Rate and Launch Angle
  • Carry Distance
Flow: swapping Smash metric tile to Side.
★★★★★
"App is really intuitive and easy to use. Does a great job at keeping you focused during practice. Refreshing to see a launch monitor app that doesn't try to do everything at once!"
App Store review · Blue Tees LAUNCH · June 2026
02 · One map

A whole session on one map

After fifty shots, a list of numbers tells you nothing. The dispersion view puts every shot of a session on one map, so the pattern shows.

In the final design each club family got one hue and each club a shade of it, so you read the family first, then the club.

The shipped dispersion view: every shot of a session on one map, one colour per club family, and the zoom slider
Flow: from a blank screen to the shipped design, zoom with the slider, select a 7 iron shot.

Marketing and sales used the dispersion view at events and shows, including the PGA Show.

03 · The trend

The trend sits where you're already looking

In Target mode you pick a distance and try to land on it. To improve you need your trend, but a trend usually means a chart, and a chart means another screen while your hands are on a club.

I borrowed onion skinning from animation: your last five shots stay on the range and fade, the newest brightest. Setting the target is one swipe, and the rest of the interface blurs while you do it.

Target mode on the range: the last five shots stay as amber trails, the newest brightest and the older ones fading, the target at 255 yards
  1. One swipe sets the distance
  2. Last shots, fading
Flow: shot one lands, one swipe sets the target, four more shots, the newest brightest.
05 · Design workflow

A file framework, so engineers stopped asking which version was right

How the team's Figma files went from loose frames to one template, and what that changed at handoff.

A team, and files people could find

I joined as the first product designer in the US and grew the design team from one to four, across the US and India. Our Figma had no covers or flows, and decisions were made out loud. In my first week I shipped a file framework: a cover with status and version on every file, and pages split by phase and platform.

Soon the PMs and the designers were writing their decisions into the file. Every handoff came with a changelog card on the page, with the old and new design side by side, so engineers stopped asking which version was right. The hardware partner's team was new to Figma, so they got tutorials first, then wireflows for every press of the remote.

Files beforeFigma files before the framework: loose frames, no covers
Files afterFigma files after the framework: covers, status and ordered pages
Figma file structuring guide · Oct 2024

One template every file started from

The founder and I wrote the framework down as a template every file started from: a cover with status and version, then the pages in one order. Every page name carried its date, what it was, and a status colour.

Launch App -
Pages
  1. Rainmaker Cover
  2. Overview
  3. \-----Dev Handoff </>
  4. ↳ 03.11.25 Primary \ Flow \ First Time Setup 🟢
  5. ↳ 03.26.25 Primary \ Flow \ Home 🟢
  6. ↳ 04.03.25 Primary \ Flow \ Session Summary 🟢
  7. ↳ 04.22.25 Primary \ Flow \ Range 🟢
  8. ↳ 05.07.25 Secondary \ Flow \ Hero Screens 🟢
  9. ↳ 05.15.25 Primary \ Component \ Design System 🟢
  10. ↳ 05.21.25 Tertiary \ Flow \ Team Workflow 🟢
  11. ↳ 05.29.25 Primary \ Flow \ My Bag 🟢
  12. ↳ 06.10.25 Primary \ Flow \ Session History 🟠
  13. ↳ 06.13.25 Secondary \ Flow \ Settings for Profile 🟠
  14. ↳ 06.18.25 Secondary \ Flow \ Demo Mode 🟠
  15. ↳ 06.23.25 Tertiary \ Flow \ Mobile Wireframes 🔴
  16. UI Library
  17. Wireframes - MVP
  18. WIP - Range UI
  19. For Review
  20. \-----Research 📖
  21. \-----Draft/Archive 🗂️
  22. Archived Designs
  23. --- Simulation (Phase 2 or beyond)
  24. Sandbox
Layers
Slide 16:9 - 1
Slide 16:9 - 1 The Launch App file's cover: In progress and Version 1.0 tags, the title Launch APP, created June 23, 2025, by Nitin
Page name, from the guide ↳ [Date] [Class \ Type \ Verb] [Status] A Dev Handoff page in this file ↳ 04.22.25 Primary \ Flow \ Range 🟢
The Launch App file's Pages panel and cover, its Dev Handoff pages named by the guide: date, class, type and what it is, then 🟢 completed, 🟠 in progress or 🔴 paused. Dash pages split it into front matter, dev handoff, the library, research and the archive.
06 · Looking back

What I'd do differently

  1. Test outside the building

    Our testers were good golfers who worked at Blue Tees. None saw the app the way a beginner would, and the My Bag reviews show what that cost. I'd fund a small research practice before the next launch.

  2. Write the limits down on day one

    No text on the device, heavy blur on Android, glass without motion. I found them one at a time, and each changed a design after it was drawn.

  3. Argue harder for the default

    Sixteen tiles shipped as the default because the number sold. The first review that praised the app praised it for not doing everything at once.

Nobody buys a launch monitor to look at an app. Most of my job was getting the screen out of the way of the swing.