EasyCircuit

A schematic view export would be amazing, especially as a downloadable PDF or SVG. Right now you get the parts kit but if I want to tweak the design myself or share it with a maker friend, I have nothing to work from visually. That would make this way more useful for anyone learning along the way.

Sourcing real in-stock parts is the underrated feature here, half the pain of hobby electronics is finding out the part in the tutorial went obsolete years ago. The breadboard to perfboard progression is a nice touch too. How does verification work under the hood, does it actually check electrical constraints like current limits or is it matching known patterns from the parts library?

Looks like I'm about to lose myself in this for quite a few fun evenings! :)

The orchid chamber origin story is great, that is exactly the kind of project people abandon once the wiring gets confusing. This would get me to finally attempt a hardware side project instead of stopping at the idea stage. With 290 parts in the library so far, how do you decide what gets added next, sensors, motors, or whatever users request most?

Do you see EasyCircuit evolving into a full KiCad workflow? It would be amazing if beginners could go from a plain-English idea all the way to a PCB while learning why design decisions were made.

Hardware is the last place where iteration still costs weeks and real money, so lowering the barrier here matters more than another web-app builder. The question I'd have as a user: how far does it get me before I need an EE to check the work? Congrats on shipping.

the fried-sensor case is one thing, but I'd want to know about the failure modes that are actually dangerous rather than just annoying - anything touching mains voltage or LiPo battery charging. does the tool flag current/voltage limits that could cause a real safety issue (overheating, fire risk) as a hard stop, or is that still something a beginner could accidentally wire past since it technically "works" on the breadboard?

The prototype is the easy half, honestly. I do sourcing and QC in Yiwu, and what usually stalls people is the handoff: the factory asks for a BOM with acceptable substitutes, and the answer is "whatever the prototype used." Then someone swaps a capacitor to hit a price target and nobody catches it until the first batch lands.Curious whether you export anything a factory could actually quote from, or is that outside what you're solving?

the orchid growth chamber backstory sells this way better than a generic pitch would. one thing that gives me pause with AI-designed hardware specifically vs AI-designed software: a bad software deploy just rolls back, but a bad resistor value or wiring choice doesn't show up until you've already soldered a real board and maybe cooked a sensor. does the breadboard stage actually catch those mistakes before anything's committed, or is it mostly a physical-layout check rather than a real electrical sanity check?

Hey Product Hunt 👋

I built EasyCircuit because of a much weirder project: an instrumented orchid
growth chamber. I wanted to run real causal-inference experiments on plant
growth — controlled interventions on temperature, humidity, light — which
meant I needed a custom sensor/actuator circuit with an ESP32, humidity
sensors, a pump, heaters, LEDs, all wired together correctly.

I know how to write code. I did not know how to design a circuit. Every time
I tried, I'd hit the same wall: which pins are safe to use, what resistor
values won't fry a sensor, whether a part I liked online was actually in
stock anywhere. Days would disappear into datasheets before I'd wired a
single connection.

So I built the tool I wished existed: describe what you want in plain
English, and a copilot designs the full schematic, lays it out for a
breadboard so you can prototype before anything is soldered, and matches
every part to a real, in-stock supplier — then bundles it into one
made-to-order kit if you want it shipped.

It's still early — 290+ parts in the catalog today, more added weekly — and
it's meant for exactly the person I was a few months ago: comfortable with
code, new to electronics, tired of losing a weekend to a part that turned
out to be discontinued.

Would love your feedback, especially if you try describing something weird
and see what it designs. That's the best way to find where it breaks.