Abstract
Growing interest in data-driven, decision-support tools across the life sciences and physical sciences has motivated development of web applications, also known as web apps. Web apps can help disseminate research findings and present research outputs in ways that are more accessible and meaningful to the general public--from individuals, to governments, to companies. Specifically, web apps enable exploration of scenario testing and policy analysis (i.e., to answer “what if?”) as well as co-evolution of scientific and public knowledge. However, the majority of researchers developing web apps receive little formal training or technical guidance on how to develop and evaluate the effectiveness of their web-based decision support tools. Take some of us for example. We (Saia and Nelson) are agricultural and environmental engineers with little experience in web app development, but we are interested in creating web apps to support sustainable aquaculture production in the Southeast. We had user (i.e., shellfish growers) interest, a goal in mind (i.e., develop a new forecast product and decision-support tool for shellfish aquaculturalists), and received funding to support this work. Yet, we experienced several unexpected hurdles from the start of our project that ended up being fairly common hiccups to the seasoned web app developers among us (Young, Parham). As a result, we share the following Ten Simple Rules, which highlight take home messages, including lessons learned and practical tips, of our experience as burgeoning web app developers. We hope researchers interested in developing web apps draw insights from our (in)experience as they set out on their decision support tool development journey.
Highlights
Web applications, known as web apps, are increasingly common in the research communication portfolios of those working in the life sciences (e.g., [1]) and physical sciences (e.g., [2,3,4])
Examples of web apps range from interactive maps depicting disease transmission (e.g., [9]), marine health (e.g., [10,11]), natural hazards (e.g., [12,13]), and pest infestations (e.g., [14,15]) to bioinformatics resource collections (e.g., [16]), to omics data analysis platforms (e.g., [17]), and to citation visualization tools (e.g., [18]), among others. Throughout this ten simple rules paper, we focus on web apps that help stakeholders make decisions by improving their access to information
To illustrate how contracts and mock-ups are drafted in practice, we offer the final version of the ShellCast contract complete with mock-ups (S2 Text, S1 Fig)
Summary
Citation: Saia SM, Nelson NG, Young SN, Parham S, Vandegrift M (2022) Ten simple rules for researchers who want to develop web apps. PLoS Comput Biol 18(1): e1009663. https://doi.org/ 10.1371/journal.pcbi.1009663 Funding: This work was supported in part by the North Carolina Sea Grant R/20-SFA-4 (NGN, SMS, SP), United States Department of Agriculture (USDA) Food and Agriculture Cyberinformatics Tools (FACT) project 2019-67021-29936 (NGN, SMS), and USDA National Institute of Food and Agriculture (NIFA) Hatch projects 1021499 (SNY) and 1016068 (NGN). The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript. Competing interests: The authors have declared that no competing interests exist.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
