Deep Feedback on Google Stitch: UI, AI Trust Issues, Advanced Canvas Management, and Full Functional Preview Requests

First, I want to thank the team for this amazing tool! The designs are incredible, generated in seconds, and the instant export to Lovable and AI Studio is an absolute game-changer. It has massive potential. However, after using it extensively, there are a few critical bottlenecks and some feature ideas that could elevate Stitch to the next level.

Here is my detailed feedback and suggestions:

1. Partial Translation / Localization Issues

  • The Issue: The interface is not fully optimized for Hebrew speakers. When trying to translate the page, the translation is only partial—some elements convert to Hebrew while others remain in English, creating a confusing and inconsistent user experience.
  • Impact: High friction for creators trying to navigate the platform fluidly due to the mixed-language interface.

2. Prompt Fidelity & False Confirmations (AI Trust Breakdown)

  • The Issue: The AI frequently fails to execute detailed, specific instructions. More critically, it consistently reports success—stating it has completed the task when no changes were actually made, or worse, when it broke existing elements or did the exact opposite.
  • Impact: Beyond the massive time loss, this creates a severe breakdown of trust between the user and the system. When the AI claims it performed an action but didn’t, the user loses confidence in the tool’s reliability.

3. Canvas Management & Lost Screens (The “Waze-like” Recentering Solution)

  • The Issue: Screens easily get “lost” on the canvas. If they accidentally shift out of frame (e.g., if a user accidentally drags a screen too far away), there is no intuitive way to locate or track them.
  • Suggested Solution: Introduce a quick “Recentering” button (similar to the “re-center” button in navigation apps like Waze) with three automatic layout options:
  1. Center All Screens: Instantly bring all scattered screens back to the center of the viewport, making it easy to find lost screens.
  2. Stack by Versions/Groups: Automatically organize screen groups vertically or sequentially based on their development stage or version, making it clear at a glance which screens are fully built and which are still in development.
  3. Order by App Flow (Hierarchical Order): Automatically arrange screens based on their actual role and flow in the app (e.g., Home Screen first, followed by subsequent screens in the user journey). This is incredibly helpful for keeping projects organized, especially for newer developers who need a visual hierarchy to keep track of the app’s structure.

:light_bulb: Major Feature Requests

A. Sidebar Navigation & Folder System

To solve both screen management and export efficiency, I highly recommend introducing a Sidebar Directory / Folder System:

  • Organized Folders: Allow users to group selected screens into custom folders for better project categorization.
  • Targeted Export: Give users the ability to select a specific folder and export only those screens directly to Lovable or AI Studio, instead of exporting the entire project every time.
  • Quick Navigation: Clicking a screen in the sidebar should instantly snap/center the canvas to that specific view, completely eliminating the issue of screens disappearing or getting lost on the canvas.

B. Full Functional Interactive Simulation (Like Lovable’s Preview Mode)

Currently, Stitch offers a basic preview, but it feels like jumping between static pages rather than interacting with a real application. I highly recommend shifting towards a **fully functional ap p simulation environment**, similar to how Lovable handles live previews:

  • True App Interaction: Instead of just browsing disconnected pages, users should be able to interact with the project as a live, cohesive system—typing and entering data (stored locally/in the browser), opening modals, navigating between real categories, and testing actual button functionalities.
  • Enhanced Debugging: Experiencing the entire application flow in real-time makes it immediately obvious what is working and what is broken, which directly improves the building process.
  • Unique Page Identifiers (IDs): Each page should have a distinct, visible ID in this mode. This will make it incredibly easy to give precise feedback to the AI (e.g., "On Page ID #04*, fix the button spacing"*), drastically reducing prompt looping and errors.

:rocket: Final Note

Despite these challenges, I want to emphasize how incredibly excited I am about this tool. I truly believe that Google Stitch has the power to completely redefine how we build software. With this level of potential, this platform is going to change everything we know and propel the entire industry years into the future. Thank you to the development team for your hard work—you are building something revolutionary!

Thank you for listening to user feedback! I look forward to seeing how Stitch evolves.

Hey @LAVIE, thank you so much for putting together such an incredibly thoughtful and detailed breakdown. This is exactly the kind of insight that turns early-stage tools into powerhouses, and you’ve identified some significant, real-world friction points.

I have reviewed every point you raised, filed the necessary feature requests and bug reports, and cross-referenced them with our current tracking backlog. The team is already working on several of these. We truly appreciate your effort and look forward to hearing more of your feedback in the future.