Independent product · Role: Product Designer and builder (product thinking, UX, UI, AI-assisted development)

After a decade of gigs and festivals, my concert memories were scattered across Notes, Instagram stories, ticket emails and memory. Music apps focus on discovery, tickets and setlists, not on collecting and revisiting the shows you've already been to.

Set four product principles: personal, visual, useful and low friction

Cut an early social feed to focus on the structured history the diary creates

Designed in Google Stitch, then built the app with Claude Code, React and Supabase, deployed on Vercel

Added setlist.fm and Spotify integrations only where they reduced logging or made the record more useful

A diary, not a feed. A visual, card-based history linked to artists, venues and setlists.

Design for real data gaps. setlist.fm often misses smaller or older gigs, so there's a manual fallback and an empty state that invites your own memories.

Let the build shape the scope. API limits, loading and error states clarified what the MVP really needed, and pushed other ideas to later.

MVP built and deployed in about 48 hours

v1.5 shipped in September 2026, adding milestone stamps, a "this day in your history" home screen and shareable story images

70+ shows logged in the live demo, which anyone can explore without signing up

AI made the build much faster, but the quality still came down to product and design decisions. Next, I'm testing with real users.

Full case study: https://janitadacosta.com/scenes