Release 7a · Queued
Check-ins & Tags
The core social layer. Validation loop, friend tagging, pin visit timeline. Where WanderPins graduates from a solo journal into a network.
Summary
The core social layer. The validation loop (you went where your friend said to go, they get notified), friend tagging at shared experiences, and the timeline of revisits. This is where WanderPins graduates from a solo travel journal into an actual network of trusted recommendations.
Maps onto SCOPE.md scenarios C, D, and E: owner revisits own pin (C), user checks into someone else's pin and gets prompted to save their own (D), and users tag each other on shared experiences (E).
What's in scope
- Check-in on own pin (Scenario C) — adds a visit entry to the pin's timeline instead of creating a new pin
- Check-in form — date, note, photos, condition update
- Pin visit timeline view — full history displayed on the pin detail
- Freshness indicator — time since last visit, shown on pin cards
- Validation loop notification — pin owner notified when someone in their network checks in
- Prompt to save personal pin after checking into someone else's (Scenario D)
- Tag a friend from pin detail (Scenario E)
- Tag acceptance → pre-populated pin copy — tagged friend gets a new pin draft with shared context
- Push notification integration for tags and check-ins
Open questions
- Check-in UX — PRD needed. Form design, what conditions to track (road closed? water available? site quality?).
- Tag flow UX — how does the tagged person accept? Notification with accept/decline? Deep link? Drafts folder?
- Notification copy and delivery rules — when is a check-in notification too noisy? Batched daily digest vs real-time?
- Validation loop — quiet mode? Some users may not want to notify the original pin owner every time. Opt-in or opt-out?