Tomas Novak

Tomas Novak designs interfaces that feel right.

I am a product designer in Prague who prototypes in the browser. For six years I have worked on booking, payments and audio apps, where a single transition can decide whether people trust what they see.

Everything below runs on your input. Drag a seam, step a state, open a row. No video, no script.

Sheet entry, five frames

Step through the keyframes

Three things I made, with the interaction attached

Each project below comes with the piece of interaction that mattered most, rebuilt so you can try it. The notes say why it moves the way it does and what the engineers took away.

Moravka Rail: Booking a regular trip in three taps

Before and after, draggable2022

Most people buying tickets in the Moravka Rail app took the same trip every week, yet the booking form asked for route, date, passengers and seats every single time. I redesigned the start screen around the trip people were most likely to take next, with every detail still one tap away if they needed to change it.

Interaction design, prototype, motion spec

After

Prague to Brno, tomorrow

Same seats as last time, 2 passengers

Book these seats

Change anything above by tapping it

Before

Book a ticket

RouteDate of travelPassengersSeat preferenceBoarding point
Continue

Step 1 of 4

Drag the grip at the bottom right of the left panel

What the drag shows

The old five field form on the left, the new prefilled trip card on the right. Same data, one decision instead of five.

Why it moved

Tapping any line on the card expands it in place rather than opening a new screen, so people never lose sight of the trip they are about to book. The expand runs at 220 ms with a short settle.

What engineering got

A working prototype in the browser, a one page motion spec and a list of the five fields with the rules for prefilling each one.

Taps per booking went from 9 to 3. Drop off at checkout fell from 31% to 14%.

Tilia Payments: Payment status people can believe

State stepper2024

Small business owners using Tilia Payments kept calling support to ask whether a supplier had been paid. The app showed a spinner and then a tick, with nothing in between. I mapped every state a payment can be in and gave each one a clear line of copy, a progress meter and a color that never jumps backward.

Interaction design, state copy, design engineering

Sedlak Building Supply

Invoice 3057

QueuedSent to bankRetryingSettled

Sends at 5 pm with the day's batch.

The bank has it. Most payments like this clear in under a minute.

The bank is slow this evening. We are still trying and you do not need to do anything.

Received by Sedlak Building Supply. Reference TP 2916 35.

Step the row

What the stepper shows

One payment moving from queued to settled, including the slow evening retry that used to look like a failure.

The rule

The meter only ever moves forward. A retry holds its position and changes color, so a delay never looks like money going back.

What engineering got

A state chart with every transition, the copy for each state and a component built in React that the team shipped almost unchanged.

Status tickets fell by 27% in the first quarter after release.

Kolo Audio: Finding your place in a long episode

Spring disclosure2021

Kolo Audio's listeners skipped around two hour interviews with a scrubber that was hard to hit with a thumb. I designed a chapter list that opens with a light spring under the player, plus a scrubber with a larger handle and a preview of the chapter name while you drag.

Interaction design, prototype

onScrubStartFires once when a finger lands on the handle

Pauses playback, enlarges the handle and shows the chapter preview after 150 ms. A tap that lifts before then seeks straight to that point.

onScrubMoveThrottled to one frame

Updates the time label and chapter preview on every frame. Audio stays paused so listeners do not hear a stutter of clipped words.

onScrubEndFires on release or cancel

Seeks to the new position and resumes playback. On cancel, the handle springs back to where it started and nothing changes.

Open a row

What the rows show

The three scrubber events I specified for engineering, each one opening to explain exactly when it fires and what it changes.

The number that mattered

The handle grew to a 44 px touch target and the chapter preview appears after 150 ms of dragging, early enough to guide the thumb without flickering on every tap.

What engineering got

An event spec, spring values for the chapter list and a test page they used to tune the timing on real phones.

Time to find a chapter in usability tests dropped from 52 seconds to 27.

How I work

I start by writing down every state a screen can be in, including the boring ones: loading, empty, slow, wrong and offline. Most interface problems I am asked to fix turn out to live in a state nobody drew.

Then I prototype in the browser, usually in React, with real data where I can get it. A prototype that runs on a phone in someone's hand settles more arguments in ten minutes than a week of static mockups.

When the behavior is right, I write it up on one page: the states, the timing, the copy and the edge cases. Engineers get something they can build from, and testers get something they can check against.

What I can hand a team

State charts that engineers keep open
Every state and transition on one diagram, with the copy for each state written next to it.
Prototypes in browser code
Working React prototypes that run on real phones and can be tested with real people.
Motion specs on one page
Durations, easing and spring values in a single table, matched to the prototype.
Interface copy under pressure
Clear words for errors, delays and retries, the moments when people are most anxious.
Accessibility in the interaction
Focus order, touch targets and reduced motion settings planned from the first prototype.
Design systems for behavior
Shared rules for how components open, close and fail, not just how they look.

Experience

  1. Tilia Payments, Prague

    2023 to now

    Lead product designer

    Lead designer for payments and invoicing in the business app, working with two product teams and a design system group of three.

  2. Moravka Rail, Brno

    2021 to 2023

    Interaction designer

    Redesigned ticket booking and live journey updates in the passenger app, used by around 400,000 riders a month.

  3. Independent, Prague

    2020 to 2021

    Prototyper, contract

    Built interactive prototypes for startups and agencies, including the chapter player for Kolo Audio.

  4. Vltava School of Design, Prague

    2017 to 2020

    BA in interaction design

Say hello

If you have an interaction that needs to feel right before it ships, send me a short note about the product and the moment that is giving you trouble.

tomas@example.com

Taking one new project from February 2027

The PrototyperBuild this oneAll templates
Tomas Novak, The Prototyper demo | Syforia