ITMO/EVENTS
We developed a scalable interface covering the entire event experience — from announcement and registration to venue access and post-event analytics. The solution is based on intuitive navigation, a structured presentation of events, and minimizing user interactions during registration and attendance.
About the project
ITMO.EVENTS is the university’s one-stop portal for events. The platform brings together announcements, event pages, and registration forms for students, staff, and some external participants all in one interface.
On the surface, the product looks like a full-fledged event platform rather than a collection of separate landing pages: the homepage features promotional events, a “Trending Now” section, a general catalog, calendar navigation, thematic tags, and a section for past events. This helps users avoid having to search for an event among dozens of social media groups, allowing them to navigate through a clear workflow within a single service.
ITMO.EVENTS
Problem
Before the platform was launched, event registration was handled through forms. Events were scattered across different systems, there was no centralized catalog, and it was difficult to collect and analyze statistics on registrations and participants.
For users, this meant extra steps and a fragmented experience. For the university, it meant manual work, poor process control, and a lack of transparency regarding events.
Development
A unified registration process instead of a set of separate forms
Different events had different participation rules. For some, a simple registration was sufficient; for others, participants had to select a time slot; for others still, they had to choose a seat in the hall; and for external guests, passport information was required, followed by further processing through the access control system.
If you create a separate form for every scenario, the product quickly becomes a collection of exceptions. This is difficult to maintain and hard to scale.
That is why I designed and implemented a unified front-end registration logic with extensions for various participation scenarios.
Base-case scenario:
- The user opens the event page
- Log in via itmo.id
- Completes registration
- Receives a ticket with a QR code via email
Scenario extensions:
- Selecting a time slot
- Selecting a seat using a custom seating plan
- Registration for external visitors
- Registering a child
- QR code for external visitors as a temporary pass
Registration by time slot
Why was this important?
The first release had to be released in 1 month, so one-time solutions for each case would quickly create technical debt. At the same time, the platform itself already suggests scale from the outside: different types of events coexist in one interface - from open days and lectures to sporting events and internal activities. The home page supports this scenario through the catalog, calendar, tags, and collections. In other words, the product initially required not just one registration form, but a scalable recording model.
Main page
The main one solved the discovery problem: to help the user quickly find a suitable event and not get lost in the stream of announcements.
On the public version of the platform this is visible at several entry points:
- promotional block with events
- «Popular Now»
- calendar navigation with datepicker
- general directory
- thematic tags
- archive of past events
Main page
This approach lowers the entry barrier: the user can search for an event not only by name, but also by date, topic and format.
Event page
The event page was not just a content screen for me, but a decision point.
На ней пользователь должен быстро понять:
- what is this event
- when and where it takes place
- who is the organizer
- are there any restrictions
- is it worth registering right now
Event page
This is where interest turns into action: the event page should not just inform, but lead to registration.
Registration form for events with selection
Result
The platform has reduced the manual work of organizers and improved the conversion to recording.
The following were implemented:
- registration by time slots
- registration with seat selection according to a custom scheme
- registration of external guests
- registration of children (minors)
- QR for external guests as a temporary pass
The most illustrative example is Night skiing from ITMO.STUDENTS: 400 registrations through forms in 2022 → 2800 registrations through the platform in 2023
What does this case show?
This project addressed the following issues:
- designing product scenarios
- making technical decisions in a short timeframe
- building scalable logic, not one-time screens
- connecting UX, business logic, and integration constraints
For me, ITMO.EVENTS was a project about systemic design. We needed to build not just a showcase of events, but a platform that would cover the entire user journey: from event selection to registration, QR code tickets, and eventual admission to the venue.
[ Contacts ]
Get in touch