EVENTRITE - WEBAPP
EVENTRITE - WEBAPP
EVENTRITE - WEBAPP
PRODUCT NAME
PRODUCT NAME
eventrite
eventrite
eventrite
PROJECT MODE
PROJECT MODE
Personal Project
Personal Project
Personal Project
PLATFORM
PLATFORM
Mobile App
Mobile App
Mobile App
TARGET AUDIENCE
TARGET AUDIENCE
Event Organizers
Event Organizers
Event Organizers
ROLE
ROLE
Product Designer
Product Designer
Product Designer
TIMELINE
TIMELINE
3 Weeks
3 Weeks
3 Weeks
Rethinking event platforms as growth systems
Overview
A few days after hosting a successful event, there’s usually a moment that doesn’t get talked about enough. The room was full. People showed up. Tickets sold. Conversations happened. From the outside, everything worked.
But then… it ends. No follow-up. No easy way to reconnect with attendees. No clear path to turn that momentum into something lasting. Just a list of emails—somewhere—and the quiet pressure of having to start all over again for the next event.
That moment is what this project is really about. Because if I’m an event organizer, that “after” moment matters just as much as the event itself. It’s where I either lose everything I’ve built—or figure out how to build on it. The more I thought about it, the more I realised that most event platforms aren’t designed for that moment. They’re designed to help you get through the event, not grow beyond it.
So I approached this product from a different angle. Instead of asking how I could help organizers run better events, I focused on how I could help them carry the value of one event into the next—without losing momentum, without switching tools, and without starting from zero every time.
My goal was to design a unified event management system that enables organizers to efficiently create and manage events, control ticket sales and pricing, run communication and marketing campaigns, and track performance through clear, actionable insights — all in one place, so they can operate events more effectively and grow them over time.
eventrite is a mobile-first ticketing platform that enables users to discover events, purchase secure digital tickets, and manage them seamlessly within a single ecosystem.
A few days after hosting a successful event, there’s usually a moment that doesn’t get talked about enough. The room was full. People showed up. Tickets sold. Conversations happened. From the outside, everything worked.
But then… it ends. No follow-up. No easy way to reconnect with attendees. No clear path to turn that momentum into something lasting. Just a list of emails—somewhere—and the quiet pressure of having to start all over again for the next event.
That moment is what this project is really about. Because if I’m an event organizer, that “after” moment matters just as much as the event itself. It’s where I either lose everything I’ve built—or figure out how to build on it. The more I thought about it, the more I realised that most event platforms aren’t designed for that moment. They’re designed to help you get through the event, not grow beyond it.
So I approached this product from a different angle. Instead of asking how I could help organizers run better events, I focused on how I could help them carry the value of one event into the next—without losing momentum, without switching tools, and without starting from zero every time.
My goal was to design a unified event management system that enables organizers to efficiently create and manage events, control ticket sales and pricing, run communication and marketing campaigns, and track performance through clear, actionable insights — all in one place, so they can operate events more effectively and grow them over time.
I designed eventrite webapp as an event creation and management platform for organizers to plan, launch, and actively manage events in real-time. From ticketing and attendee engagement to on-ground operations and post-event insights.
I designed eventrite webapp as an event creation and management platform for organizers to plan, launch, and actively manage events in real-time. From ticketing and attendee engagement to on-ground operations and post-event insights.
Problem Statement
After establishing what Eventrite is, I needed to clearly define the problem I was solving — not at a surface level, but from the reality organizers face.
After establishing what Eventrite is, I needed to clearly define the problem I was solving — not at a surface level, but from the reality organizers face.
At first glance, the problem seems straightforward: organizers need a way to create and manage events. But as I looked deeper, I realized that wasn’t the real issue. Most existing platforms already make it possible to create events, sell tickets and view basic anlytics. Yet despite having these tools, organizers still struggle to consistently run successful events.
At first glance, the problem seems straightforward: organizers need a way to create and manage events. But as I looked deeper, I realized that wasn’t the real issue. Most existing platforms already make it possible to create events, sell tickets and view basic anlytics. Yet despite having these tools, organizers still struggle to consistently run successful events.
Organizers lack the ability to actively manage and influence the success of their events in real-time, due to rigid tools, passive analytics, and limited operational control.
Organizers lack the ability to actively manage and influence the success of their events in real-time, due to rigid tools, passive analytics, and limited operational control.
MY ROLE
On this project, I worked as the Product Designer, but my responsibilities extended beyond designing interfaces. I was responsible for shaping the product direction, defining its core value, and ensuring that every part of the experience connects back to that value.
I approached this as both a designer and a product thinker. I wasn’t just asking, “What should this screen look like?” but also, “Why does this feature exist, and how does it help the user move forward?” My goal was to design something cohesive, not just functional.
On this project, I worked as the Product Designer, but my responsibilities extended beyond designing interfaces. I was responsible for shaping the product direction, defining its core value, and ensuring that every part of the experience connects back to that value.
I approached this as both a designer and a product thinker. I wasn’t just asking, “What should this screen look like?” but also, “Why does this feature exist, and how does it help the user move forward?” My goal was to design something cohesive, not just functional.
MY APPROACH
One of the most important decisions I made early on was to stop thinking about the product as a collection of features. Instead, I started thinking about it as a continuous journey.
I mapped out the lifecycle of an event organizer’s experience, from the moment they decide to create an event to what happens after that event is over. What stood out to me was that most tools focus heavily on the beginning of that journey, but almost completely ignore what happens afterwards.
So I designed around a simple but powerful loop: An organizer creates an event, attendees sign up, those attendees become part of an audience, and that audience becomes the foundation for future engagement. Everything I designed had to support that loop in a way that felt natural and seamless.
This approach helped me avoid designing disconnected features and instead focus on how each part of the experience leads into the next.
One of the most important decisions I made early on was to stop thinking about the product as a collection of features. Instead, I started thinking about it as a continuous journey.
I mapped out the lifecycle of an event organizer’s experience, from the moment they decide to create an event to what happens after that event is over. What stood out to me was that most tools focus heavily on the beginning of that journey, but almost completely ignore what happens afterwards.
So I designed around a simple but powerful loop: An organizer creates an event, attendees sign up, those attendees become part of an audience, and that audience becomes the foundation for future engagement. Everything I designed had to support that loop in a way that felt natural and seamless.
This approach helped me avoid designing disconnected features and instead focus on how each part of the experience leads into the next.
“How might I design a ticketing experience that users can trust from discovery to event entry?”
“How might I design a ticketing experience that users can trust from discovery to event entry?”
User Stories: Grounding every decision in real needs
User Stories: Grounding every decision in real needs
To make sure I stayed aligned with real user needs, I kept returning to a set of user stories that reflected how organizers actually think and behave. I thought about the organizer who wants to get their event live quickly without being slowed down by complexity, and how important it is for that process to feel simple and guided rather than overwhelming.
I thought about the organizer who just wants to get their event live without friction, and how important it is for that process to feel quick and guided rather than overwhelming. I also considered the need for automatic data capture, where every ticket purchase becomes more than just a transaction—it becomes a valuable contact that the organizer can use later.
To make sure I stayed aligned with real user needs, I kept returning to a set of user stories that reflected how organizers actually think and behave. I thought about the organizer who wants to get their event live quickly without being slowed down by complexity, and how important it is for that process to feel simple and guided rather than overwhelming.
I thought about the organizer who just wants to get their event live without friction, and how important it is for that process to feel quick and guided rather than overwhelming. I also considered the need for automatic data capture, where every ticket purchase becomes more than just a transaction—it becomes a valuable contact that the organizer can use later.
As an event organizer, I want to create and publish an event quickly so that I can go from idea to live event without unnecessary friction or technical complexity.
As an event organizer, I want to create and publish an event quickly so that I can go from idea to live event without unnecessary friction or technical complexity.
As an event organizer, I want to set up different ticket types and pricing options so that I can cater to different audience segments and maximise revenue opportunities.
As an event organizer, I want to set up different ticket types and pricing options so that I can cater to different audience segments and maximise revenue opportunities.
Communication also played a big role in shaping the experience. I imagined how important it is to send reminders, follow-ups, or promotions without needing to set up complex campaigns.
Communication also played a big role in shaping the experience. I imagined how important it is to send reminders, follow-ups, or promotions without needing to set up complex campaigns.
As an event organizer, I want to send emails or updates directly to my attendees so that I can keep them informed, engaged, and connected before and after the event.
As an event organizer, I want to send emails or updates directly to my attendees so that I can keep them informed, engaged, and connected before and after the event.
And finally, I thought about growth. If I’ve already gathered an audience once, I shouldn’t have to start from zero again.
And finally, I thought about growth. If I’ve already gathered an audience once, I shouldn’t have to start from zero again.
Challenges: Designing a powerful system without overwhelming the user
As the product started to take shape, one of the biggest challenges I faced was managing complexity. This wasn’t a simple tool. It combined multiple functionalities—event creation, ticketing, attendee management, communication, and analytics—into one platform.
The risk here was obvious. If not handled carefully, the product could easily become overwhelming. I had to be intentional about how information is introduced and how users move through the experience. Instead of exposing everything at once, I focused on guiding users step by step, making sure each action feels manageable.
Another challenge was behavioural. Even though organizers understand the value of audience retention, their workflows don’t always reflect that. So I couldn’t rely on them to actively seek out these features. I had to design the experience in a way that naturally encourages these behaviours.
As the product started to take shape, one of the biggest challenges I faced was managing complexity. This wasn’t a simple tool. It combined multiple functionalities—event creation, ticketing, attendee management, communication, and analytics—into one platform.
The risk here was obvious. If not handled carefully, the product could easily become overwhelming. I had to be intentional about how information is introduced and how users move through the experience. Instead of exposing everything at once, I focused on guiding users step by step, making sure each action feels manageable.
Another challenge was behavioural. Even though organizers understand the value of audience retention, their workflows don’t always reflect that. So I couldn’t rely on them to actively seek out these features. I had to design the experience in a way that naturally encourages these behaviours.
SOLUTIONS (UI DESIGNS)
To solve these challenges, I focused on designing flows that feel connected and purposeful.
I started with event creation, making it as frictionless as possible. From there, I treated ticket purchases as more than just transactions. Every purchase automatically feeds into an attendee database, ensuring that organizers are constantly building an audience without extra effort. I designed the attendee management to feel dynamic and useful.
Finally, I designed analytics and insights to provide clarity for the organizers for easier and better decision making.
To solve these challenges, I focused on designing flows that feel connected and purposeful.
I started with event creation, making it as frictionless as possible. From there, I treated ticket purchases as more than just transactions. Every purchase automatically feeds into an attendee database, ensuring that organizers are constantly building an audience without extra effort. I designed the attendee management to feel dynamic and useful.
Finally, I designed analytics and insights to provide clarity for the organizers for easier and better decision making.
A guided event creation experience
The first place I focused on was the entry point—creating an event. From my research, it was clear that organizers want to move quickly from idea to execution. The moment someone decides to host an event, any friction at that stage can slow them down or even discourage them.
The first place I focused on was the entry point—creating an event. From my research, it was clear that organizers want to move quickly from idea to execution. The moment someone decides to host an event, any friction at that stage can slow them down or even discourage them.
Turning every ticket purchase into audience growth
One of the most important shifts I made was redefining what a ticket purchase represents. In most platforms, it’s treated as the end of a transaction. But in this product, I designed it as the beginning of a relationship. Every time someone purchases a ticket, their information is automatically captured and stored in a structured attendee database. This happens seamlessly in the background, without requiring any extra action from the organizer.
One of the most important shifts I made was redefining what a ticket purchase represents. In most platforms, it’s treated as the end of a transaction. But in this product, I designed it as the beginning of a relationship. Every time someone purchases a ticket, their information is automatically captured and stored in a structured attendee database. This happens seamlessly in the background, without requiring any extra action from the organizer.
Attendee management system
Once attendee data is captured, the next challenge is making it useful. Instead of designing a basic attendee list, I approached this as a lightweight relationship management system. I wanted organizers to feel like they’re not just viewing names, but actually understanding their audience.
So I designed the attendee view to allow filtering, segmentation, and visibility across events. Organizers can group attendees based on ticket types or engagement patterns, making it easier to take targeted actions later.
Once attendee data is captured, the next challenge is making it useful. Instead of designing a basic attendee list, I approached this as a lightweight relationship management system. I wanted organizers to feel like they’re not just viewing names, but actually understanding their audience.
So I designed the attendee view to allow filtering, segmentation, and visibility across events. Organizers can group attendees based on ticket types or engagement patterns, making it easier to take targeted actions later.
Performance tracking & insights
Finally, I focused on the dashboard and analytics. I didn’t want to overwhelm users with data. I wanted to give them clarity. So I prioritised showing revenue, tickets sold, and sales trends. Rather than presenting complex dashboards filled with excessive data, I prioritised the metrics that actually matter—revenue, tickets sold, and sales trends over time.
The goal was to help organizers quickly answer simple but important questions:
Is this event performing well?
What’s working?
What should I do differently next time? By keeping the analytics focused and easy to interpret, I ensured that the product supports decision-making instead of complicating it.
Finally, I focused on the dashboard and analytics. I didn’t want to overwhelm users with data. I wanted to give them clarity. So I prioritised showing revenue, tickets sold, and sales trends. Rather than presenting complex dashboards filled with excessive data, I prioritised the metrics that actually matter—revenue, tickets sold, and sales trends over time.
The goal was to help organizers quickly answer simple but important questions:
Is this event performing well?
What’s working?
What should I do differently next time? By keeping the analytics focused and easy to interpret, I ensured that the product supports decision-making instead of complicating it.
By keeping the analytics focused and easy to interpret, I ensured that the product supports decision-making instead of complicating it.
By keeping the analytics focused and easy to interpret, I ensured that the product supports decision-making instead of complicating it.
Results & Impacts
By connecting these flows into a single system, the product shifts from being a tool for managing events to a system for building growth. Organizers can now move seamlessly from creating an event to capturing attendee data, and from there to engaging that audience again. This reduces reliance on multiple tools and simplifies their workflow.
More importantly, it changes how they think about their work. Instead of viewing each event as a standalone effort, they begin to see it as part of a larger journey. Each event contributes to a growing audience, making future events easier to promote and more successful.
That shift from isolated execution to continuous growth, is where the real impact lies.
By connecting these flows into a single system, the product shifts from being a tool for managing events to a system for building growth. Organizers can now move seamlessly from creating an event to capturing attendee data, and from there to engaging that audience again. This reduces reliance on multiple tools and simplifies their workflow.
More importantly, it changes how they think about their work. Instead of viewing each event as a standalone effort, they begin to see it as part of a larger journey. Each event contributes to a growing audience, making future events easier to promote and more successful.
That shift from isolated execution to continuous growth, is where the real impact lies.
Conclusion
Looking back, what made this project meaningful to me was the shift in perspective. By focusing on continuity instead of just functionality, I was able to design a product that feels more complete and more valuable.
It’s not just about helping organizers run events. It’s about helping them hold onto the value they create and build on it over time. And that’s what good product design should do it should extend value beyond the immediate interaction.
Looking back, what made this project meaningful to me was the shift in perspective. By focusing on continuity instead of just functionality, I was able to design a product that feels more complete and more valuable.
It’s not just about helping organizers run events. It’s about helping them hold onto the value they create and build on it over time. And that’s what good product design should do it should extend value beyond the immediate interaction.
While it wasn’t built for a live product, the process helped me grow as a designer and reinforced the value of user-centered thinking.
While it wasn’t built for a live product, the process helped me grow as a designer and reinforced the value of user-centered thinking.
Next Steps
If I were to continue working on this product, I would focus on deepening the idea of audience growth.
I would explore ways to make audience segmentation more intelligent, allowing organizers to better understand patterns in attendee behaviour. I would also look into introducing automated communication flows, especially for post-event engagement, to reduce manual effort while increasing consistency.
On the analytics side, I would expand the insights to include engagement and retention metrics, helping organizers understand not just what happened, but why it happened.
But more importantly, I would continue refining how the product communicates its value, making it even clearer that this isn’t just an event tool.
It’s a system for building something that grows with every interaction.
If I were to continue working on this product, I would focus on deepening the idea of audience growth.
I would explore ways to make audience segmentation more intelligent, allowing organizers to better understand patterns in attendee behaviour. I would also look into introducing automated communication flows, especially for post-event engagement, to reduce manual effort while increasing consistency.
On the analytics side, I would expand the insights to include engagement and retention metrics, helping organizers understand not just what happened, but why it happened.
But more importantly, I would continue refining how the product communicates its value, making it even clearer that this isn’t just an event tool.
It’s a system for building something that grows with every interaction.
2025
Mobile App
Ridely
Mobile-first delivery experience for riders handling logistics.
2026
Mobile App
In Progress
Recruitly
Mobile-first AI-powered gamified experience job applicants.
2023
Mobile App
Eventrite
Mobile-first ticketing platform that enables users to discover events, purchase secure digital tickets.
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts