CRM Mobile App
Recruiters and account managers use the mobile app to work on the go.
Bullhorn is the leading ATS (Application Tracking System) and CRM (Customer Relationship Management) software for staffing agencies.
Staffing firms' users travel often and they need a good mobile experience when on the go. Before this mobile app, they primarily used Bullhorn's mobile site, a mere reduction of the web app, which was designed with few considerations given to the unique needs of users who are out of the office.
As the sole owner of UX of the product, the deliverables I produced include:
Account Manager - Mary
Recruiter - John
Find critical information, and perform key actions quickly to ensure successful meetings with clients and candidates.
Based on the research, we decided that just a more user-friendly mobile experience is not enough. We came up with 2 additional functionalities exclusively for the mobile app.
Today - A feature that that predicts what users need right here right now. For example, an upcoming meeting with a candidate will be listed here with all associated records at hand. Within a handful of taps, a user can call the candidate, pull up the resume and add notes.
Calls - The feature looks at the user’s call log and reminds them to take notes about these calls so they become a public record within the team.
The "Calls" feature doesn’t directly address the needs of users. Instead, it focuses on the needs of the businesses where users work. For each user research project that would impact the business, I always interview a couple of business owners and system admins to understand the business’ perspective and ensure our product benefits their bottom line.
Then for the regular CRM part, the experience is optimized based on the use cases we summarized during research.
Part of the IA document.
Due to the shortage of development resources, this app was built as a hybrid app, meaning it's essentially a web app with a native wrapper. What it meant for me is that I couldn't design system-specific experiences for each platform. Android and iOS users would see the same version of the app.
The good news is, all Bullhorn mobile users do have one app they use several hours a day - the Bullhorn web app. if I use patterns similar to the web app, it doesn't take long for users to figure it out, even though it's not how most of their mobile system apps work. So that's exactly what I did.
When I did have to pick a mobile specific pattern for which there is no similar patterns on the web app, I picked the one that makes the most sense either through looking at the context, or testing with real users from each platform.
On the web app, the navigation system has a flat organization, with all menu items on the same level. In some early iterations, I tried to keep the same paradigm using the material design's drawer component.
Through review and testing, I opted out of this approach because:
I tried out a few of different ideas and finally landed with a hybrid approach, with elements drawn from both iOS and material design paradigms, while keeping it visually similar with the web app.
On the web app, all filters are visible on the search results page. To move that experience to a small mobile screen, my first approach is putting all filters on a separate page, launched by tapping on the filter icon in the search bar.
Through testing and review, I found that:
After more sketching and research on search patterns on other mobile apps, I landed on the final design:
There is a widget in the users' dashboard on the web app. It tracks a user's phone conversations with their clients and candidates, which is a selling point because users don't have to log these calls manually if they have the app.
After MVP, we planned to add a dashboard feature, for which I designed a dozen types of data visualization.
I also explored animation for the onboarding screens.