A prototype becomes a different kind of responsibility when it contains real accounts and content. Figma’s new releases bring that decision closer to the design canvas.
Each feature has its own availability
Figma’s October 15 release notes put code layers and Specs in open beta. Specs is rolling out on paid plans. Code sources, which bring repository or package context into the agent, are in closed beta. Centralized design systems remain in preview.
Payload in Figma is rolling out across plans. Figma says Make can scaffold a hosted backend with content management, data, authentication, and an admin panel. Expanded MCP support is not available.
The introductory offer has a narrow scope
The code-layer help page says creating code layers needs a Full seat. Imports do not consume AI credits, but subsequent agent edits normally do. Generating and editing within code layers is free on paid plans through November 4, 2026.
Other agent work in a prompt can still consume credits during that offer. Access is rolling out over several weeks, so two people on the same team may receive it at different times.
Use one acceptance test from design through data
Choose a small flow, such as creating and editing a draft product entry. Define the expected saved state before prompting. Then check the result after refreshing and signing in as a second user.
- Confirm who can create, read, and change the test record.
- Check that a failed save displays a useful error.
- Inspect the mobile layout with real content.
- Record which actions consume credits.
- Check export and hosting requirements before importing production data.
This proposed trial tests a working application, not just a convincing canvas. Keep the same record and expected permissions throughout; otherwise, a new screen can hide a missing backend behavior.
Keep written intent close to the result
I would use Specs to record the rule a reviewer must verify, such as who can edit a record after publication. A design reference helps with appearance. An explicit permission rule helps the team judge behavior.
Our Figma Weave guide covers the separate media-workflow product. For model availability, see the updated Gemini 4 Argon guide.
Read the sources and plan your next step
Which application behavior would you verify first after turning a design into working code?
Checked October 15, 2026. This is source-based reporting and analysis;the proposed checks are not hands-on test results.
