A New Era for Shiny-based Clinical Submissions using WebAssembly
summary
A working submission prototype packages a Shiny app so a reviewer extracts a bundle and launches it in a browser instead of installing R, Rtools and hundreds of packages; Pilot 2 produced a usable app from CDISC ADaM data and Pilot 4 uses WebR plus shinylive to run R in-browser, swapping the server engine for the client and reducing setup from many steps to one. Development required swapping golem for the rhino framework, using renv-like frozen dependencies, Windows VM testing with quickEMU, Appsilon and Docker support, and careful handling of injected datasets for security.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:58The R Submissions Working Group
- 3:29Why am I so excited
- 5:30How does Shiny work
- 11:45Dependencies
- 12:57What does this actually look like
- 13:41The power of interactivity
- 15:04A bright future
- 16:57Team effort
- 18:04Conclusion
- 18:58Security Concerns
related talks
01h 44mShinylive - Running R and Python Dashboards without a Server
20mRunning Shiny without a server
14mR Shiny - From Conception to the Cloud
20mRunning R-Shiny without a Server- 14mR Shiny - From Conception to the Cloud
20mWeb applications with Shiny and React and AI
18mShiny New Tools for Scaling your Shiny Apps- 20mRunning Shiny without a server