Hi @RISHABH_CHAUHAN,
First, I want to appreciate the direction Stitch is taking, especially with the MCP Server and IDE integration. As a founder managing multiple startups, the dream of a “Design-to-Code” pipeline is exactly what I need to accelerate my MVPs.
However, after extensively testing the current models (including Pro), I’ve hit a significant roadblock that prevents me from using Stitch for production: The model lacks “Native Mobile” DNA.
I attempted to design a minimalist, futuristic iOS utility (think “Liquid Glass” aesthetics, MeshGradients, and native blur materials). Instead of generating a clean, haptic-focused mobile interface, the model hallucinated a sci-fi “Power Plant” dashboard with generic web-style cards and non-native elements.
The Gap: It feels like Stitch is heavily biased towards Web/CSS paradigms. It struggles to distinguish between a “Web Dashboard” and a “Native Mobile App.” It doesn’t seem to “think” in SwiftUI primitives (Materials, Springs, VStacks, Dynamic Islands).
My Request: For us mobile founders, we need a “Native Mobile First” mode. We need a model that:
-
Understands Modern HIG: Knows that “Energy” in a mobile context often means “Wellness/Tracking,” not “Kilowatts/Voltage.”
-
Native Materials: Prioritizes native system materials (UltraThinMaterial, MeshGradient) over solid hex colors or custom PNG assets.
-
Mobile Ergonomics: Understands reachability, touch targets, and the difference between a mouse click and a finger tap.
I really want to make Stitch my primary prototyping tool, but until it speaks “Native iOS,” I’m forced to stick to manual coding for that high-end feel.
Looking forward to seeing this evolve!