Running R-Shiny without a Server
summary
ShinyLive now runs R entirely in the browser via webR so a Shiny app needs no R server at runtime; the exporter turns an app directory into static HTML/JS, the online editor runs apps in-browser, and a Quarto extension embeds apps in documents — summarized as convert, fiddle, and include. It actually runs (example demo draws 100 samples for a central‑limit demo), but expect larger downloads, slower startup and some server‑only features to remain unsupported.
AI-written summary · about
chapters (9)
- 0:00The need for servers
- 2:27Understanding WebAssembly
- 4:28Technical challenges of wasm
- 6:03The birth of Shiny Live
- 10:00Converting apps to static
- 12:06Interactive app development
- 13:24Embedding with Quarto
- 15:07New possibilities and use cases
- 19:21Limitations and conclusion
related talks
20mRunning Shiny without a server
01h 44mShinylive - Running R and Python Dashboards without a Server
20mRunning Shiny without a server
20mA New Era for Shiny-based Clinical Submissions using WebAssembly
05m`livecode`: broadcast your live coding sessions from and to RStudio
44mShiny: Data-centric web applications in Python
05mWebR: R compiled for WebAssembly and running in the browser
25mReproducibility Around a Web Application
