E-Ticket

E-Ticket is a single electronic ticket for public transport in the Kharkiv city.

Client

Kharkiv Government

Kharkiv Government

Industry

Public accessibility

Public accessibility

Client

Economy Bookings

Position

Product Designer

Product Designer

Work type

Mobile

Work type

Mobile

Mobile

What I did

As a Product Designer, I designed an iOS app consolidating fare payment across all public transport types in Kharkiv, running the project end-to-end from research through clickable prototype: surveying 30 residents, visitors, and benefit-eligible riders across three user segments, synthesizing findings into personas, a customer journey map, and a service blueprint, then prioritizing and prototyping the features that mattered most (in-app payment, card top-up, balance transfer, route and arrival visibility).

How I did it, and what I used:

  • Defined the problem before designing
    Kharkiv's public transport had fragmented, cash-heavy fare systems and no centralized route/schedule information, creating friction for daily commuters, benefit-eligible riders, and tourists alike (language and currency barriers on top of everything else).

  • Grounded the app in real user data
    Ran a 30-respondent survey via Google Forms, split across three groups (general citizens, citizens with transport benefits, tourists), to understand payment habits, preferred platforms, and pain points before designing anything.

  • Went deeper with qualitative research
    Followed up with user interviews to complement survey data, then organized all findings: survey, interviews, and observations into a mind map in Miro to group insights and surface the core problems worth solving.

  • Structured the problem with UX artifacts
    Built personas, a Customer Journey Map, and a Service Blueprint to map how different user types actually move through the city and where the current system breaks down.

  • Prioritized ruthlessly
    Turned raw feature ideas (smartphone payment, card linking, balance top-up, benefit-tier switching, route/arrival visibility, fund transfer between cards) into a ranked list before touching prototypes, so effort went to what users actually asked for.

  • Validated with hypotheses, not assumptions
    Framed testable if/then hypotheses tied to adoption and satisfaction, then built a Lo-Fi prototype to test them before investing in high-fidelity screens.

  • Shipped a clickable prototype
    Final designs were built and prototyped in Figma, collaborating regularly with city transport authorities to keep the design aligned with real infrastructure constraints.