So we have to make our plots, downloads, etc in the server There is no active code running in the ui at any time - all changes seen in the UI are passed through the server (more or less). The most important thing to understand about the UI is that it receives inputs from the user and displays outputs from the server. HTML and CSS elements (addressed later).Navigation aspects of an app - tabs, panes, etc.Plots, tables, etc - outputs that are generated with R code.“Widgets” - dropdown menus, check boxes, sliders, etc that can be interacted with by the user.This means everything that is displayed in the UI of an app. The UI element of a shiny app is, on a basic level, R code that creates an HTML interface. Put simply, these are two objects that are interacting with each other whenever the user interacts with the shiny app. We next need to understand what the server and ui objects actually do. R files in our structure that we can source() into our app.

Note: we can also (and we should if we have a larger app) have other. These objects must be defined in every shiny app and are central to the structure of the app itself! In fact, the only difference between the two file structures described above is that in structure 1, both ui and server are defined in one file, whereas in structure 2 they are defined in separate files. If you open this file, you’ll notice that two objects are defined - one called ui and another called server. # an example of app.R library ( shiny ) ui <- fluidPage ( # Application title titlePanel ( 'My app' ), # Sidebar with a slider input widget sidebarLayout ( sidebarPanel ( sliderInput ( 'input_1' ) ), # Show a plot mainPanel ( plotOutput ( 'my_plot' ) ) ) ) # Define server logic required to draw a histogram server <- function ( input, output ) # Run the application shinyApp (ui = ui, server = server ) 46 Version control and collaboration with Git and Github.33 Demographic pyramids and Likert-scales.

19 Univariate and multivariable regression.

Rstudio shiny dashboard