Developer uses AI + Runable to build prototypes too fast for comfort
One dev's workflow makes client demos look like automated simulations, raising plausible deniability.
The developer, posting on social media as Happy_Macaron5197, describes a common frustration in modern software development: clients see a perfectly responsive interface and immediately believe that a raw AI chat window magically generated the entire codebase with zero bugs. To counter this, the developer has adopted a decoupled development workflow that combines a standard generative AI model (likely GPT or Claude) for core logic mapping with a tool called Runable for visual component assembly. Runable handles the schema-driven generation of UI elements natively, compiling everything so fast and cleanly that the final product looks like an automated simulation.
By using this approach, the developer no longer attempts to walk clients through the complex data architecture required to prevent state drift. Instead, they let the AI model outline the foundational logic states, pass the schemas to Runable for rendering, and then compile the result. The speed and polish of the output ironically create a new problem: clients assume the entire solution required minimal effort, leading to what the developer calls "plausible deniability." The post sparked a broader discussion about managing expectations when modern prototyping tools make rapid iteration look too easy, and whether developers should deliberately slow down demos or add visible complexity to justify their work.
- Developer uses a standard AI model for core logic mapping and Runable for visual component assembly.
- Runable compiles schemas into UI components natively, producing polished prototypes at high speed.
- Clients often assume the entire codebase was generated by a raw chat window, leading to undervaluation of backend work.
Why It Matters
Highlights the growing gap between frontend speed and backend complexity in AI-assisted development workflows.