Foresome
Plan a golf trip with your group. One invite link, and everyone votes on:
- When: date options on a scorecard grid (in / maybe / out)
- Where: destinations, each with the airport everyone flies into
- Where we stay: paste an Airbnb, Vrbo or hotel link with the total; the app checks beds against who wants their own
- Where we play: courses and tee times by day, with greens fees and the date each price was checked
The organizer locks the winners. Everyone pays their own way; the app shows each person's estimated cost (people sharing a bed pay 25% less of the house), and the Flights tab searches round trips from each person's home airport for the locked dates and shows who lands when, flagging anyone who would miss the first tee time.
No scorekeeping. This app is only for planning.
Data sources
- Airports: OurAirports (public domain), bundled in
src/data/airports.json: airports with scheduled flights only. Typing a destination suggests the closest ones, favoring big airports with more flights.
- Golf courses: OpenStreetMap via Nominatim, with Overpass as a backup (free, attribution required).
- Weather: National Weather Service forecast within 7 days (US), and, further out, typical weather from NOAA climate normals (nearest US station) with NASA POWER for wind and trips abroad. Both free, no key, fine for commercial use.
- Place lookup: OpenStreetMap Nominatim (cached a week per place).
Stack
- Next.js 15 (App Router) + TypeScript, deployed on Vercel
- Supabase (Postgres) for trips, members, options and votes
- Duffel for flight search
- No passwords: joining a trip stores a secret token on that phone. All database access goes through the app's server with the secret key.
Set it up (about 20 minutes)
1. Supabase
- Open your Supabase project.
- Go to SQL Editor → New query, paste everything in
supabase/schema.sql, and click Run.
Projects created before accounts or notifications existed: also run supabase/002_accounts.sql, supabase/003_notifications.sql and supabase/004_safety_email.sql.
- Go to Project Settings → API and copy:
- the Project URL →
SUPABASE_URL
- the secret key (
sb_secret_...), or the legacy service_role key → SUPABASE_SECRET_KEY
2. Duffel
- In the Duffel dashboard, go to Developers → Access tokens.
- Create a test token (
duffel_test_...) → DUFFEL_ACCESS_TOKEN.
Test mode is free and returns sample airlines so you can try the flow. Switch to a live token when you want real fares.
3. Vercel
- In Vercel, click Add New → Project and import the
Foresome repo from GitHub.
- Before deploying, open Environment Variables and add the three values:
SUPABASE_URL, SUPABASE_SECRET_KEY, DUFFEL_ACCESS_TOKEN
- Click Deploy. Vercel gives you a link like
foresome-xyz.vercel.app. The live app is at https://www.foresomes.net (domain registered at Netlify, DNS pointing to Vercel).
4. Try it on your iPhone
Open the link in Safari, create a trip, then tap Share → Add to Home Screen. It opens full screen with its own icon. Send the invite link from the Trip tab to a friend and vote from both phones; updates appear within a few seconds.
Run it on a computer (optional)
cp .env.example .env.local # fill in the three values
npm install
npm run dev # http://localhost:3000
How the code is laid out
| Path | What it does |
|---|
supabase/schema.sql | Tables: trips, members, options (date, destination, lodging, round), votes |
src/lib/shared.ts | Types and trip math: vote tallies, leaders, bed counts, cost per person |
src/lib/server.ts | Database client, input cleaning, loading a trip |
src/app/api/trips/... | Create, join, load, actions (vote, add, lock, pairings, flights picked, email the plan), flight search |
src/app/api/preview | Reads a pasted listing link's title and photo when the site allows it |
src/components/TripApp.tsx | The trip screen: syncing, tabs, join screen |
src/components/tabs/* | Trip, Vote, Stay, Golf, Flights |
What's next
- Live tee times and greens fees from the GolfNow affiliate API (needs approval)
- Hotel search with commission through the Expedia Group creator program
- Text-message reminders to people who haven't voted
- An App Store version wrapped with Capacitor (needs a Mac and an Apple Developer account)
Accounts, guests and notifications
- People can start or join a trip with just their name and home city (a guest spot saved on that phone), or sign in with email so their trips follow them to any phone. Signing in later attaches the account to the guest spot.
- Only members see a trip's details. Anyone else with the link sees the trip name, the organizer's first name and how many are going.
- Notifications use web push. On iPhone they work once Foresome is added to the Home Screen (iOS 16.4+). The signing keys are generated on first use and stored in
app_settings; nothing to configure.
/api/health reports whether the database, accounts and notifications are set up.
Emails, daily job and safety
- Trip emails go through Resend's API when
RESEND_API_KEY is set in Vercel: nudges, "dates/destination/place locked", and the organizer's Email the plan. Only people with an account and Trip emails on (profile) get them; every email has a one-click unsubscribe.
- Daily job (
vercel.json → /api/cron/daily): keeps the free Supabase project from pausing and clears old sign-in requests, rate-limit records and sessions unused for 6 months. Set CRON_SECRET in Vercel to lock it to Vercel's scheduler.
- Rate limits on sign-in emails, new trips and guest joins (
rate_events table).
- Flight search only appears with a live Duffel token (
duffel_live_...). Until then the Flights tab uses Google Flights plus manual entry.
- Old address: opening foresome-one.vercel.app moves the phone's saved trips and sign-in to www.foresomes.net (
/migrate).
- Privacy and terms:
/privacy and /terms. Have a lawyer review them before charging money.
