ReCd(Fyi)

Burn virtual CDs with AI-powered metadata, share via email or links, discover public collections, and enjoy authentic Y2K nostalgia. (Imagine a better Spotify with AI & 90's essence)

Comment

Inspiration

I grew up in the era of CD-burning, mixtapes, and physical disc sharing(Born in year 2000); carefully curating albums, creating custom playlists, exchanging discs with friends for sharing data. Over time, streaming and cloud-based music/data replaced those rituals, and with them vanished the charm, tangibility, and nostalgia of “owning” a collection. I asked myself: What if I could bring that nostalgic mixtape/CD-burning experience back; but enhanced with the power and convenience of modern web, cloud, and AI?
That question sparked ReCd(fyi): a virtual CD-burning and sharing platform that revives the mixtape spirit for the digital age.

🎛️What ReCDFyi Does

  • Lets users upload media files (audio tracks, images, metadata) and “burn” them into a virtual CD-style collection stored in the cloud.
  • Presents a clean, retro-inspired frontend with album-cover-art, tracklists, metadata, and familiar “mixtape/CD booklet” vibes; but fully modern and accessible via browser.
  • (Optional) Leverages AI to auto-generate metadata; artist names, track titles, descriptions; so even a raw folder of files becomes a polished album. (Also allow better indexing and searching when made public for easy discovery)
  • Allows easy sharing: once a “CD” is published, users get a shareable link; recipients can view the collection, browse metadata/cover-art, and stream or download tracks.
  • Built modularly: clean separation between UI components, backend services, storage, and optional features. This architecture supports future growth — public mixtape galleries, community sharing, mobile-friendly UI, and more.

🧱 How I Built It & What I Learned

Using a structured, spec-driven approach with Kiro, I developed ReCDFyi through iterative cycles; generating clean, modular code, writing tests, and refining features step by step through vibe coding and some manual bug fixing.

  • Spec-first architecture: I started with a high-level spec defining core flows (upload → metadata → burn → share), integrations (cloud storage, optional AI metadata), and modular boundaries (frontend, services, config). This spec guided the entire build.
  • Modular design: The frontend is built with React + Vite, organized into components/pages. Backend logic, storage, metadata generation, and sharing are encapsulated in services/hooks — ensuring clean separation of concerns and easier maintenance.
  • Iterative development with Kiro: For each feature/task, I used Kiro to auto-generate skeleton code, then manually reviewed, refined, and tested. Treating tasks as “must-have” helped enforce robust test suites and edge-case handling (uploads, metadata quality, invalid inputs, storage failures).
  • Optional/extendable features: Features like AI metadata generation and sharing are optional modules; allowing both a lightweight core build and a full-featured version; which taught me how to design for flexibility and future expansion.
  • Lessons learned: Building ReCDFyi reinforced the value of spec-driven design, modular architecture, and automated testing; especially important when scope evolves. It also gave me hands-on experience combining web frontend, cloud backend, optional AI, and user-facing product design in a cohesive project.

⚠️ Challenges I Faced & How I Overcame Them

  • Translating nostalgia into modern UX. Early versions looked too “web-app” and lacked the charm of a mixtape/CD experience. I iterated on UI design, album-cover layouts, and metaphors until the interface evoked the desired nostalgic vibe.
  • Managing optional complexity. Supporting multiple optional integrations (cloud storage, AI metadata, sharing) risked tangled dependencies. I resolved this by enforcing modular boundaries, spec-driven service interfaces, and clear separation for optional features.
  • Ensuring robustness with uncertain inputs. Handling file uploads, variable metadata quality, invalid inputs, or storage/ network failures required comprehensive validation, fallback strategies, and thorough testing.
  • Balancing ambition with realistic scope. With many ideas and features, it was easy to over-engineer and risk missing the deadline. I prioritized a minimal viable core first (upload + basic storage + playback), then layered optional features and enhancements.

🌱 What I’m Proud Of & What’s Next

I’m proud that ReCDFyi isn’t just a hackathon prototype; it's a well-structured, modular, and potentially real-ready application. It supports both minimal and enhanced builds, is thoughtfully designed, and has a clear path for future expansion.

Next on my roadmap:

  • Social features (community/group sharing, commenting collaborative mixtapes)
  • Further AI enhancements (e.g. auto-artwork generation, smart recommendations)
  • Better streaming / playback support, user profiles, and enhanced metadata editing

I believe ReCDFyi can revive an underappreciated format (the mixtape / CD collection) for nostalgic music lovers, indie artists, and communities; blending analog charm with modern cloud convenience.

If you’ve ever missed curating a mixtape, burning a CD, or sharing music the old-school way, ReCDFyi invites you to do it again with all the power of cloud, web, and AI.

Built With

Share this project:

Updates