Software Update Protocol
Background
Originally, the software update protocol was offered to users, asking if they would like to update. Providing only two options:
• Yes
• No
The 'yes' being the 'OK' button and the 'no' being the 'X' button.
Update Available
Update Prompt
Update Enhancement Process pt. 1
In order to prioritize a more understandable and transparent flow, we have to understand the following philosophies outlined by Jakob Nielsen from Nielsen-Norman Group (NN/g):
• Users don't understand where they are in an information architecture
• If a page does not appear relevant to the user's current goals, the user will ruthlessly click the Back button after 2-3 seconds
• If users don't understand a certain design element, they don't spend time learning it - instead, they ignore it
So, why does this matter?
In the original design, users are offered the update and taken to the settings page.
If the user is not wanting the update, they will need an exit strategy.
The prompts given to the user are slightly vague, one is an 'OK' and the other is an 'X' symbol. It's possible to be more direct and employ modern design techniques. This increases transparency from the system to the user and they are more aware of their actions.
The consequences of the 'X' symbol can vary. Users may not have any idea what happens after 'canceling' the update. Will it come back? When? How do I find it again?
Original Flow
Updated Flow
Update Enhancement Process pt. 2
Factory-shipped watches may be sitting in boxes for long periods of time and have an earlier firmware version.
The new update protocol now directs that users should be prompted to update right after their pairing process.
This ensures that the best possible version of the product is introduced in exchange for some of their newly unboxed patience. If not, the user can postpone the update for 24 hours until prompted again.
FOTA (Firmware-Over-The-Air) Enhanced Flow after Pairing