Disposable Shiny Apps
summary
Claims that a typical week of Shiny work becomes hours, demonstrated by a twin potty training command center built in about 12 minutes using Positron Assistant (Shiny extension) with Claude Sonnet 4, bslib, brand.yaml, Ellmer and shinychat, then deployed to Posit Connect. App tracks Henry and Penelope, shows a parental sanity meter and a motivational chatbot; initial run fails but is fixed after three iterations. Argument: start with one clear intent, accept throwaway lifecycle, use push‑button deploy to make interactive demos practical.
AI-written summary · about
chapters (18)
- 0:00Disposable Shiny apps intro
- 1:04Long-lived apps pain
- 2:54Engagement vs slides
- 3:40Power of disposable apps
- 4:22AI accelerates creation
- 6:55Crafting Shiny prompts
- 8:42Rapid dev tools/workflow
- 10:26Push-button deployments
- 11:07Support concerns
- 11:49Managing app sprawl
- 12:52Work vs slides?
- 13:53Mindset shift
- 14:16Challenge: build disposable
- 14:45Q&A: User input
- 15:50Q&A: Prevent crashes
- 16:31Q&A: Org prep
- 17:36Q&A: Share without accounts
- 18:19Q&A: Workflow trade-offs
related talks
19mFrom Concept to Impact: Building and Launching Shiny Apps in the Workplace
27mShiny: A GUI for the Tidyverse
35mBuild Simple and Scalable Apps with Shiny
21mEffective use of Shiny modules in application development
44mShiny: Data-centric web applications in Python
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
20mBuilding a Flexible, Scaleable Self-Serve Reporting System with Shiny
18mBuilding an AB testing analytics system with R and Shiny