Request for "Edit Previous Iteration"

Stitch
, ,
1

Subject: Request for “Edit Previous Iteration” Functionality in Gemini’s Design Tool

Problem Description:

The current design tool, when using the edit_design function, generates a new screen_id for every modification made to a screen. While this creates a version history, it critically prevents the user from directly selecting and making further changes to any screen_id that has been superseded by a newer edit.

Current Workflow Limitation:

  1. Linear Progression Only: Each time a design is refined (e.g., Screen A v1 is edited to become Screen A v2), a new screen_id (v2_id) is created, and the previous screen_id (v1_id) becomes inactive for further modification.

  2. No Direct Rollback or Branching for Edits: If a user wants to revert to an earlier design state (v1_id) or make a modification that branches off from v1_id instead of v2_id, they cannot directly select v1_id and apply new edits to it.

  3. Loss of Iterative Flexibility: In real-world design, it’s common to explore a path (v1 to v2), realize a previous iteration (v1) was better for a specific aspect, or want to branch a new design direction from an older successful iteration (v1). The current system forces a forward-only modification path for any given screen_id lineage.

Impact on User Experience:

  • Hindered Iteration: Designers frequently experiment. The inability to easily go back to a specific screen_id to refine a previous idea or explore a divergent path without manually re-describing the entire older state (via generate_design) significantly slows down and complicates the iterative process.

  • Version Management Complexity: While screen_ids create a history, the inability to interact with past IDs for editing makes version management less intuitive and more cumbersome than typical design software.

  • Frustration: Users lose the flexibility expected in a creative design workflow, where revisiting and modifying past states is a fundamental requirement.

Requested Enhancement:

We request the ability to edit_design any active screen_id within the conversation history, not just the most recently generated one for a given screen lineage. This would allow users to:

  1. Select a specific screen_id (e.g., v1_id) from the history.

  2. Apply modifications to that screen_id.

  3. Generate a new screen_id (e.g., v1.1_id) that branches off from the selected v1_id, leaving v2_id intact and allowing parallel design exploration.

This enhancement would significantly improve the flexibility, efficiency, and overall user experience for iterative design work within the Gemini design tool.

3

Thank you for providing the detailed feature request regarding the need to edit previous design iterations. This is an excellent and clear feedback. The core issue—that the current edit_design function enforces a linear progression by deactivating older screen_id for further editing is a significant pain point for iterative, non-linear design workflows.
I have logged this as a high priority feature request and will pass it directly to the internal team. We appreciate you taking the time to outline this requirement as it is crucial for improving the user experience of the Stitch.