Suggestions for improvements of online demo instance
As a side-effect of Aura's ongoing development and intensified user testing, requests and suggestions for improving the functionality provided by our online demo instance (dashboard.aura.radio) keep coming up. These shall be collected in this ticket to be reviewed in further discussion, before deciding on concrete improvements of our current setup.
Requests and Issues to be addressed:
- stability: dashboard.aura.radio is deployed daily on the current development status. this provides the change to test brand-new dashboard developments quickly, but unstable / broken features can block the usage of the demo instance and thus can have an impact on the user testing progress. One idea was to have two demo instances: one with daily updates on the current dev status, one that runs on the latest stable release, or at least is deployed/updated less frequently.
- every radio dataset only holds the recurrence rules that are in use for the specific station. (Thus, at the moment, the demo instance only presents rrules of RH because the dataset was taken from there) If we want to provide all of Aura's capabilities in the demo instance for user testing, then we should add more rrules to the database give users an overview of the full scope of that feature.
- deployment: the current instance of dashboard.aura.radio does not yet use the latest autodeployment routine. Do we want to update this?
We should discuss these topics with regard to the different needs and timeframes of test settings (acceptance testing vs. beta-testing) before deciding on how to adapt our demo instance.