Rio: Web apps in pure Python

Original Article ↗ Hacker News Discussion ↗

Architecture & Runtime Model

  • Python code runs on the server (FastAPI-based); no Pyodide/WASM in-browser Python.
  • Client does as much work as possible; interactions go back to a CPython process or whatever backend FastAPI supports.
  • run_in_window() uses pywebview to wrap the app in a native webview (Electron-like for Python). Claimed cross‑platform but described as experimental with subtle issues, especially on Linux (e.g., video playback on GTK).
  • Rio’s own marketing site is reportedly built with Rio.

Target Use Cases & Audience

  • Aimed at Python-first people (data/ML, scientific computing, backend devs) who find web stacks a barrier.
  • Seen as suitable for internal tools, dashboards, and small bespoke apps where “good enough” UIs and fast iteration matter more than custom design or massive scale.
  • Not pitched as a replacement for large consumer SPAs.

Comparisons to Other Tools

  • Frequently compared to Streamlit, Reflex, Dash, Gradio, HTMX+Flask/Django, NiceGUI.
  • Streamlit seen as quick but opinionated and awkward for complex multi-page apps; Rio viewed as more general UI framework.
  • Reflex praised as a Python wrapper over React but inherits JS/React constraints; Rio keeps state and callbacks purely in Python.
  • Some argue existing stacks (HTML/CSS + Flask + HTMX, or just modern JS with web components) are simpler and more flexible.

UI Model, Naming, and Styling

  • Components are Python classes (e.g., Text) with properties like justify, mapped under the hood to HTML/CSS (e.g., span, text-align).
  • Supporters say these names are more approachable to non-web devs, analogous to Python’s list/dict vs arrays/hashtables.
  • Critics argue renaming breaks alignment with web platform docs and complicates the inevitable need to understand HTML/CSS semantics.
  • Default styling is Material Design; claims that with low-level primitives (e.g., rectangles) you can build visually distinct, even retro, UIs.

Debugging, Layout & Tooling

  • Rio provides built-in dev tools that explain layout decisions in plain language (why a button got a given width, alignment, etc.).
  • Some say this makes layout debugging easier than wrestling with CSS; others are skeptical that abstraction avoids real web‑debugging issues long term.

Critiques & Concerns

  • Concerns about in-memory state and simple SQLite-based auth patterns compared to mature frameworks (e.g., Django).
  • Worries about performance, longevity, learning yet another niche framework, and difficulty once you hit its abstraction limits.
  • Skepticism toward “no HTML/CSS/JS needed” marketing; many say such abstractions work until you need to debug or step outside the framework.
  • Others welcome experimentation and see value even if Rio never becomes mainstream.