TUI Studio – visual terminal UI design tool

Original Article ↗ Hacker News Discussion ↗

A new “Figma for terminals” tool called TUI Studio has drawn both enthusiasm and skepticism on Hacker News. Commenters praise the concept of a visual designer for terminal UIs, invoking nostalgia for tools like Turbo Vision and Visual Basic for DOS, but many point out that the flagship feature—code export to real TUI frameworks—is not yet functional and that the app itself is a heavy web/Electron GUI rather than a TUI. The conversation widens into a broader debate over the value of modern TUIs versus web UIs, touching on SSH use cases, keyboard-centric workflows, nostalgia-driven aesthetics, accessibility, and the growing trend of “vibe-coded” AI-generated software.

Overall reception of TUI Studio

  • Many commenters find the idea “Figma for terminals” / “Qt Designer for TUIs” very cool and original, with strong nostalgia for DOS/Borland/Visual Basic for DOS–style UI builders.
  • Others say it immediately made them want to port their apps, or that it could solve the painful trial‑and‑error layout loop common in TUI development.
  • Several people, however, note that code export is explicitly non‑functional yet, so the tool is currently just a visual mockup environment, not a full workflow solution.

Debate: TUIs vs GUIs and what a “TUI” is

  • Long argument over definitions:
    • One side: if it renders in a terminal using character cells, it’s a TUI, even with mouse, buttons, and tabs.
    • Other side: once it mimics GUI paradigms (WIMP, buttons, pointer‑centric design), it’s “a low‑res GUI larping as a TUI” and misses why people like classic TUIs (compact, keyboard‑centric, low bloat).
  • TUIs are praised for: working well over SSH, low CPU/memory, staying inside tmux, avoiding browser bloat, and sometimes improving mental focus.
  • Critics say many new TUIs are fashion/nostalgia, often less composable than classic CLIs, and worse at complex visual tasks than web UIs.

Implementation quality and AI “vibe‑coding”

  • The repo and site state that most code was generated by LLMs; several commenters call it “vibe‑coded,” arguing this explains broken or missing features.
  • Some defend AI‑assisted development as the new normal; others say AI‑generated trash is worse than human‑written trash and should not be hyped.
  • Skepticism that multi‑framework, “production‑ready” export across Textual/Ratatui/etc. is realistically achievable, at least in the current alpha.

Product choices and UX critiques

  • Many find it ironic or disappointing that:
    • The editor itself is not a TUI.
    • Even the embedded preview and site interactions lack robust keyboard navigation.
  • Performance complaints: the animated ASCII background and overall site reportedly peg a CPU core and lag on scroll.
  • macOS users hit Gatekeeper / “unidentified developer” warnings, clashing with the marketing claim of “no install fuss.”
  • Accessibility concerns: TUIs often lack the structured semantics that screen readers get from the web/OS accessibility APIs; some suggest terminal‑embedded webviews or mini webservers as better patterns.

Context: TUI hype, nostalgia, and alternatives

  • TUIs are framed as:
    • Partly nostalgia/cyberpunk aesthetics.
    • Partly a reaction to bloated Electron/web apps and desire for lightweight, portable tools.
  • Some argue we should instead build fast native GUIs or web UIs, possibly styled to look like TUIs, and expose CLIs plus optional TUI/web frontends.
  • There’s interest in related tools (Ratatui, Turbo Vision, Bubble Tea, Textual, shell‑based TUIs) and in future agent‑friendly TUIs, but also concern that terminals are being “over‑slopped” like the web.