Multipurpose interruption feature

[stenington]

The AIFC has introduced the need to interrupt users on the platform at different points in time to ask them to complete consent forms or do surveys, and that's likely to continue year to year as we ask them to do preliminary work for a given season, even as a returning user. This year we relied heavily on the family account signup process to collect the necessary information, but we won't necessarily be able to do that in the future in the same way (unless we delete accounts year to year).

[hellafitz]

Assumption (based on past one-off interruption features): this would actually block users from doing anything else until they complete a required action referenced by the interrupting message.

Q for Program: is this still relevant?

[hellafitz]

A: yes. Particularly if it could be used to gather impact data from educators post-registration

[hellafitz]

A related resource on designing banner alerts for disasters, by a DevSummit friend https://blog.kalamuna.com/news/web-design-disaster-part-1-alert-your-users?utm_medium=social-organic&utm_source=twitter&utm_campaign=knowledge-sharing&utm_content=2020-04-01

[hellafitz]

• hard vs soft interrupt (i.e. are they required to do something before they can proceed doing anything else?)
• targetable to specific user types and account characteristics? (e.g. appears only for returning families?)
• what are examples of the multiple purposes (surveys, consent forms, other stuff tbd)?
• is this to make this DIY for an admin, or strengthen our developer toolkit/framework to do this?