...
Note: Test on iPad with Split view as well.
Custom messages
Playbooks has custom message blocks that provide interactive options and contextual metadata for certain messages. On mobile, these custom messages may have limited functionality based on the available feature set.
Status Update Posts
Whenever someone posts a run status update, a custom message displays the contents of the update along with metadata in the footer including the number of tasks checked (X of YY tasks done) and the current number of participants in the run. We should render the same details in the mobile app to stay consistent with the webapp.
Note that links within the status update should be tappable.
Status Update Reminders
If a run is configured to prompt participants for regular updates, the user receives a reminder message at the scheduled time when the update is due. There is a custom attachment style card attached to this reminder that has buttons to allow the user to Post an update and a dropdown to Snooze the reminder for the selected duration.
Both of these options should also be available in the mobile app.
Tapping Post Update immediately navigates the user to that run’s “Post Update” modal.
Selecting a Snooze duration offers a bottom sheet with preset intervals (15 mins, 30 mins, 1 hour, 1 day, 1 week) to delay the reminder. Selecting any of these options should delete the update reminder message and schedule the reminder to be sent after the selected duration.
If offline, the user sees an error toast; the message remains so they can retry.
Retrospective Prompt
Once a run is finished, the system posts a prompt asking whether to fill out a retrospective report.
Since the functionality to add a retrospective is not available on mobile, this custom attachment for filling out the retrospective report should not show on mobile. The message to notify users that the run as ended should only contain the text “@user marked Run Name as finished.
Edge Cases
No Connectivity:
If the user attempts to take an action like post an update or check off a task while offline, there should be a clear error message shown to the user. In case of posting an update, any data entered should not be lost and the user should stay on that screen and be allowed to copy the entered text before closing it or regaining connectivity.
No In-Progress Runs:
The runs banner is hidden in the channel. The “Playbook runs” menu item is still present, but filters default to Finished runs.
No runs at all in a channel (In-progress and Finished)
The runs banner and the “Playbook runs” menu items are hidden for the channel. This is because we don’t have the ability to start a run, hence leaving nothing for users to view or an action to take once they go to Playbook runs.
Permission Issues:
If a user is not a participant in a run, they should not see that run in the channel banner or in the playbook runs list. The run should not be counted while displaying the number of in-progress runs for that user.
...