- Problem
- Family stories vanish because capture tools are fragmented and nothing turns the recordings into something durable. The prototype tests a keepsake pipeline end to end.
- Role
- Product builder and prototype engineer
- Date
- 2026
- Tools
- Next.js, PWA, Local media storage, Private preview workflow
Family Story Keepsake PWA
A voice-and-photo story-capture prototype for turning family history into keepsake products — deliberately parked, with the restart criteria written down.
Claim: the prototype works; the launch is the part being withheld.
Receipt: a private preview app that captures family stories by voice and photo and shapes them toward keepsake outputs — with payments, print fulfillment, and external AI calls deliberately disabled in preview.
Status honesty: Preserved means parked, not abandoned. It sits in the register untouched until an active lane earns out. The restart criteria are already set: privacy review, family permissions, and trust design lead any relaunch — monetization follows, never the reverse. An emotional product gets held to the highest bar in the shop.
Receipts
Outcomes and lessons.
Outcomes
- Private prototype exists for voice/photo story capture.
- Payments, print fulfillment, and external AI calls intentionally disabled in preview.
- Public proof waits on screenshots and permission review — no exceptions for sentiment.
Lessons
- Emotional products need trust, privacy, and restraint before monetization.
This entry stays in the portfolio as product-thinking proof, not a launch claim: a real workflow was prototyped, and the pieces that would create privacy or fulfillment risk were held back on purpose. That restraint is the point.