Project: Mobile Availability Management
Role: UI/UX Designer
Platform: Mobile
Tools: Figma
Objective: Simplify the process of selecting and submitting availability.
The Problem
Existing Calendar UI
Existing Calendar UI
Existing Date Selector UI
Existing Date Selector UI
Existing Availability UI
Existing Availability UI
From the experiences of fellow co-workers, and also my own personal use of the app, the issues of the existing availability flow were as follows:
1. Availability and unavailability are separated into two concepts
2. The vertically scrolling list creates unnecessary confusion with the relationship between the dates they represent
3. No clear way to select a range of dates
4. Existing or pending requests were not accounted for when creating a new availability request
5. Clarity with what was about to be submitted by the user was lacking
The idea was to consolidate the elements of the current UI into a more concise and easy to understand calendar design, similar to that of the Apple Calendar app. Using this flow, the user would find it easier to navigate and would be able to review their selected dates and make any adjustments if needed.
Date Selection
Iteration 1
Iteration 1
Iteration 2
Iteration 2
Iteration 3
Iteration 3
Iteration 3 cont.
Iteration 3 cont.
To combat issues with date selection, the new UI merges two screens into one succinct calendar format. The user also now receives instant feedback of their selection with the summary of changes at the bottom of the screen. These changes allow the user to understand the dates they have selected at a glance.
When selecting two dates, The new UI gives the user the choice of whether to select them as two separate entities, or as a range including all days in-between. This improvement in ease of use creates less confusion and provides a better experience for the user.
Conflicting Dates
Iteration 1
Iteration 1
Iteration 2
Iteration 2
Iteration 2 cont.
Iteration 2 cont.
Within the new calendar UI, dates from previously submitted requests are marked for the user. If the user then selects a marked date, the summary card will appear in red to let them know that there is a conflict with this specific day. If the user then tries to submit a request that contains a flagged date, an error message appears that gives the user the option to either resolve the problem, or continue without the offending dates.
Submission Page
The final submission screen gives the user the chance to further review their changes before sending the request. There is also the option to edit a request once it has been submitted for any last minute changes.
Reflection
This project showed how something as simple as an availability calendar can become much more complex when things like date ranges and conflicting dates become involved.
The main focus with this design was to give the user the reassurance that what they were selecting was being interpreted by the calendar in the correct way. Through the incorporation of the summary of changes and confirming date ranges and conflicts, I think this goal was achieved.
If I were to continue this project, the next step would be to utilise usability testing in order to validate some of the assumptions made within the redesign.

You may also like

↑Back to Top