Sound bank management application and project call
WeCompoze is a platform dedicated to the creation and management of sonic identities. It enables brands to launch open calls to composers while also providing access to a library of sound assets that can be explored and licensed.
The challenge was to design an experience capable of supporting these two distinct use cases — custom sound creation and an existing sound library — within a clear, fluid, and coherent product for different types of users.
Client
WeCompoze
My role
UI Design
Categories
SaaS
Desktop
BtoB
BtoC
Project duration
4 month
Year
01
Understanding the product
To understand the product, I started by analyzing the ecosystem of the platform and the interactions between its different actors: the brands, the composers, and the internal team.
This step allowed me to identify two main uses:
I also studied the business model and the expectations of the users in order to clarify the product objectives and the constraints to be considered for the continuation of the design.
02
Mapping the user flows
To better understand how the platform works, I have mapped the user journeys distinguishing three main flows: the journey of companies, that of composers, and that of the WeCompoze team.
This modeling allowed me to clarify the role of each actor in the process of creating a sound identity, from defining the brief to selecting the composer.
The visualization of these three journeys also highlighted several frictions in the existing interface, particularly in understanding the project stages, tracking participation, and the flow of information between the different actors.
These flows then served as a basis to structure the platform architecture and guide design decisions.
03
Structuring the platform
Based on the identified user journeys, I initially structured the back-office architecture to clearly organize the different functionalities of the platform.
The interface was designed around three main pillars: project and sound catalog management, sales-related functionalities, and the general settings of the platform.
This organization allows grouping actions by business logic, while simplifying navigation for administrator users.
The definition of this hierarchy served as a basis for designing the screens and ensuring the overall coherence of the interface.
Backoffice
PROJECTS AND CATALOGS
Dashboard
Projects
Albums
Signatures
SALE
Products
Orders
Private label
GENERAL SETTINGS
Users
Roles and permissions
Import / Export
Terms and Conditions / Contracts
04
Design the experience
Based on the architecture defined earlier, I designed the main screens of the platform, ensuring a clear and consistent experience for different users.
The work focused on managing project calls, exploring the sound library, and administering the catalog from the back office.
The goal was to simplify the consultation of content, the management of participations, and administrative actions, while ensuring a readable and structured interface.
This design phase allowed for transforming the product architecture into a smooth and usable user experience on a daily basis.
Name | Dark | Light |
|---|---|---|
Also, thanks to the use of Figma variables, I was able to integrate into the high-fidelity prototype the switch between light mode and dark mode.
