Effective use of Shiny modules in application development
summary
Shows a working Shiny app architecture that uses modules to replace duplicated UI widgets and messy reactive wiring, with one example deployed as the Ames housing data Explorer on the Shiny gallery. Explains using modules to handle persistent session state, dynamic UI and HPC integration, documents clear inputs/return lists, and demonstrates nesting modules. Warns against the reactiveValues kitchen sink hidden‑state anti‑pattern, covers when to pass static vs reactive args and the common parentheses gotcha.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:33My Journey with Shiny
- 1:22My First Attempt
- 3:15What are Modules?
- 6:24All roads lead to these principles
- 8:45Document your modules!
- 12:19Static or reactive inputs?
- 13:10Present or future value?
- 14:09Traps to avoid
- 15:38You may already know...
- 16:20What's in it for me?
- 16:44Calls to action
related talks
35mBuild Simple and Scalable Apps with Shiny
27mShiny: A GUI for the Tidyverse
19mDisposable Shiny Apps
20mBuilding a Flexible, Scaleable Self-Serve Reporting System with Shiny
44mShiny: Data-centric web applications in Python
19mFrom Concept to Impact: Building and Launching Shiny Apps in the Workplace
31mTips to Level-Up Your Shiny for Python Applications
18mShinyUiEditor: From Alpha to Powerful Shiny App Development Tool