Crucial tasks that will take considerable time

[maurolepore]

Here are a few epics we'll need to figure out. Each deserves multiple issues but I collect them here put them under our radar ASAP.

• 94

It's still unclear how exactly we'll implement the requirements. However, considering our permissive access and the intent of usage -- it seems possible to start with something super simple, such as replacing "download data" with "request data" and link to a google form where the user registers their personal details, agreement, and email. Then we manually email the data. This meets the following requirements:

• Leaves a record of who agrees to our conditions
• Delivers the data only if the email is valid.

It may not scale up to a great number of users, but I don't worry about that for now since the first bottleneck will be the app's inability to serve many users.

• 95

Currently the app likely fails to serve more than one user at the time. The second and subsequent concurrent users get a horrible user experience. They would only notice the app doesn't load or is unresponsive.

Paid solutions aliviate this problem

https://docs.posit.co/shinyapps.io/guide/applications/#application-instances

The maximum number of instances you can add is governed by your subscription plan:

• 96

If the real data is large, it may be hard or impossible to deploy it along with the app. Instead we may need to host the data separately. The app would then be trully only a front end with the data stored in some kind of database.

[maurolepore]

I'm closing as not planned to avoid duplicating issues that are already more granular