surveydown

Note: This site only documents the {surveydown} R package - visit our main site at surveydown.org for more information!

surveydown is a flexible, open-source platform for making surveys with R, Quarto, Shiny, and Supabase.

The basic concept is:

1. Design your survey as a Quarto document using markdown and R code.
2. Convert your survey into a Shiny app that can be hosted online and sent to respondents.
3. Store your survey responses in a Supabase database (or any Postgres database).

The {surveydown} R package provides functions to bring this all together.

See the documentation to get started making your own surveydown survey!

Installation

Install R & Quarto

We also recommend working with an IDE that has good support for R, Quarto, and Shiny. RStudio is great, and we also like VSCode and Positron.

Install the {surveydown} R package

The {surveydown} R package is not yet on CRAN, but you can install the development version from GitHub with the following command in your R console:

# install.packages("remotes")
remotes::install_github("surveydown-dev/surveydown")

Version Control

We made some functions to make it easier to keep your R package up to date.

To check which version of the {surveydown} package you have installed, run:

surveydown::sd_version()

To update to the latest version of the {surveydown} package, run:

surveydown::sd_update()

Background & Motivation

Most survey platforms (e.g., Google forms, Qualtrics, etc.) use drag-and-drop interfaces to design surveys, making version control and collaboration with others difficult. They’re also not reproducible (others cannot easily reproduce a survey made on these platforms), and many require a paid subscription or license to use.

The surveydown package was designed to address these problems. As an open-source, markdown-based platform, all survey content is defined with plain text (markdown and R code) in a survey.qmd file and an app.R file that renders your survey into a Shiny app that can be hosted online. This makes your survey easy to reproduce, share, and version control with common tools like Git. The survey data collected is also owned by the survey designer in a separate Postgres database (we recommend Supabase as a free and open-source database provider).

If you’re curious where this whole idea came from, check out this blog post, which outlines more on the general idea and the motivation for it. The post is now outdated in terms of the overall package design, but it provides something of an origin story and some of the motivation for developing this project.

TODO List

This is a running list of things we’re working on / have already added to the project:

• show_if (conditionally display question)
• skip_if (conditionally skip to page)
• Set defaults for questions to not have any choices selected on launch.
• Ability to embed markdown inside choice options (like mc buttons in formr)
• Option for ignore = TRUE setting (database connection is ignored)
• Automatically include timestamps on each page and question interaction in the data
• Option to start at a designated page, e.g. start_page = 'page_name'
• A show_all_pages = TRUE argument to show all the pages and hidden questions when launched (e.g. to be able to print out the entire survey text). Could also be a sd_print_survey() function to print it to pdf.
• Set up SCSS to be compatible with Quarto-supported bootstrap themes.
• Include an optional progress bar.
• Include input checks for skip_if and show_if (question_id exists, and data frame names are correct)
• Required questions: post a popup if a question is required before allowing next button.
• Add a sd_get_data() function so the survey designer can obtain the current survey results from inside the app: https://shinysurveys.jdtrat.com/articles/get-survey-data.html
• Ability to pass url parameters, e.g. for tracking users.
• Ability to redirect users to another url.
• Admin page w/password to preview / download data (see https://github.com/daattali/shinyforms)
• Form validation: Make sure the user inputs the correct type depending on the question type. (see https://shiny.posit.co/r/reference/shiny/0.14/validate.html)
• Leverage cookies so users who close the browser can start back where they left off.
• Question types:
  • Multiple choice (single choice)
  • Multiple choice (multiple choices)
  • Select
  • Text
  • Numeric
  • Multiple choice (button…like formr mc_button)
  • Text area
  • Date
  • Slider
  • Matrix
  • Best worst

Resources / other related examples:

• shinysurveys
• shinyforms

License Information

Citation Information

If you use this package for in a publication, please cite it! You can get the citation by typing citation("surveydown") into R:

citation("surveydown")