The Past and Future of Shiny
summary
Shiny marks ten years since its July 31, 2012 debut and claims a design breakthrough: reactive server logic inspired by Meteor’s 71 lines of code, implemented as an R-first framework and proven in a seven weeks proof of concept. The R community responds with dozens of extensions, books and a contest; Shiny is production-ready via Shinyapps.io and RStudio Connect. New work shows Shiny for Python alpha, editor tooling and a static/Wasm deploy tease and easy deployment via deploy to shinyapps.io.
AI-written summary · about
chapters (22)
- 0:00Shiny’s origin story
- 1:50Shiny born in 2012
- 3:02Early influences and manipulate
- 5:57Why Shiny avoided traditional UI
- 8:46Meteor’s reactive magic
- 12:01Shiny’s architecture vision
- 13:31Life-changing decision to create Shiny
- 17:59Proof of concept in seven weeks
- 19:02Three critical questions for Shiny
- 20:28R users ready for web apps
- 22:55R community’s overwhelming response
- 28:17Why R for Shiny
- 35:51Shiny’s success and R’s advantages
- 36:33Shiny for Python intro
- 37:46Shiny for Python state and alpha
- 41:42Shiny for Python deployment
- 43:36Running Shiny for Python without a server
- 44:40Future: R and Python together
- 45:10Visual editor for Shiny UI
- 46:14Shinytest2 and app robustness
- 47:28Thanks to Shiny team
- 48:29Q&A with Joe Cheng
related talks
44mShiny: Data-centric web applications in Python
18mDiversify Your Career with Shiny for Python
35mBuild Simple and Scalable Apps with Shiny
50mShiny in production: Principles, practices, and tools
14mR Shiny - From Conception to the Cloud
20mRunning Shiny without a server
20mWeb applications with Shiny and React and AI
20mRunning R-Shiny without a Server