Problem
The new SpeziScheduler currently supports card-like UI to present upcoming events (see #44). We currently do not support other ways of visualizing events to the user.
Solution
In certain scenarios it might be great to provide simple checklist-style UI for reminder-like events (e.g., take medication). This UI components should be able to combine multiple events. For example a medication task might schedule its events multiple times in the day. Therefore, the checklist should show all events of this task in a single view, visualizing which events have been marked as completed and which are left as a todo.
Additional context
This UI component might benefit from infrastructure to provide naming to Occurrences of a Schedule. For example a Schedule that repeats everyday at 8am, 1pm and 6pm might receive labels like Breakfast, Lunch, Dinner to better describe their meaning. This is currently not possible , as all these occurrences are describe with a single RecurrenceRule that doesn't allow to store additional data.
A simple solution could be to provide a list of labels each associated with a time interval. For example the Breakfast label could be applied for any events occurring between 6am and 9am. We would need to investigate what the exact use case of such labels is, and if a time-interval-based solution is sufficient for these use cases.
We should additionally explore if we want to support marking tasks as overdue in existing UI.
Code of Conduct
Problem
The new SpeziScheduler currently supports card-like UI to present upcoming events (see #44). We currently do not support other ways of visualizing events to the user.
Solution
In certain scenarios it might be great to provide simple checklist-style UI for reminder-like events (e.g., take medication). This UI components should be able to combine multiple events. For example a medication task might schedule its events multiple times in the day. Therefore, the checklist should show all events of this task in a single view, visualizing which events have been marked as completed and which are left as a todo.
Additional context
This UI component might benefit from infrastructure to provide naming to Occurrences of a Schedule. For example a Schedule that repeats everyday at 8am, 1pm and 6pm might receive labels like Breakfast, Lunch, Dinner to better describe their meaning. This is currently not possible , as all these occurrences are describe with a single
RecurrenceRulethat doesn't allow to store additional data.A simple solution could be to provide a list of labels each associated with a time interval. For example the Breakfast label could be applied for any events occurring between 6am and 9am. We would need to investigate what the exact use case of such labels is, and if a time-interval-based solution is sufficient for these use cases.
We should additionally explore if we want to support marking tasks as overdue in existing UI.
Code of Conduct