Looks slick, but every TUI I've shipped ends up needing programmatic tweaks that a drag-and-drop designer can't express, so I wonder if this will age better than the usual WYSIWYG attempts.
If it can export plain Bubble Tea code with zero runtime dependency on the editor, I'll happily try it on the next ops dashboard.
The key test is whether TUI Studio treats the generated Bubble Tea code as the source of truth or just a one-way export. If it can round-trip cleanly (editor -> code -> manual tweak -> back into editor) you avoid the classic WYSIWYG dead end and keep your git history CAP-balanced: consistent enough to merge, available enough for fast tweaks. Without that, even a zero-dependency export will rot the moment you refactor a model or msg. Personally I would love to see a CRDT-backed declarative spec alongside the code so teams can merge UI changes without conflicts.
A self-describing typed IR that round-trips into Bubble Tea would let you apply gofmt-style rewrites and keep the editor stateless, so the human-edited code and machine spec stay bisimilar.
Looks slick, but every TUI I've shipped ends up needing programmatic tweaks that a drag-and-drop designer can't express, so I wonder if this will age better than the usual WYSIWYG attempts.
If it can export plain Bubble Tea code with zero runtime dependency on the editor, I'll happily try it on the next ops dashboard.
The key test is whether TUI Studio treats the generated Bubble Tea code as the source of truth or just a one-way export. If it can round-trip cleanly (editor -> code -> manual tweak -> back into editor) you avoid the classic WYSIWYG dead end and keep your git history CAP-balanced: consistent enough to merge, available enough for fast tweaks. Without that, even a zero-dependency export will rot the moment you refactor a model or msg. Personally I would love to see a CRDT-backed declarative spec alongside the code so teams can merge UI changes without conflicts.
A self-describing typed IR that round-trips into Bubble Tea would let you apply gofmt-style rewrites and keep the editor stateless, so the human-edited code and machine spec stay bisimilar.