The shift to designing directly in Framer rather than importing from Figma is well underway and this video explains why

When Framer's native design capabilities have reached the point where you can design fully inside the platform and publish directly, the Figma import step is adding friction without adding capability. The design-to-build workflow being entirely within Framer changes the iteration speed because you are not managing asset handoffs and component translation between tools.

The AI-assisted design with ARIA accessibility labels being generated automatically is the professional quality standard that previously required dedicated accessibility review. Having it built into the generation process rather than as a separate audit step changes both the quality floor and the workflow.

The CMS with flexible content structures supporting filtering, sorting and search across all content types is the content management layer that changes what categories of site are practically buildable in Framer without developer involvement.

The template library covering SaaS, portfolio, agency and e-commerce sites is the starting point variety that determines whether Framer serves a broad enough range of project types to replace a separate build tool for most web work.

What is the project type where you have found Framer's native design capabilities to be insufficient compared to Figma?