Product case study / 66days
66days
Product Engineer · Product, design, and engineering
A social journaling product where writing from a 66-day experience becomes a personalized physical exhibit.
Proof signals
- Seasons
- Two paid seasons
- Migrations
- 95+ migrations
- Quality
- 110+ automated tests
User problem
A long-form journaling experience needed a clear path from daily writing to a personalized physical exhibit.
Ownership
Jaeyong designed the flows, data model, and interface, then built the product with React/Next.js and Node/Postgres.
Selected decisions
- Designed the product flow around a 66-day experience and its final physical artifact.
- Created the data model to support the journaling and exhibit workflow.
- Used automated tests to protect the product as it moved through migrations.
Outcome
The product has shipped two paid seasons, completed 95+ migrations, and has 110+ automated tests.
Stack
- React
- Next.js
- Node
- Postgres