3 specific things stand out for me after many years of daily use:

Variables and component properties.

We do complex SaaS products and software design: fintech dashboards, healthcare platforms, enterprise tools. These demand a single button component that works seamlessly across a main platform, a patient portal, and an admin dashboard. Variables let us manage this flexibility without component bloat.

Branching.

When designing in phases for active products, we often explore multiple directions simultaneously. Branching allows us to do this securely, without copy-pasting files or losing version history.

Dev Mode.

Engineering teams use this to pull spacing values, color tokens, and code snippets directly, which cuts the spec documentation time roughly in half. Review collected by and hosted on G2.com.

Performance degrades noticeably on large enterprise files. We work on products with 200+ screens and dozens of component variants, and once a file crosses a certain complexity threshold, the canvas starts to lag: zooming, scrolling, and switching between pages all slow down. You can split files to work around it, but that introduces its own problems with cross-file component references.

Prototyping is still limited. Complex conditional flows - where the next screen depends on data state, user role, or previous selections are hard to represent without workarounds. For a dashboard where what a user sees depends on their portfolio type, account level, and market state, we end up building separate prototype flows for each scenario rather than one dynamic prototype. We often supplement with coded prototypes for client presentations. Review collected by and hosted on G2.com.