Refactoring app navigation and the browsing experience.
Rapchat’s most engaged with feature by far, is beats. Users spend hours each day browsing for beats that they like and want to record over. But the experience of browsing for beats and inspiration was sub-par.
I was tasked to lead the refactoring of the entire browse experience, which comprised of standard track browsing, the top 100, beats, and producers.
The most used feature within the app is hidden within the overcrowded browse tab and is not frequently updated with fresh content – letting users run out of new beats.
When I arrived at Rapchat, the founders were sitting on a wealth of user feedback explaining their frustrations with beat discoverability – it just hadn’t been properly addressed.
This project took 6 weeks with our small team:
Before diving into research I wanted to get as clear as possible around what the problem was. To do this, I created a hierarchy map to showcase the inequalities within the various tabs.
This helped me visualize part of the problem – that the browse tab is over-cluttered with content and not clear.
As shown, the majority of the content within the app is grouped under the “Browse” Tab. This was a result of new features getting added into this bucket with little regard of where they make sense within the app experience.
I conducted 6 user interviews with users across the world, in the US, Mexico, and Barbados. The focus of these interviews was to determine how the understand how to best structure the app hierarchy to suit user needs.
Assumptions ↓
Takeaways ↓
The improved flow showcases a more organized app structure, with beats and browse being completely separated and challenges having their own home within browse.
This directly improves the discoverability of beats, allowing Rapchat to provide users with a personalized experience of beat suggestions.
Aside from just changing the structure and navigation within the app, there were various visual inconsistencies that needed to be addressed.
Beats being removed from the browse tab allows for proper organization and discoverability.
Key points:
Challenges are a huge part of the in-app experience that was lacking from an organizational standpoint.
Key points:
Beats being removed from the browse tab allows for proper organization and discoverability.
Key points:
One of Rapchat’s most engaged with features was truly lacking in experience.
Key points:
This project was completed and is currently in the handoff stages, I am actively communicating with developers and stakeholders throughout the process. We had parts of the app built and shipped to beta testing in waves.
First, changing the navigation, then updating the UI. We chose to break up the design into two builds to reduce the load for users and our dev teams.
Reflecting on the project I would have focused more effort onto the Producer experience as well as directly reviewing user feedback once this build was shipped.