The realtime collaboration was just straight up broken; as in, my collaborator would make changes that would not manifest until I refreshed. This is unacceptable.
The PCB tracing was unusable because you could not control the wires and things would appear in strange places. Forget auto-routing... I had trouble just getting it to connect wires.
I could go on at (great) length, but while I genuinely am rooting for the team behind this product, I can't recommend it until they prioritize getting the fundamentals working properly over adding new AI features.
That said, in attempting to work through these issues, I gained a healthy amount of respect for how hard it is to create a viable new entry in this domain. For whatever reason, it often seems culturally normalized to shit on Flux and I think this is toxic and unproductive.
Also, we're working fast to solve some of the issues you describe. Have you tried us recently?
I transitioned my product to KiCAD in late December. I'll definitely check out how things are going when I start my next product later this year.
These "library managers" like Ultra Librarian and SnapEDA are a pox upon the ecosystem. The symbols and footprints have non-open source licenses, so you nominally can't share them. They simply want to get in the middle of your design so that they can monetize you.
How does the licensing issue actually manifest in a practical sense? By what mechanism(s) could this monetization occur? Is this sabre rattling or are small hardware designers actually getting bills for using premade footprints and models?
The AI is a cool idea. Maybe as an add-on? An import? A library? Collaboration? IDK, but details like via tenting properties on layer 3 are best left to the experts.
We see this in the web browser engine space with Chromium.
That's why I find the glee with which prominent EE community types appear to condemn Flux really frustrating. Yes, Flux has big problems and a huge mountain to climb. To me, that's why we should encourage them. There are a million easier things those folks could be attempting, so shitting on them for trying to bring a new perspective is self-defeating.
As for Altium, I haven't used it because it's very expensive and tied up in a larger enterprise ecosystem. It doesn't make a ton of sense for solo or small-team designers to use a tool heavily influenced and full of tooling for use by the world's largest companies.
That's why I found Flux so compelling; my partner and I actually want to use the "Figma for electronics", if such a thing can be provided without critical bugs.
By that I mean most work is heavily regulated, either defense, aerospace or industrial goods that must meet safety certs. Schematic and PCB design flow are heavily impacted and you can't go all tech startup go fast and break things on it.
Anything that's mass market consumer goods these days is outsourced to a shop in Asia or even Eastern Europe to design. At that point their labor is cheap that you don't care what they use.
I should add that I’m somewhat experienced as well. I’ve successfully designed 6 layer boards with blind via, BGAs, Bluetooth trace antennas before trying flux. Still have no clue how to use flux.
I needed something with really complex footprint that no one had, I contacted SnapEDA, and for $50 they did a model and footprint in less than a day. Extremely worth the money in that case.
It'd be nice to be able to describe the circuit as simple code, compile it, and then get it in the mail a couple of days later.
I'd love to be able to design circuits the way I can do with 3D printing.
