OmEvent
UX/UI design for a multi-role event platform with user accounts, organizer dashboards, and an admin panel
UX/UI
Product Design
Admin Panel
Dashboard
Design System
About the project
OmEvent was conceived as the first ticketing service focused on personal growth events, including yoga, retreats, meditation, and similar formats. The platform needed to support three roles:
- attendees discover events and buy tickets;
- organizers create events and manage sales;
- administrators moderate the platform.
Challenge
Build a platform where attendees can discover events and buy tickets, organizers can manage events, sales, and attendees, and administrators can oversee the service through clear moderation workflows and statuses.
The main design challenge was to make purchasing simple while giving organizers and the platform team a transparent view of events, sales, and payouts.
The main design challenge was to make purchasing simple while giving organizers and the platform team a transparent view of events, sales, and payouts.
Key outcomes
Designed the platform’s end-to-end UX/UI system:
Designed the public website: event catalog, event and organizer pages, and ticket checkout
Created a user account area for tickets, favorites, subscriptions, gifts, and referrals
Designed an organizer dashboard as a workspace for managing events, attendees, finances, and documents
Designed an admin panel with consistent tables, statuses, filters, and quick actions
Created a UI kit and the foundations of a design system to support scaling and development handoff
Post-launch figures
70+
registered users
40+
events created
30+
organizers joined
Approach
I started with roles and scenarios rather than individual screens: attendee, organizer, and administrator. I then mapped the information architecture and key user flows before moving on to interfaces and components.
Attendee
Finds events, explores details, buys tickets, saves favorites, follows organizers, earns rewards, and joins the referral program
Pain points:
- No single place to find these events: listings are scattered across channels, chats, and social media.
- Organizer reviews and reputation are often unclear.
- Rewards accumulate across different platforms without an obvious benefit.
Interface:
- Public website
- User account
Insight:
People choose not just an event, but an organizer they trust. I made organizers more visible through dedicated profiles, a follow feature, and their presence on event cards.
Organizer
Creates and edits events; manages tickets, pricing, promo codes, referral links, payouts, reviews, and co-organizers
Pain points:
- Sales, attendee lists, communication, and finances are often managed manually or across separate tools.
- It is difficult to quickly see ticket sales, registrations, and funds available for withdrawal.
- Organizers need to promote both individual events and their reputation on the platform.
Interface:
- Organizer dashboard
Insight:
Organizers have different levels of technical experience. The interface should be straightforward: clear tables, structured information, simple forms, and quick actions, with minimal decorative complexity.
Administrator
Moderates events, organizers, users, reviews, support requests, payouts, refunds, partner offers, promo codes, and referral relationships
Pain points:
- Too many record types—events, organizers, users, referrals—with no consistent management model.
- Finding the right item and making a decision takes too many steps.
- Data is scattered across different systems, increasing manual work and the risk of errors.
Interface:
- Admin panel
Insight:
The admin panel needs one consistent pattern for managing records. Content may differ by section, but the interaction model should stay the same.
Moderation and status changes should be immediately accessible, without extra steps.
Moderation and status changes should be immediately accessible, without extra steps.
Information architecture
Public website
Approach
The public website follows the core user journey: quickly find a relevant event, get enough information to make a decision, and buy a ticket.
Event catalog — the main entry point
Event page — supporting the decision
Ticket purchase — the key conversion flow
The goal is to guide users from ticket selection to payment without unnecessary doubts or backtracking.
Solution
I kept event details and selected tickets visible throughout checkout, so users could confirm their choices without going back.
I split checkout into three steps—ticket selection, attendee details, and payment—to simplify the flow and reduce cognitive load.
Organizer profile — building trust
User goal
Find a relevant event and buy a ticket easily
Outcome
The attendee receives a ticket and is ready for the event
Next step
Returns to the platform and takes part in the loyalty program
User account
Approach
OmEvent encourages repeat visits through rewards in the user account area. Loyalty points unlock partner gifts, while referral earnings in rubles can be spent on events or withdrawn to a bank card. I kept these balances separate so users could clearly understand the value and purpose of each.
Gifts and referrals — retention and growth
Users need to see the value of their activity: completing tasks earns points, unlocks levels, and gives access to rewards at special prices.
Referrals earn rubles, which can be used for tickets or withdrawn to a bank card.
Referrals earn rubles, which can be used for tickets or withdrawn to a bank card.
Solution
I separated points from rubles so that each reward had a clear purpose and value, rather than mixing them in a single balance.
I connected each program to specific actions. The loyalty program shows tasks and discounts; the referral program shows events users can invite friends to.
Gifts — loyalty program
Referrals — referral program
Organizer dashboard
Approach
The organizer dashboard streamlines everyday work: creating events and managing sales, attendees, finances, and documents. It follows the event lifecycle, from publication and ticket sales to attendee management and withdrawals. Information is organized into dedicated tabs, keeping processes under control without overwhelming the interface.
Home — an overview at a glance
Organizers need to quickly understand how their events are performing: available funds, ticket sales, and current events.
Events — the dashboard’s core workflow
The organizer’s main task is to create and manage events. They need a quick overview of events and their statuses, a way to monitor sales, and easy access to editing.
Solution
I divided Events into two core flows:
1) creating a new event; 2) managing existing events.
1) creating a new event; 2) managing existing events.
I used tables for event lists so organizers could quickly scan events and act without opening every individual page.
Managing existing events
Creating a new event
Attendees — managing the event audience
The attendee section supports a key operational workflow after a ticket is purchased. It is a tool for preparing for an event, rather than simply a list of users.
Supporting tools
Additional sections support feedback, legal documentation, and team management.
Balance
Legal entity details
Public organizer profile
Team management
Service acceptance documents
Admin panel
Approach
To keep the admin panel clear as the number of record types grows, I established one interaction model across sections: search, filter, review a table, and change a status. Administrators can find information, make decisions, and manage processes with fewer transitions.
Key consistency decisions
Table structure
Each section shows only the information administrators need to make a decision.
Status system
I made status changes in each section’s table the administrator’s primary action.
Search and filtering
I added search, filters, and sorting to tables across all sections for faster content management.
User administration
Organizer verification
Organizer promo codes
Visual system
Approach
The design system provides a foundation for scaling the platform. I aimed for one visual language across different interface types. Modular components can be reused across scenarios, speeding up interface assembly, maintaining consistency, and simplifying development handoff.
Graphic assets
variables & styles
Components
Reflection
Simplicity often matters more than visual complexity. The admin panel was initially planned with more features, but conversations with the founder and team showed they needed a simple, flexible tool for everyday work. This led to a consistent model across sections and a clearer workflow.
AI can accelerate the work, but it cannot replace a design foundation. The team chose AI tools to speed up development. Without designs, the results were unpredictable: the generated interface missed the product’s specific needs and workflows.
Once the designs were in place, implementation became more accurate and predictable.
Once the designs were in place, implementation became more accurate and predictable.
The end
