Love what Claude shipped with Cowork Artifacts but generating code for Generative UI is the wrong…
Rabi Shanker Guha
在 X 上查看@rabi_guha2550 位关注者
46,745 次观看
Love what Claude shipped with Cowork Artifacts but generating code for Generative UI is the wrong architecture
Wasteful: A single dashboard costs 2k boilterplate React/HTML tokens before any meaningful pixel is streamed
Inconsistent: Two dashboards generated 5 mins apart don't feel like the same product. No design system. No shared components. Every output is a one off
Security Liability: Today its a single-user sandboxed demo. But real software has shared dashboards, team views, embedded reports - LLM generated code for one user running in another user's session. Sandboxed or not, that's OWASP LLM05 territory.
Multi-surface: A dashboard generated for desktop never works reliably on mobile. Want to render it on an iPhone? Your only option is an iframe. Yuck.
Unstreamable: Partial code is extremely hard to stream meaningfully. What you get is hundreds of chunks of broken renders that flash and flicker. That's not progressive UI - that's broken UX.
Code generation is a great starting point. It's not a production architecture.
Generative UI in production needs an abstraction layer. The model describes intent. The renderer owns the pixels. Everything else is a liability.
评论
评论来自 X (Twitter) 上的原帖
暂无评论
