FULL-STACK PRODUCT LIVE PRODUCT
SlowJam.
A song. A message. A moment, kept for later.
A music-driven digital time capsule. Choose a song, write something personal and set an unlock date. Share it now. Open it when the time is right.
- visitors at launch
- 6.5K+
- page views in one week
- 25K+
- capsules created to date
- 1.8K+
Owner-reported launch figures: 1,500+ capsules during initial traffic; the platform later passed 1,800. These are historical figures, not a live counter.
01
Built for sharing. Tested by real traffic.
SlowJam explores the connection between music, anticipation and personal messages. A recipient can receive a capsule link immediately, while its contents remain locked until the selected date.
The product moved beyond a local prototype when public interest brought real traffic. That made external dependencies, error handling and recovery part of the engineering work.
PROJECT EVIDENCE
From a thought to a keepsake.
Actual product screens in owner-supplied walkthrough graphics. Sample content shows the creation, opening and keepsake journeys.
01 / Create and seal
Choose a recipient and song, write a message, then send now or choose an unlock date.
Open full image →
02 / Open the capsule
The recipient discovers the song and message, with an optional reflection connecting them.
Open full image →
03 / Frame the moment
Add a photo and export a framed keepsake for sharing or saving.
Open full image →
04 / Make it a letter
Personalize the background and sign-off, using the original message or AI song story.
Open full image →02
A production dependency, reconsidered.
The first release used Spotify for song search. When public traffic arrived, that integration became a production dependency issue.
I replaced it with the iTunes Search API and redeployed within approximately 24 hours. Keeping the application’s song data contract compatible limited the change needed in the interface.
- External integrations are part of the reliability model.
- A stable application contract makes provider changes easier.
- Recovery matters as much as the happy path.
03
Application and data decisions.
Next.js, React, TypeScript, Tailwind CSS and Framer Motion support the application experience. Supabase provides PostgreSQL persistence and optional account support through Supabase Auth.
Server routes connect music search, reflections and email workflows. Shareable links keep the recipient journey simple, with optional account features for managing capsules.
COMPONENTS & CONNECTIONS
System architecture.
Create & persist
- clientCreatorSong + message + date
- apiNext.jsApplication & server routes
- dataSupabasePostgreSQL + Auth
Share & reveal
- clientRecipientShareable capsule URL
- apiUnlock validationWait until selected time
- aiSong + messageOptional Gemini reflection
TECHNOLOGY & INTEGRATIONS
Each part has a purpose.
- Next.js
- TypeScript
- Supabase
- iTunes API
- Gemini
- iTunes Search API
- Music search, artwork and preview audio
- Google Gemini
- Optional reflection after opening
- Resend
- Email delivery workflows
- Vercel
- Deployment, Analytics and Speed Insights
Project scope and implementation references: view the repository ↗. Recognition, professional context and historical metrics are supplied by the project owner.
Continue the conversation.
Interested in the system, the decisions or what comes next?
Get in touch →