The immediate problem I encountered was its scrolling and anchoring interaction. Tapping on a category where no data exists results in no action, with the user thinking maybe it’s a bug. The user also needs to take an added step to see all the requests coming in.
Rethinking the sub-navigation
I first addressed the problems of the second tier navigation and proposed swiping between content, with all the requests living within the designated page. Not only is it clear what content lives underneath, we minimize the amount of clicks for the user to get to his or her data.
Clean up, minimize, standardize
From above, the initial layout (1) strays away from current patterns existing within the desktop app (2) confuses the user with the icon and color blocking, looking like an add contact button.
In the desktop application, Zap already assigns contacts a “ZapScore,” which reflects a contact’s online activity and engagement level. Higher ZapScores indicate which prospects are “hot” (and therefore a potentially higher ROI for business) versus “cold” clients.
Here, we leverage ZapScore clearly in order to establish a clear hierarchy for actionable items, so that the user can quickly determine which clients to prioritize.
The current proposed layout for reminders is also confusing. Here, we treat reminders as actionable checklists, with clear separation between overdue and upcoming tasks, so users can get ahead.
Within the real estate industry, agents and brokers are subject to compliance requirements from their brokers, which dictates how often clients should be contacted. In the prior design, it is unclear whether the color-coding measured client activity or indicated past and upcoming deadlines.
In the revised design, I leveraged ZapScore to give a clear indicator on which clients to prioritize contact with, and visually highlighted upcoming or past deadlines.
By launch, we were able to release a more polished and intuitive product.