B2C users seek simplicity, visual appeal, and mobile-first access;

B2B users prioritize control, data depth, and desktop workflows.

Designing two interfaces required thorough understandings of each user group. Building on the co-founders’ preliminary market research, which identified 1) Moroccan club owners’ need for an accessible ticketing and revenue management platform, and 2) club-goers’ need for a simple way to purchase tickets, I conducted further competitor research for both groups to uncover user habits and guide my design decisions.

Reflecting Research Insights on Distinct User Needs in My Design

Challenge 2

Design For Development

Design Inconsistency Cause Development Delays;

Effective Communication Solves Mistakes

Through close collaboration with developers, I gained first-hand insight into how design can support development. In this instance, by actively listening to developer feedback, I learned the importance of maintaining consistent design across platforms (mobile and desktop) to ensure a smooth development process.

Challenge 3

Beyond Figma

Slightly Compromising Aesthetics for a Much Shorter Development Timeline

While developing the MVP, we faced a decision: implement my original payment page design or integrate an existing API to handle transactions. Here’s why we ultimately chose the API.

Establishing Email Design Standards for the Full User Experience

As multiple points in the consumer user flow required back-and-forth communication between the user and ViBeat, such as confirming a security code during registration or sending upcoming event reminders, I created a full set of email design templates to cover a range of use cases.

Checkout Vibeat at https://vibeat.io/, Thanks for Visiting