Chapter 9 Dashboards

This document provides standards for dashboard creation, design considerations, examples of dashboard use cases, and maintenance reminders.

Dashboards in R can be as simple as a single Rmd document, and as complicated as explicit server and UI definition with submodules and javascript components. Choosing between the many options comes down to these main considerations:

• Infrastructure and Runtime Costs

• Development and Maintenance Time

• Number of Users

• Memory and Storage Requirements

9.1 Flexdashboard

For a simple dashboard meant for 1-3 persons to use and which is unlikely to change substantially, or which is for short-term use, the best solution is probably an Rmd document using the {flexdashboard} framework and specifying runtime: shiny in the configuration.

9.2 <Insert framework name>

If the project requires many users to utilize the dashboard, often concurrently, or if the project is expected to be operated long term, a more advanced and flexible framework is desirable.

9.3 Golem

Finally, for dashboards which are public facing and likely to be used en masse (guaranteeing concurrent usage), require future extensibility, then an enterprise-grade framework such as {golem} is the way to go.

9.4 Mobile-friendly

** Mobile friendly dashboards are more difficult to develop, require more long term maintenance, and often aren’t very informative, or are difficult to use. If you still find yourself needing a mobile-friendly dashboard, reference the {insert framework name} library, get ready to brush up on CSS, and good luck! **