Figma Make | Gemini 4 Argon Joins the Model Picker for AI Prototypes

Figma began rolling out Gemini 4 Argon in Figma Make on October 13, 2026. It joins the model picker as an option across all plans. For designers turning an idea into an interactive prototype, the useful question is how it interprets the same visual context and interaction requirements compared with the model already being used.


Figma Make Gemini 4 Argon model selection

{getToc} $title={Table of Contents}

Change the model without changing the workspace


The selection lives in the Make chat box: open a new or existing file, click the displayed model name and choose Gemini 4 Argon. The menus, conversation panel and code view stay in place. Switching the underlying model therefore fits into the existing prototyping workflow.


Use a defined task for the first comparison. A booking flow, for example, needs understandable choices, clear feedback and a coherent path back from an error. Establish those requirements before judging the first screen. A polished visual result is useful only if the interaction it represents also makes sense.



Compare a complete interaction


Choose one short flow and keep the brief consistent. Ask the prototype to handle the same content, states and basic layout, then review where the generated experience follows or misses the design intention. Record specific differences such as a missing confirmation, an unclear control or a layout that breaks with longer text.


Refine the most important issue before adding new features. For a filter panel, that might mean checking selected states and reset behavior; for a sign-up screen, it might be the response to invalid input. Small, observable tasks produce a clearer model comparison than a broad request to improve the entire application.


Check AI access and credit use


The team's or organization's AI setting must be enabled to access Figma Make. Non-default models can behave differently, take longer or use substantially different amounts of credits. Consumption also depends on task complexity and context, so the account's own credit history is the practical reference for evaluating cost.


Keep the first test limited enough to compare effort as well as appearance. Note how many revisions were needed and whether the final interaction met its acceptance criteria. A result that looks stronger initially may still require more work to make it understandable, accessible and consistent with the rest of the design.


Preserve the design context across revisions


Figma Make allows model changes during a conversation. New files start with the default model, while existing files retain the last selection used there. Confirm the current choice when returning to a prototype so a later comparison is based on the model actually handling the request.


Before reviewing with teammates, check the prototype at relevant screen sizes and replace vague sample text with realistic content. Explain which behaviors are ready to assess and which remain exploratory. This gives reviewers a useful basis for feedback without treating every generated interaction as an approved product decision.


Daisuki's Take: What This Means for Designers


We would evaluate Gemini 4 Argon through a real interaction rather than a screenshot alone. The model needs to help communicate how the design behaves.


A fair comparison includes the revisions and credits needed to reach an acceptable result. Those details matter when prototyping becomes a regular part of the team's work.


For designers, the useful option is the one that interprets the brief clearly and supports deliberate refinement. Keep the test specific enough to make that judgment.



Sources and Recommended Links