ML-552 ⁃ Scheduling of activities

[odziem]

Rewrite activity scheduling logic including:

• bucketing of activities into in-progress, due, scheduled, unscheduled, and completed
• fetching the dayspan schedule from the getApplets API request
• fetching response times from the getSchedule API request
• reminder dots on activities and applets
• reminder notifications

The complete list of activity buckets is:

• In Progress, for activities that have been started but not completed.
• Due, for activities currently scheduled - or - previously scheduled and not yet completed.
• Scheduled, for activities scheduled some time in the future.
• Unscheduled, for activities with no schedule.
• Completed, for activities which have been completed and have no more scheduled occurrences.

Activity currently due:

Activity completed and scheduled for next day:

[binarybottle]

I liked the previous "Due: Today..." vs. "Due on: Today..."
For parallel structure, I would use "Scheduled: Nov..." rather than "Scheduled for: Nov..."

[binarybottle]

I'm confused about the times in the screen capture -- the phone's time is 2:18, which I assume is 2:18pm, so it makes sense that 11am's activity is due (or technically overdue, depending on what the expected response time window would be, were we to set that), but why would the evening's notification be "Scheduled" for the next day, rather than later in the same day?

[odziem]

@binarybottle The previous screenshots demonstrated that the actual schedule can be arbitrary for each activity, e.g. the "Evening" activity can be scheduled for the morning. I've updated the description with screenshots demonstrating a more realistic scenario. Sorry for the confusion. 😄

The current screenshots show a scenario where the morning activity is scheduled between 10am-1pm and the evening activity is scheduled between 3pm-7pm.

On the topic of the due date label - this is something I'm hoping to change in a subsequent PR. Currently the date/time displaying after "Due on:" is the beginning of the scheduled interval for the activity. Semantically it would make more sense for the date/time to be the end of the interval the activity should be completed by. When I make that change I can also update the label to remove the "on".

[shnizzedy]

Looks great to me. 🎉

On the topic of the due date label - this is something I'm hoping to change in a subsequent PR. Currently the date/time displaying after "Due on:" is the beginning of the scheduled interval for the activity. Semantically it would make more sense for the date/time to be the end of the interval the activity should be completed by. When I make that change I can also update the label to remove the "on".

― #302 (comment)

My thoughts as well. @binarybottle can we go ahead and merge this PR and leave the label for a later PR?