Phone and web interfaces.
WHAT THE APPLICATION MUST DO
Show device status Present data meaningfully Allow configuration Deliver alerts Handle setup
WHAT SETUP IS
The hardest part, and the largest source of support contacts.
WHAT IT MUST HANDLE
Finding the device Transferring network credentials Confirming connection Explaining failure precisely
WHY EXPLAINING FAILURE MATTERS MOST
A generic error leaves the user with no action.
WHAT TO SHOW INSTEAD
Which step failed, and what to try.
WHAT TO DISPLAY ABOUT EVERY DEVICE
Whether it is currently reachable When it last reported Battery or power state
WHY THE SECOND ONE ALWAYS
Data without its age misleads.
WHAT ALERTS REQUIRE
Permission, requested with context Categories the user can control Restraint
WHY RESTRAINT
Excessive alerts are disabled entirely, including the important ones.
WHAT OFFLINE BEHAVIOUR SHOULD BE
Showing the last known state, labelled as such.
WHAT TO AVOID
Interfaces assuming constant connectivity Configuration that fails silently when the device is offline
WHAT TO TEST
On a modest phone, on mobile data, with the device offline.
