Iflexion’s team split the project into three iterations:
- User profile analysis, where we elaborated user scenarios and prioritized features.
- User flows, where we defined how to transform a complicated measurement process into a cohesive and intuitive experience.
- UI design, where we prepared and implemented UI artifacts.
User Profile Analysis
Our team started with the analysis of target user groups and the UX flows, which incorporated the customer’s profound knowledge of game-specific details, user needs, and expected parameters.
We expanded the user roles originally found in the PoC and added three main user groups altogether, based on their particular goals and requirements:
Casual players
This group includes people interested in tracking their own performance. Their main goals are to easily capture their results, view the detailed history of throws, and share their achievements on social media.
We defined their key expectations from the app as an intuitive and sleek setup and one-off settings configuration.
Coaches
This group includes people interested in tracking results of multiple players during trainings and viewing a detailed history with advanced charts for a particular player.
Besides the same requirements for easy setup and configuration, coaches expect to be able to manage one or multiple teams as well as to quickly switch between players.
Sport fans
This group includes people interested in tracking professional players’ results during a live game.
Sport fans want to track ball speed from any section of the stadium, expecting the so-called ‘freedom of location’ as the app owners dubbed it. Fans too expect an intuitive setup and quick switching from one player’s statistics to another’s.
User Flows
Our team came up with detailed user scenarios to optimize interaction with the app. The challenge was in making complicated flows quick, easy and clear for users while keeping all the required steps, such as entering parameters and setting up the camera for precise measurement.
A User Flow Example
The launch flow. This flow includes the initial steps needed to set up the application for speed measurement. We minimized the number of actions and settings required for the first throw, in order to start tracking results immediately. We also separated basic settings from advanced ones to let users adjust basic settings first and start measuring right away, leaving advanced settings for further fine-grained configuration.
UI Design
Once we elaborated the flows for all the user groups, we moved on to preparing UI artifacts.
First Launch
The first launch flow covers initial actions for starting measuring ball speed. We divided the settings into required and optional. Users can finish configuring settings when they see the screen saying ‘Congratulations!’ and the buttons for skipping or continuing the setup of additional features.
Switch Player and Player Profile Screens
Considering the difficult stadium conditions for tracking results during a live game, it was important to create convenient navigation for viewing the results, quickly switching between players, and starting a new session.
To avoid overloading the results display, we designed a separate screen for player profiles with their results and a main screen with an active player view and action buttons. This way, users can quickly select a new player or change the mode without leaving the screen, and view a player’s details on another screen.
Field View
For the integrated math algorithm to calculate precise ball speed, users need to set accurate parameters, including the field size and distance. To facilitate this, we designed different game field types that match real-life field parameters with a high degree of accuracy.
Session Results
The challenge was to make a large set of calculations fit on a mobile screen. To solve the task, we applied several solutions:
- Option buttons for switching between basic and advanced charts
- Average results placed above raw data for quick analysis
- Hints and guiding elements
Advanced Settings
Users can increase measurement precision if they adjust advanced settings.
Initially, the customer planned to place all the settings on one screen. As the screen became overloaded, we broke it down into three screens with one setting per each. We also suggested adding tips for each setting describing its importance for getting precise results.
Results Screen
This is the screen with pitching or hitting results of a single attempt. The screen has options for quick switching to another player as well as ending a current session and returning to the main screen with all the previously adjusted settings retained. Users can also share their results on Facebook, Twitter, or via email.
To switch a player, users just need to click the button with the active player’s name and choose a new player. The buttons are distinct in the clear-cut screen interface.