This is really cool. I think a lot of people will initially dismiss your demo as ‘slop’ unless the landing page drops some of the Claude-isms (text and design) because it’s clear this is a project with passion in it, but the demo page and landing page both look like something Claude might’ve made with a single prompt.
You're wrong! It was two prompts!
Jokes aside, you're right. I wanted to have something up quickly. Before the real launch ( and not just this demo ) I'll write one by hand, I'm against AI written copy / blogposts, just could not find the headspace to focus.
Nope, not at all. This is the original KiCad sources with some modifications to make it run in a browser. As far as I know kicanvas renders PCBs, we can do the whole workflow ( create a schematic => pcb => DRC checks, exports etc ).
My selfish suggestion would be to add support to populate the part numbers for all the components from LCSC's database. JLCPCB wants these numbers in order to assemble a PCB.
(Currently I use a JLCPCB plug-in to do this in KiCAD.)
thanks! one thing we did not port is the plugin system: it's quite hard to run python on the web ( AFAIK pyodide is not enough here ) and I've heard that it will be deprecated in the next version.
The KiCad editor's state is accessible from the web app, we'll do some kind of plugin system like Figma's or just implement these functions as an overlay. We'll see, thanks for the tip!
Again, thanks for the feedback, I'll take it!
Next time I'll make a smoother demo...
My selfish suggestion would be to add support to populate the part numbers for all the components from LCSC's database. JLCPCB wants these numbers in order to assemble a PCB.
(Currently I use a JLCPCB plug-in to do this in KiCAD.)
The KiCad editor's state is accessible from the web app, we'll do some kind of plugin system like Figma's or just implement these functions as an overlay. We'll see, thanks for the tip!