2026–PresentFounder · Product Design · Mobile

Parfade

Product design for golf social — plan rounds, side games, groups

  • Product
  • iOS
  • Social
Visit live site →
Parfade product screenshot

Product screens

The loop in the hand

Parfade splash — Golf plans without the group text chaos
Positioning — plans without group-text chaos
Parfade Discover feed with planning and instant rounds
Discover — open rounds looking for players
Parfade My Rounds — planning and confirmed tee times
My rounds — planning vs locked tee times
Parfade Planning Round form with time, visibility, and join policy
Create — find players first, lock details later
Parfade Invite Friends bottom sheet
Invites — search and add friends in-flow
Parfade Games hub with Skins, Wolf, Nassau, and more
Games — Skins, Wolf, Nassau, Sixes…
Parfade activity feed with Wolf standings
Activity — game results and standings
Parfade Groups — My Groups list
Groups — communities for regular play
Parfade profile with handicap, followers, and activity
Profile — handicap, social graph, hosting
Parfade architecture diagram

Overview

Parfade is a consumer iOS app for golfers who already have a network — Saturday regulars, the “who’s free Thursday” crowd. Getting a round together was eating more energy than the round: three group chats, half the people don’t see it, maybes pile up, and the tee time’s gone. The work isn’t golf. It’s logistics.

I own product design and the full stack. The product only works if other people tap Accept — I feel the pain as a player, but I’m not the customer.

Problem

Scorecard apps don’t fix invites; invite tools don’t run games. The real failure mode was leaving negotiation outside the product.

Product decisions

First I tried the timid version: a link or poll dropped into the group thread — keep iMessage as home base, make the app a helper. It failed. People answered in the thread, the poll went stale, and the host was back to juggling.

So availability became a first-class action. Pick friends or a group; Parfade pushes; first to accept are in. In-app chat stays for people already in the round. What I refused to keep was three outside chats as the booking system.

  • Invite → push → accept/decline — host sees who’s in without chasing threads
  • Planning vs locked tee time as clear states; course and time on the notification and accept screen (after a friend accepted then texted “which course?”)
  • Games, scoring, and recaps so the app isn’t only useful for five minutes of RSVP
  • Groups and profiles so regular foursomes stick around after the round

Brand & craft

Visual system leans golf-club calm: cream surfaces, forest green, gold mark, script wordmark next to utilitarian UI. Lifestyle photography sets the bar; in-app chrome stays quiet so course photos and standings can lead.

Outcome & honesty

Shipped loop at parfade.com — build your people, invite, accept, play. Traction is early on purpose: no marketing yet; me and two friends is enough to feel the product break in real rounds, not enough to claim PMF.

The real constraint is habit. Group chat is still the default. I don’t win by building a better messenger — I win when a host trusts a Parfade invite to fill a tee time faster than three threads.