MomenticketA booking path that wasn’t converting.

Make the first field answer back.

A suggestion list does appear — it is simply ranked alphabetically. On the Kyiv–Warsaw route, typing “вар” returns Варакути, Вараш, Варва, Варваринці and Варварівка — five villages, with Warsaw below the fold. autocomplete="off" on the same field then suppresses the browser’s own saved entries, so a returning traveller gets no help either.

So the field had to answer back. Autocomplete now groups results and leads with popular destinations and the traveller’s own recent searches, so the common case is a tap rather than a spelling test. The date picker handles one-way and return in the same control. On mobile every field opens full-screen — the keyboard no longer fights the form for space.

Everything the system knew, all at once.

The old card published every fact the system held: three payment badges, a cumulative discount line, amenity icons, the carrier, the full station address at both ends. Filters took a third of the screen. Nothing was ranked, so nothing stood out — and comparing two departures meant reading two dense blocks line by line.

The rebuilt card carries only what decides a trip: times, duration, transfers, price. Everything else moved behind an expand, one tap away and complete when you want it. Transfers became explicit rather than a footnote — direct, guaranteed connection, change of station, self-transfer each read differently at a glance, because that difference is what a traveller is actually buying.

Where a ready buyer was still lost.

Checkout happened inside the route card. The card rebuilt itself as you filled it in, buttons moved out from under you, and there was no indication of how many steps remained. Registration was mandatory and arrived as a surprise at the end, in a modal with no close button and no way back.

Booking is now three declared steps — details, payment, confirmation — with the stepper visible throughout and the price held in view. Registration became optional: you buy as a guest and are offered an account afterwards, which is what both Omio and Tickets.ua already do. Every ending resolves to a next action, including the ones nobody designs for: verification pending, payment failed, paid on the bus.

A page per route, answering the route’s questions.

A separate, smaller piece of work: a landing page built from scratch for a single origin–destination pair — Kyiv–Kharkiv, Kharkiv–Lviv, Kyiv–Warsaw and so on — in both desktop and mobile layouts.

Someone who arrives here has already named their route, so the page answers for that route before the form is touched: the lowest cached price with its date, prices on the neighbouring dates, and the route in numbers — from-price, how many buses run it, the fastest time. Three departures are picked out and bookable — cheapest, fastest, and the balance between them — so a decided traveller never has to run a search at all. The search form is there, pre-filled with the route, for everyone else.

The rest of the page exists for the answer being no: related routes out of both cities, the advice that shifts a trip by a day or an hour, and a request form when nothing on the page fits.