What stood out to me:
• Smooth and thoughtful interactions
• Clean visual hierarchy
• Strong product storytelling
• Minimal yet engaging UI
• Great use of motion throughout the experience
Would love to know what you guys think about this design approach.
A booking system and a public press kit site for a Baltimore-area musician, connected so they share one set of data.
The booking app tracks outreach to 190+ venues. A pinned follow-up list sits above an aging queue that filters by days since contact. Statuses cover contacted, waiting on reply, parked with a check-back date, and a sub list for venues that said yes without a date. Gigs link to their venues, record what each show paid, and roll up into yearly earnings. Two people work from it at once, with changes syncing live.
The EPK is a one-page site with the artist's bio, video, and photos, plus a "Catch him live" section that pulls upcoming dates straight from the booking app. Add a gig and the public site updates on its own.
The "Catch him live" section auto-pulling from the booking app is the detail that makes this worth building instead of just handing him a static site — no more manually updating tour dates in two places. With two people syncing live on the same venue queue, did Firestore's...
Managing tasks gets messy when everything depends on remembering what needs to be done.
Today, I built a lightweight Task Manager API with FastAPI to make that process more organized. It can create, update, complete, search, filter, sort, paginate, and delete tasks.
What I enjoyed most wasn't just building the endpoints—it was testing the system, finding a real bug, understanding why it happened, and fixing it.
Another small step toward building backend systems that solve real problems.