I have been extensively using Figma Make for iterative AI-driven design exploration and observed a workflow-level limitation that may benefit from product consideration.
During extended usage across multiple prompt iterations, there is currently no structured mechanism to manage or track AI-generated outputs in a systematic way. Specifically, there is no built-in version control or branching model that enables users to:
• Track prompt-to-output evolution
• Compare multiple AI-generated variations side by side
• Branch or revert iterations in a structured manner
• Maintain continuity across sessions
In complex exploratory workflows, this creates cognitive overhead and reduces efficiency when managing multiple variations or refinement paths.
Steps to reproduce:
-
Generate multiple outputs using iterative prompts in Figma Make.
-
Attempt to compare, branch, or revert earlier variations.
-
Observe the absence of structured version tracking or variation management.
Environment:
Figma Web (latest Chrome), macOS.
This is not a technical malfunction, but rather a workflow-level UX gap within AI-driven iteration flows. A structured variation management or branching capability could significantly enhance exploratory design efficiency.
I would be happy to share a detailed system-level UX case study outlining a potential enhancement framework if helpful.