Feature Requests

Currently, traces have a keep out minimum set against other traces and polygons. That causes auto-layout to route traces too close to pads. It would be great to add a trace-pad (or net-everything) keep out minimum default.

I've seen this a few times but did not find a design rule for it. Example explanation https://www.pcbway.com/blog/PCB_Basic_Information/What_are_PCB_Teardrops_PCB_Knowledge_453166ec.html

Many times, users need to add additional layers to the PCB to use as user notes or manufacturer notes. Silkscreen can be used as a workaround, but that is a layer that will be manufactured, so users need to remember to delete those before sending it to manufacturers. Creating this feature request to track user demand.

Today, polygons show a net label at their center of mass. If the polygon is oddly shaped, this label just floats out in space. I'd like polygon labels to display one or many net labels over their actual copper. I realize this would be "fun" for engineers, but the desire is in cases where there are "fingers" of the polygon, identify these areas and pick their center of mass and show the label there. I've attached a mock where I've marked on each polygon "finger" where I expect to see net labels.

I have a complex schematic that I'd like to break down into smaller, more manageable sections. It would be great if Flux could support multi-page schematics, allowing me to divide a single schematic into multiple pages for easier navigation and organization.

Would absolutely LOVE, LOVE a split view feature where I can see both schematic and PCB views side by side.

I'm finding it challenging to export schematics in a format that's easy to read and print. It would be beneficial if I could export these schematics in PDF format for better readability and ease of printing.

Many users get confused when trying to import Kicad or Eagle projects from the profile page. Since all import options are in the same menu, it's hard to understand at a glance that some allow project imports, while others allow only component imports. Idea: Adding a sub-menu in the import (like the import menu in the editor page) that looks something like: Import -> Libraries -> KiCAD/Eagle Import -> Schematics -> Altium/Cadence

Traces could follow parts while dragging the parts around

Ability to create hierarchical designs like in KiCad. An absolute must for any serious design. Ability to instantiate designs multiple times for reused blocks. Along with the hierarchical schematics then the ability to perform a layout of a hierarchical element, and then 'stamp' these designs into the final design. Take a 32 input sensor. A sensor channel is defined in a schematic and instantiated 32 times. Then laid out once and the same layout is repeated 32 times. What ever structuring required can be overlaid at a high level 2x16, 4x8, global controller distributed controllers, etc etc. Such a feature is not only useful for a multi-channel project, but extremely useful for say a PC motherboard, a Tablet or similar large design, where you want to build sub-components for getting the design broken down in manageable parts, that can be captured and routes, and then placed and connected at a high-level. Adding a feature like this will give Flux.ai a very unique and very strong position in the market.