Feature Requests

If I search for a 100nf capacitor in search, it'd be so cool if in the background, it also searched for other combinations of that unit, like 0.1u.

Sometimes I import a part just to see if it's in fact the one I'm looking for. I'd rather be able to see the 3D model of the part and maybe the footprint to feel more confident that I'm importing the right part and not wasting time.

Need ability to directly import parts from well know sellers like Mouser, LCSC, etc. Should program AI to AUTOMATICALLY create a Part library based on accessing established data sources like above.

After the sixth version of KiCAD was released, many platforms with KiCAD component libraries started supporting all version 6 files, so actually components from their libraries cannot be added to Flux. It would be great if Flux had support for version 6 of KiCAD, it would make it possible to import components/files from ultralibrarian without problems

The preview image for a module in the parts library search makes it look like an IC, which is confusing when looking for a sublayout (i.e. something with traces, passives, etc). In this image, you can see the "buck boost" search query shows plain ICs as well as the submodule I want, but to a new user this is hard to quickly distinguish when browsing search results. The request: show a snapshot of the PCB view (2d or 3d is fine) in the preview image for a sublayout.

When I type in an LCSC part number (or digikey, mouser etc) into the part library search, a component should show up.

I have a bunch of parts from previous projects. It would be great if Flux could show how many of that part I have on hand as well as a filter in the library for parts I physically have. This would prevent me from buying more of the same parts or parts with different packages.

Make it easier to find parts in the library by using properties as a filter. For example, I'd like to set a filter for diodes and threshold voltage.

Is there any way to vet pin names and footprints on custom parts made by the community? One of the main reasons that stops me from using Flux is that people who create custom symbols for IC's usually don't take the time to also create the footprint and properly label the pins according to the datasheet. Some will even leave out pins that they deem "unnecessary". This absolutely kills productivity as now the designer must try and analyze the symbol itself to make sure that it fits the specifications on the datasheet, spend additional time searching and vetting a suitable alternative, or make their own from scratch. I understand the desire to offload work by having the community create create a symbol library for your business, but having no vetting process for symbols just fills the search with unfinished garbage.