Open kimberly-bastille opened 1 year ago
I like this idea a lot, especially for our group.
I like the idea of the app living in the package and found this example which includes a function to run the app in the package (All in one delivery!). So the user would only have to run NEFSCspatial::run_app()
to use the tool and explore the available datasets. I started a shiny-dev branch where we can develop the app and function.
Right now the app is just the "Old Faithful" default with a new name and is all in one script app.R
but we can split that out if the code gets long.
Exactly. I also have a repo where i walked through the steps of turning just a repo containing the code for an app into a package to deploy the app. However i like how the example you provided contained the ENTIRE app (server and ui) in the inst folder and not just the data
Develop a shiny app that toggles datasets on and off.
This could be a cool rollout tool for when we want to market this package to the masses.
Questions: 1) Where to store? 2) Who is developing? 3) What type of features do we want the app to include?