Portrait of Yurii Korolev
Yurii Korolev Frontend developer
/
Hero illustration for the project «ITMO/EVENTS»

ITMO/EVENTS

Company / ClientITMO University
SphereEvent Tech, B2C / B2G
Project timelineSeptember 2023 – May 2024
My roleFrontend Developer

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:

Scenario extensions:

Registration by time slot

[ Contacts ]

Get in touch