The Doozer App, one native app for the whole ecosystem (kick-off plan)

decisions/doozer-app.md · Decision · doozer-app, native, mobile, ios, android, expo, wuz, check-ins, leadbuilder, location, memories, plan

status: plan · written by claude-opus-5-5 on 2026-10-25 · stale after 2027-04-01

October 2026 kick-off for a cross-platform native app that carries the whole Doozer ecosystem: find a place, arrive, keep the moment (a check-in becomes a Wuz), relive it, and the commerce in between, with LeadBuilder as the data spine. What it is, the architecture, the privacy rules, the phases, and the decisions that are Jon's.

The Doozer App

"A native app that will incorporate the entire doozer ecosystem into a native app with cross

platform use, in the way that checkins become wuz's and data is tracked by leadbuilder. Same

deal as the web but an all in one local commerce app with location and everything we've wanted

to do from making memories to reliving them." (Jon, Oct 25 2026)

This is its own project, started in its own chat. This page is the plan to hand it off with.

What it is

One app, called Doozer, that is the web ecosystem in your pocket with the things only a phone can do: it knows where you are (when you let it), it has a camera, and it can tap you on the shoulder. The loop it exists for is the one The One was built around:

1. Find: nearby places, open now, a search, Alice suggesting the next step, Doozer Town.
2. Arrive: "I'm here" becomes a real check-in. The app can notice you have arrived and ask,

only if you turned that on.

3. Keep: a photo, a note, a receipt, the people you were with (who agreed) become a Wuz:

a memory with the place attached.

4. Relive: your Wuzzes on a timeline and a map. "A year ago today, coffee with Dad at Luc's."
5. Connect: two people who were in the same place at the same time can find each other,

only if both say yes. And the commerce in between: gift cards and ordering (doozer.shop), game nights (doozer.games, join by scanning the TV), Doozer+ for owners, leads for the businesses people choose to contact.

The data spine: LeadBuilder

LeadBuilder (lb_*) already carries identity (lb_users, entitlement in tier), sessions, events, follows and leads, and bridges every demand signal on the web. The app uses the same spine, so a person is one person on the web and in the app.

• What LeadBuilder tracks for a business, in aggregate: visits to its page, taps (call,

directions, order), check-ins counted, leads a person chose to send. Never a person's identity unless that person contacted the business.

• What stays the person's: the trail, the notes, the photos, the Wuzzes. Private by default,

theirs to export or delete.

Architecture (recommended)

• Expo (React Native) with TypeScript, iOS and Android from one codebase. Native modules for

location and geofencing (expo-location, background only by opt-in), camera and photos, push (expo-notifications to APNs and FCM), maps (MapLibre), secure storage, a local SQLite store. EAS builds and over-the-air updates. (Capacitor wrapping the web pages is faster to start but will never feel native; Flutter is fine but would not share code with the web.)

• An API, versioned: doozer.work/api/v1/..., built from the endpoints the web already has

(places_mini, businesses_near, geo, check-ins, photos, saves, sv_still, Alice's model, the One profile). JSON only, the same sources and tags the page shows (G W M C D P O).

• Identity: the magic-link sign-in that exists (lb_users, stateless signed JWT, global

sign-out by token_version), plus Sign in with Apple (Apple requires it alongside other sign-ins). A device token per install for push.

• Offline first: the trail, Wuzzes and saved places live on the device and sync; The One

pages cache for the places you saved.

• Deep links: doozer.link and every One page open in the app (universal links / app links);

a game QR opens straight into the game controller.

Rules (non-negotiable)

• Location only while using the app by default. "Remember where I've been" (background) is

off until the person turns it on, explained plainly, and can be paused or erased.

• No covert presence: no Bluetooth or Wi-Fi scanning of who is near you, no face matching,

never revealing a person from a receipt or a photo's background. Connection is mutual opt-in.

• A business sees counts, never people, unless a person chose to contact it.
• No dark patterns: no streaks that guilt, no fake urgency, notifications only for what the

person asked for (a saved place opening, a game night, a reply).

• The person's memories are theirs: export everything, delete everything, one tap each.

Phases

• A0, foundations (first in the new chat): inventory the web endpoints into an API v1 map;

the app's design system from the Doozer family tokens (includes/doozer-family.php); the data model for a Wuz (place, time, photos, note, receipt, companions-who-agreed, privacy level); repo and Expo/EAS setup; App Store and Play accounts.

• A1, the MVP: sign in; nearby and search; The One as a native screen (photos, hours, Street

View, sources, Alice); save and lists; "I'm here" check-ins with a note; the trail.

• A2, memories: photos and receipts on a check-in become a Wuz; the timeline and the map;

"on this day"; a shareable memory card.

• A3, owners: the owner's own page (the Owner's One), their numbers, leads and the call queue,

push for a new lead; Doozer+.

• A4, the rest of the family: join a game by scanning the TV (the phone becomes the touchpad),

gift cards from doozer.shop, Doozer Town, widgets and Live Activities ("you're at Luc's").

• A5, launch: TestFlight and Play testing with real users in West Milford, then the stores.

Decisions that are Jon's

• The name in the stores ("Doozer") and the developer accounts (Apple, Google).
• Expo as the stack (recommended above).
• Doozer+ inside the app: Apple and Google take 15 to 30% of digital subscriptions bought in an

app, and their rules decide when a business service must use in-app purchase. Decide whether Doozer+ is bought on the web only, or in the app too.

• How far "remember where I've been" goes, and whether it ships in A1 or later.
• Whether logfile.me (receipts) and wuz.ai are brands inside the app or features of it.

Related: The One Page, LeadBuilder, Alice, Doozer Games and Shop, The Observed World, No Dark Patterns.