Inspiration

AudioSetup Planner was born from a very real need—our own. Together with a group of friends, we started collecting music in physical formats—vinyl, cassettes, CDs—and quickly realized that we wanted it to sound better. The problem was, once we tried to upgrade our setups, we ran into a steep learning curve and a sea of disorganized or overly technical information.

There were countless forums, opinions, and guides, but very few visual tools to help us understand, plan, and build an audio system step by step. That’s when the idea came up: to create an app that could work as a map and guide for anyone trying to navigate the world of physical audio without getting lost in it.

What it does

AudioSetup Planner is a tool that helps you:

  • Visualize your current audio system: see what components you have and how they’re connected.

  • Plan your dream setup: add upgrades in stages based on your budget and interests.

  • Get useful guidance: recommendations on compatibility, upgrade order, and essential components.

  • Estimate costs and track multiple configurations.

The focus is on combining a friendly and visual experience with the kind of advice we wish we had when we were starting out.

How we built it

We built AudioSetup Planner using Bolt.new, a platform that allowed us to rapidly prototype and iterate on both design and functionality.

Our tech stack includes:

React for building the UI component structure.

TypeScript for clean, scalable, and safe code.

Tailwind CSS to quickly prototype a modern, responsive interface without worrying about traditional CSS.

Bolt.new was essential in helping us move fast, test ideas on the fly, and stay focused on delivering a smooth user experience over getting bogged down with low-level setup.

Challenges we ran into

One of the biggest challenges was finding the balance between simplicity and depth. We didn’t want to build something so basic it became useless, nor something so complex that it scared off beginners.

Other key challenges included:

  • Designing an intuitive interface to represent audio setups and component chains.

  • Translating technical language (DACs, gain stages, phono vs. line input, etc.) into terms anyone could understand—without losing accuracy.

  • Keeping the visual experience clean and focused, without overwhelming the user with jargon or options.

Lastly, we had to carefully design the progressive structure of the planning tool: how to allow users to upgrade step by step, without feeling like they're constantly missing something.

Built With

Share this project:

Updates