Bike-Tinder/docs/BACKLOG.md

BACKLOG — Bike-Tinder

Glenn's "later versions" idea queue. He drops ideas in conversation; they land here (near-verbatim + a scope sketch + open questions), and get built in a future version — never mid-phase. Newest first.

B1 · Photo experience v2 — multi-image galleries, photo swipe, fullscreen viewer

Queued 2026-11-10 (during the P3 build; for the version after it). PULLED FORWARD 2026-11-10 — building now, before Phase 4 (Glenn's call). Spec frozen in UI-SPEC.md §11 + DATA-MODEL.md B1 additions; live tree untouched during the build.

Glenn's words: "more pictures! As many pictures as we can get honestly. I'd like to swipe through them left and right like tinder does. One repeats, the image should change as to not tip me off." · "I'd like to tap the image to 'full screen' it so I can see it better."

Scope sketch:

1. Capture every gallery photo. Today the pipeline keeps ONE image per listing. Verified 2026-11-10: Kijiji detail pages expose the full gallery (probe — 2026 Sport Scout page: 8 unique images; Scout Sixty Bobber: 3). The image tool already opens each listing's page when filling photos — it just keeps the first image. Extension = grab all unique gallery images (dedupe by image uuid, keep page order). State gains imgs: [...] beside img; DB carries the photo list; the mirror downloads all (sizing rule unchanged: ?rule=kijijica-640-webp). Storage estimate: ~640 listings × ~5–10 photos × ~70–120 KB ≈ 350–600 MB — fine for the mirror.
2. Photo swipe on the card — Tinder-style: tap-left / tap-right zones advance photos (segment indicators on the photo's top edge); horizontal drag stays LIKE/NOPE — the no-lock law outranks everything.
3. Fullscreen viewer — tap the image → fullscreen photo (pinch-zoom, swipe through the gallery, pull/✕ to close); works from the deck card and the dossier hero.
4. Repeat handling — "the image should change so it doesn't tip me off." Two readings to settle at spec time with Glenn:
   • (a) when a card repeats (second look / re-listed ad), lead with a different photo than the one previously shown, so the repeat doesn't read as déjà vu;
   • (b) dedupe/rotate so the same photo never repeats twice in a row within or across a swipe session. Both are cheap once galleries exist; ask which was meant at spec time.
5. Gesture-map tension to resolve at spec: today a tap on the card opens the dossier, and Glenn now wants tap = fullscreen; Tinder's model taps to advance photos. The exact zone map (tap-left/right = photo, center/ⓘ = dossier vs fullscreen) is a spec-time design session with Glenn. Dossier remains reachable from ⓘ and list rows either way.

Settled 2026-11-10 (Glenn, in chat): gesture map = tap sides flip photos · tap center fullscreen · ⓘ details. Repeat handling = lead with a different photo each time (rotation). Frozen in UI-SPEC.md §11.

Not for P3 — nothing here blocks or alters the current phase. Forward-compatible: gallery segment indicators and the P3 card bands (§10.3) must share the card's top area; the stack/drag engine is untouched.

---

Other v2+ seeds already live where they were planted: distance feature (RANKING.md open decisions) · AUTH_TOKEN hardening (DESIGN.md security) · Facebook paste-the-link box (SOURCES.md) · weekly digest, "hide this seller" (RANKING.md / DESIGN.md risk notes).