Building an open source tool to simulate hardware before you build it, I would love early feedback

Hey everyone!!

I'm David the founder of Hardwave.

I came from software into hardware, and the thing that got me was how slow the feedback loop is. In software an IDE yells at me before I even hit run. If I mess something up, I usually know within minutes.

In hardware, you find out after you've ordered parts, soldered everything, and flipped the switch. Every mistake costs you a shipping cycle, not a save and refresh.

So I built Hardwave, an open source Python framework for simulating hardware before you buy or assemble anything.

Under the hood it builds a simulation graph where each component exposes inputs, outputs, and state so you can compose everything from a simple circuit to a full electromechanical system.

For example you can model a battery, an H-bridge, a DC motor, and a PID controller, then simulate how the whole thing behaves under load. This can help you determine current draw, voltage sag and controller response all in Python, before a single part ships to you.

I'm launching on Product Hunt soon, but wanted to hear from this community first.

The product is still very early. Hardwave's standard library today covers generic components, the long term goal is to build a library of real manufacturer accurate models.

Hardwave is MIT licensed and fully open source

If you build hardware: where does your iteration loop actually hurt? Have you used simulation before, or steered clear of it? What would make this useful to you?