Zwift began manufacturing their own hardware to enhance the overall software experience. This included a multitude of different pieces of equipment, each with their own unique iterative firmware. Users with any of these pieces of hardware will have access to firmware updates for their devices, and this was a novel piece of functionality for the organization. Previously all hardware used on the platform was from 3rd party manufacturers.
My role
Lead Product Designer
Team
Cross-functional product team. Including:
- Project Manager
- Engineering Manager
- iOS Engineer
- Android Engineer
- QA Tester
- QA Automation Engineer
Problem / Challenges:
Zwift offers several pieces of hardware all of which have their own software/firmware configuration. Some items are treated as stand-alone unique items, while others (specifically the Zwift Play controllers) are two unique pieces that are treated as one.
The design/experience for the user should feel seamless and be on par with other firmware update processes in the market, while integrating these unique challenges.
Solution:
The solution for users having Self-Service firmware updates is direct access to their hardware details and firmware update functionality in the Zwift Companion app.
Users will pair their devices, be notified of firmware updates, self service their update, and discover release notes and device details all in one easy to use space.
Zwift Play Firmware Update Happy Path:
2 devices treated as 1.
Dealing with outliers
- Multiple devices found (user has more than 1 set of controllers, or past controllers remembered by the device)
- Battery life too low
- Controllers not found
- Removing past devices
- Disconnects during update
- etc..
See It In Action:
- Platform – Android
- 4 devices (2 pairs)