IoT Notification Designer
IoT Notification Designer
Design Effective Alert Systems
Interactive game
Attention design
IoT Notification Designer
Design IoT alert strategies that reach people when action matters without creating notification fatigue.
10Scenarios
6Channels
30Points each
Try
Choose urgency, delivery channels, quiet hours, bundling, and a rate cap, then press Check. Each scenario is scored once; Reset clears only unscored choices.
Observe
Latest shows up to 30 points: urgency 7, channels 10, quiet hours 5, bundling 4, and rate cap 4. Optimal requires 30/30.
Explain
In scenario 1, urgency sets interruption cost and the recipient needs a clear next action; louder delivery cannot repair ambiguous content.
Technical boundaries. The checker scores fixed urgency, channel, quiet-hours, bundling, and rate-cap choices, not message wording or requested actions. Meter indices and rate caps are illustrative exercise values, not delivery probabilities or alarm standards. Rate caps apply to repeat app messages, never to the local safety alarm. It does not simulate delivery failure, alert fatigue over time, accessibility testing, localization, user consent changes, escalation staffing, or emergency-service obligations.
Notification Scenario Workbench
Progress
Scenario 1 of 10
0Score
0/30Latest
0Optimal
Loading notification scenarios...
Reference Material
Loading notification design notes...