# Duck Duck Car — Clone Plan

_Plan for an "any car" clone of the Duck Duck Jeep ducking trend. Researched & drafted 2026-06-26 (bead igor2-88g.77.10)._

## TL;DR

- **What it is:** A clone of "Duck Duck Jeep" — leave a tagged rubber duck/token on ANY parked car, the finder scans a QR sticker, claims it, and the token accrues a public "journey" (map of stops + who held it). Wholesome, low-friction, social.
- **The play:** Generalize from Jeeps-only to all cars by keying everything on an **anonymous tag ID** (the sticker), never on license plates or the car. Privacy-first is the whole differentiator and the only safe design.
- **Build it as:** A **mobile-first PWA (Next.js + Supabase + Mapbox), no app store**. Tags are pre-printed QR stickers that deep-link to `app/d/<tag-id>`. Weekend MVP is genuinely shippable; v1 in ~2-3 weekends solo with AI assist.
- **Biggest risk:** Cold-start / network effects, not tech. A duck is only fun if someone scans it. Seed one city/club hard before going wide. Existing clones (dukd.io) prove the concept works but also show how thin a brand-new network is (~55 ducks).

## Part 1 — Research (the real thing)

### The trend

"Jeep ducking" (#DuckDuckJeep) started **July 2020** when Allison Parliament, rattled by a hostile encounter at an Ontario gas station, wrote "Nice Jeep" on a rubber duck and left it on a stranger's Jeep mirror. The Facebook group hit ~10,000 members within a month; it's now a global tradition (reported 60,000+ documented participants, dozens of countries). Parliament ("the Mother Ducker") died in 2024. Jeep itself acknowledges the tradition officially. The physical ritual: leave a rubber duck (often with a tag/card saying "You've been ducked!") on a parked Jeep's mirror or door handle; the finder keeps it and ideally "ducks" someone else.

### The official app / site

**Duck Duck Jeep Club — `duckduckjeep.club`** (its TLS cert is currently expired). It sells tracking kits and runs the tracking platform. Mechanic:

- Each kit includes a **rubber duck + a playing card with a custom QR code**.
- The QR links to that duck's **"exclusive adventure page"** — its own journey.
- You "duck" a fellow Jeeper, then check back to see **where your duck has been**.
- Products: "Track Your Own Duck Kit" (tag-only) vs. a "Premium / Club Tracking Bundle" (duck + card + QR). (Exact pricing not retrievable — cert error on the shop page.)

The most-cited **iOS app branded around the movement is "Happy Duckers"** (Happy Duckers LLC, free, iOS only, ~84 MB): global + personal ducking maps, leaderboards, activity feed, profiles with ducking history, **photo required** when placing a duck, comments/emoji, privacy controls. **3.7★ from only ~10 ratings** — real but tiny.

So "the official Duck Duck Jeep app" is fragmented: the **club site sells QR kits + adventure pages**, while **Happy Duckers** is the social iOS app most associated with the brand. Treat the _adventure-page-per-QR-duck_ model as canonical and Happy Duckers as the social-layer reference.

### Adjacent apps (proof the "any car" idea already exists)

- **DuckTracks** (`ducktracks.com`; iOS/iPad/Mac/Vision; free). Most feature-complete reference. QR sticker on any duck → activate → claim by scanning → interactive journey map, photo galleries, social feed + groups, a "duck wall" of messages for the next finder, DMs, events/campaigns, referral badges. v2.2 added **airport (6,000+) and cruise-ship (490+) tracking** + privacy controls. Self-reported 50+ cities, 1,000+ journeys. Token-agnostic. **Closest thing to "Duck Duck Car" that already exists.**
- **dukd.io** (web, free, launched March 2026). Explicitly **not Jeep-only** — any vehicle + cruise ships. **"ping" report model** (finder reports location; no GPS/NFC), unique DUKD IDs + printable tags, global map, **"Ghost Mode"** privacy, leaderboards, live feed. Stats: ~**55 ducks, 8 finds, 3 countries** — brand-new and thin. Good cautionary data point on cold-start.
- Others: DuckyTrack, Destination Duck (Android), JeepDuck, myJeepDuck (3D-printed ducks + charity). Mostly merch shops or thin trackers.

**Bottom line:** The mechanic is well-established, the "any vehicle" generalization is already proven, and **every player is small** — no dominant network. The opportunity is execution + a privacy-clean, low-friction loop, not novelty.

## Part 2 — Clone Plan (for ANY car)

### 1. Concept + names

A privacy-first "pay-it-forward" token network for **any car**: leave a tagged token, a stranger scans it, the token's journey grows on a public map. Wholesome and anonymous.

- **Duck Duck Car** (literal, SEO-friendly, owns the generalization)
- **Quack Track** (playful, alliterative, hints at the map)
- **Ducked!** (the moment-of-delight)
- **Roam Duck** / **WanderDuck** (emphasizes the journey)
- **Pondhop** (token "hops" pond to pond; brandable, not duck-locked)

Pick: **Duck Duck Car** for discoverability, with **Quack Track** as the app/wordmark.

### 2. Core mechanic (any car)

1. **Buy a starter kit**: N tokens (ducks, but any token works) + N **QR stickers**, each pre-encoding a unique random **tag ID** (`qk_7f3a9c`). Sticker also has a short URL: `quacktrack.app/d/7f3a9c`.
2. **Activate** (optional): owner scans their own duck to name it / set first location. Or ship pre-activated.
3. **Duck a car**: place duck on any parked car's mirror/handle. **No interaction with the car, plate, or owner is recorded.**
4. **Finder scans** the QR → opens the PWA at the duck's page → sees its journey → "I found this duck!" → optionally adds photo + note + coarse location → claims/holds it.
5. The duck **accrues a journey**: ordered scan-events (coarse location + timestamp + optional handle/photo). Finder is nudged to **re-duck** someone else.
6. Everything keys on the **anonymous tag ID**. The car is never the entity. The _token_ is the entity.

Friction rules: scanning must work **zero-install** (camera → web); claiming should be possible **anonymously** (signup only to "own" or follow a duck).

### 3. MVP vs. roadmap

**MVP (smallest fun + shippable thing):**

- QR sticker → public **duck page** at `/d/<id>` (no login to view or log a find)
- **Journey map** (pins + connecting line), coarse location
- **"I found it" flow**: drop a pin (browser geolocation, coarsened), optional one-line note + photo
- **Activation**: owner names the duck + sets hometown
- A **global "recent finds" feed** (the dopamine)
- No accounts strictly required (anonymous handle + optional email magic-link to claim ownership)

**v1 (the network features):** real auth (magic-link), profiles + **your nest**, follow ducks + move-notifications, badges, simple leaderboards, basic moderation (report/block, photo queue), buy-a-kit checkout (Shopify or Stripe + fulfillment partner).

**v2+:** NFC tokens (tap, premium), groups/clubs, events/campaigns, "duck wall" messages, **themed maps** (cruise/airport, copying DuckTracks), sponsor/brand ducks, sticker-pack designer, AR "duck nearby", native wrapper only if push/NFC justify it.

### 4. Tech stack — recommendation

**Primary path: Mobile-first PWA. Next.js (App Router) + Supabase + Mapbox GL JS, hosted on Vercel. QR stickers (not NFC) for MVP.**

- **PWA over native:** the killer flow is _a stranger scans a QR and it just works_. An install wall at that moment kills the conversion the whole network depends on. One codebase, instant updates, no app-store latency, no Apple cut. iOS PWA push works (16.4+) if needed later. Go native only in v2 if NFC/rich push demands it. (The official-ish apps are native and _tiny_ — native isn't the blocker; the network is.)
- **Supabase over Firebase:** Postgres (real relational data: tokens → events → users), **PostGIS** for "ducks near me", row-level security for the privacy model, built-in auth (magic links/OAuth), Storage for photos. Firebase's NoSQL fights the journey model. SQL + RLS is the fit and very AI-codegen friendly.
- **Mapbox GL JS over Leaflet:** nicer cartography + clustering, generous free tier. Leaflet + OSM is the zero-cost fallback.
- **QR over NFC for MVP:** free to print, any phone camera, zero app, cheap at volume. NFC = premium upsell later.
- **Auth:** Supabase magic-link + optional Apple/Google. **Logging a find requires NO auth** — anonymous finds with optional handle; auth only to own/follow.
- **Image hosting:** Supabase Storage with size cap + server resize (or Cloudinary for auto-optimization/moderation). Moderate before public.

### 5. Data model sketch

```
token            -- the duck/tag; the central entity
  id (uuid)
  tag_code        text unique         -- short code in the QR/URL ("7f3a9c")
  name            text                -- "Sir Quacksalot"
  owner_user_id   uuid null           -- ducks can be ownerless/wild
  home_city       text null
  status          enum(active, retired, lost)
  created_at

scan_event       -- one entry in a duck's journey (the find)
  id
  token_id        fk -> token
  finder_user_id  uuid null           -- null = anonymous find
  finder_handle   text null
  lat, lng        coarsened (~city/neighborhood granularity)
  geog            geography(Point)    -- PostGIS, for "near me"
  note            text null
  photo_url       text null
  created_at

user
  id; email (magic-link); handle; avatar_url; created_at

follow           -- user follows a token's journey
  user_id, token_id

-- NOTE: there is deliberately NO `car` / `plate` entity.
-- The token is the unit of identity. Cars are never recorded.
```

Journey = `scan_event`s for a token ordered by `created_at`. "Nest" = tokens I own UNION distinct tokens I've found.

### 6. Architecture sketch

- **Client:** Next.js PWA. Public read pages (`/d/[tag]`, global feed) mostly static/edge-cached; interactive find/claim flows are client components hitting Supabase.
- **Data/Auth/Storage:** Supabase = Postgres+PostGIS + Auth + Storage + Edge Functions. **RLS** enforces privacy: anyone reads public journeys; only owners mutate their token; finds are append-only; precise coordinates never exposed (store coarsened, or store precise + RLS-hide and serve rounded).
- **Geo:** browser Geolocation → **coarsen client-side to ~3 decimal places** before sending → PostGIS point for "near me".
- **Flow:** Scan QR → `/d/<tag>` (SSR/edge, public) → "I found it" → client gets coarse geo + optional photo → photo to Storage (moderation check) → insert `scan_event` → revalidate duck page + push to global feed.
- **Tags:** generate tag codes in batches, render QR PNG/PDF sheets server-side (`qrcode` lib), hand to a sticker print shop.

### 7. Monetization

- **Starter kits** (primary): ducks + pre-coded QR stickers, tiered (5/25/76-piece). Highest-margin, on-brand. Shopify or Stripe + POD/fulfillment.
- **Tag-only refills** for bring-your-own tokens (mirrors duckduckjeep.club's "Track Your Own Duck").
- **Premium tier:** NFC tokens, custom sticker designs, longer/private map history, "verified club" pages.
- **Sponsor / brand ducks:** a coffee chain or dealership funds a branded batch; logo rides the journey. (Dealerships already lean into ducking — warm lead.)
- **Clubs/events** (later): paid group features, branded event maps.
- Keep the **core loop free forever** (scan/find/journey). Monetize the _physical kit_ and _vanity/premium_, never the scan.

### 8. Key risks / decisions

- **Privacy (#1):** **Do NOT key on license plates or identify cars — ever.** No plate field, no car entity, no "this duck is on a Toyota." The token is the only identity. **Coarsen all locations**; offer a "Ghost Mode" (like dukd.io) hiding the holder's coordinates. Copy line: "We track ducks, not people or cars." Also the marketing edge.
- **Content moderation:** photos + free text = inevitable abuse. MVP needs report/block + takedown; v1 needs a pre-publish image check (Cloudinary moderation or vision-API) + review queue.
- **Cold-start / network effects (the real killer):** a duck is worthless if the finder never scans. dukd.io launched ~55 ducks; Happy Duckers ~10 ratings. **Seed one geography or club hard** (a Seattle car/Jeep meetup, one campus) for density, _then_ expand. Don't launch nationally on day one.
- **Scan-conversion design:** QR landing page must be instant, install-free, obvious ("You found a duck! See where it's been ↓"). Every wall before the "wow" loses the finder.
- **Physical-kit logistics:** sticker durability (UV/weatherproof vinyl, laminated), print costs, fulfillment, returns. Recommendation: **software-first, dropship/partner the physical kit** — don't warehouse rubber ducks.
- **Brand/legal:** "Jeep" is trademarked — generalize to "car," don't trade on Jeep's marks. The existing Duck Duck Jeep is a nonprofit; pick a distinct name and don't imply affiliation.

### 9. Build phases + effort (AI-assisted solo builder)

- **Weekend 0 — Spike (½ day):** Next.js + Supabase + Mapbox hello-world; one hardcoded duck page rendering a map with two pins. Prove scan→page→map end to end.
- **Weekend 1 — MVP (~12–16 hr):** tag schema + code generation, public `/d/[tag]` page, journey map, anonymous "I found it" (coarse geo + note), global feed, owner can name a duck. Print 25 test stickers. **Shippable to friends.**
- **Weekend 2 — v1 social/auth (~1–2 weekends):** magic-link auth, profiles + nest, follow + move-notifications, badges, leaderboards, report/block + image moderation, Stripe/Shopify kit checkout. **Launch to one seeded community.**
- **v2 (weeks):** NFC tier, groups/events, themed maps (cruise/airport), sponsor ducks, sticker designer, AR discovery, native wrapper only if push/NFC demand. Don't build v2 before proving v1 retains people.

**Sizing reality check:** the _software_ is small and very AI-codegen-friendly — a weekend MVP is honest. The hard, non-code 80% is **seeding the network and physical-kit operations**.

## Sources

- [Duck Duck Jeep Club (official)](https://duckduckjeep.club/) — cert currently expired
- [Happy Duckers — App Store](https://apps.apple.com/us/app/happy-duckers/id6447435807)
- [DuckTracks — ducktracks.com](https://www.ducktracks.com/) · [App Store](https://apps.apple.com/ca/app/ducktracks/id6759203644)
- [dukd.io — any-vehicle + cruise tracker](https://dukd.io/)
- [Jeep ducking — Wikipedia](https://en.wikipedia.org/wiki/Jeep_ducking)
- [Allison Parliament origin (MetalCloak)](https://metalcloak.com/blog/mother-ducker-allison-parliament-who-she-was-and-why-we-care)