Prompted by a question internal to SU about best practices and how we work with Shiny.
I suspect we'd mention things like:
- modularity
- {bslib}
- testing, e.g. snapshots, mocking, {shinytest2}
- data sourcing/loading
- philosophy of {golem}/{nolem}
- strategies to limit RAM use
- when Shiny isn't the right tool for the job
Add more ideas below.
Related to the suggested Shiny C&C session: #238.
Prompted by a question internal to SU about best practices and how we work with Shiny.
I suspect we'd mention things like:
Add more ideas below.
Related to the suggested Shiny C&C session: #238.