Kitchen Dash arranges six ingredient stations in a row along the bottom of the screen. That arrangement produces two genuinely different games depending on how you play it, and knowing which one you are in is worth several seconds per ticket.
Two input models, two optimal strategies
With a keyboard, you move a selection cursor left and right and fire it. Distance matters: moving from the leftmost station to the rightmost takes five presses.
With touch or a mouse, tapping a station selects and fires it in one action. Distance is irrelevant — every station is equally far away, which is to say not far at all.
That difference produces opposite optimal strategies, which is unusual and worth knowing:
| Consideration | Keyboard | Touch |
|---|---|---|
| Station distance | Matters a great deal | Irrelevant |
| Where to rest the cursor | Near the centre | N/A |
| Ticket order preference | Adjacent ingredients are faster | No preference |
| Speed ceiling | Limited by travel | Limited by reading the ticket |
Keyboard: park in the middle
With six stations, parking the selection on station 3 or 4 means no station is more than three presses away. Parking on station 1 means the far end is five presses away.
Over a six-ingredient ticket, that difference can be a full second — which at about 12 points per remaining second is 12 points of time bonus, multiplied. Small individually, meaningful across a run.
The related habit is to return toward the centre after using an end station rather than leaving the cursor where it was.
Touch: the speed ceiling is reading
With direct tapping, the constraint stops being travel and becomes how fast you can read the ticket.
This is why the current-step ring matters so much. A player under pressure does not parse the whole sequence — they look for the one highlighted icon and tap the matching station. That is roughly two saccades and one tap, and it is close to the practical floor for a deliberate action.
Conveyor Kitchen pushes this further with a dedicated GRAB NEXT panel showing only the required ingredient, large and isolated, because on a fast belt even a six-icon sequence is too much to parse.
Why six stations
Three constraints converge on six.
- Touch target size. Six buttons fit across a phone screen at comfortably above the 44-pixel minimum. Eight would be tight; ten would be unusable.
- Scannability. Six items in a row can be scanned without moving your eyes far, so locating a station is a single glance rather than a search.
- Keyboard travel. With six, the maximum distance from a centre-parked cursor is three presses. With ten it would be five, which starts to dominate the play.
A belt layout escapes all three constraints, which is why Conveyor Kitchen can use eight ingredients: there is no travel, no fixed target row to scan, and no button grid to fit.
Ordering within a ticket
Ticket sequences are generated randomly from the ingredient pool, which means a ticket can ask for stations 1, 6, 2, 5 — a maximally awkward path for a keyboard player and no different at all for a touch player.
That asymmetry is acceptable because both input methods have roughly comparable ceilings overall: touch is faster at travel and slower at nothing, but keyboard players tend to read ahead better because they are not moving a hand across the screen.
It does mean, though, that a keyboard player benefits from glancing at the whole sequence before starting — planning a path through the stations — where a touch player benefits more from watching only the highlighted step.
Visual feedback on a station
Each station shows four states, and all four are necessary:
- Idle — a translucent white panel with the ingredient glyph and label.
- Selected — an amber fill and a thicker amber border.
- Firing — a brief white flash lasting 250 milliseconds.
- Label — the ingredient name in small text under the glyph, for players who do not recognise a glyph immediately.
The flash is the one most often omitted and most missed. Without it, a player who taps a station and gets no immediate visual confirmation cannot tell whether their input registered, which leads to double-tapping — which in a game where a wrong ingredient costs two seconds is expensive.
Try it yourself: Kitchen Dash
Read the ticket, hit the stations in order and serve before the timer empties.
Key takeaways
- Keyboard play makes station distance matter; touch play makes it irrelevant, producing two different optimal strategies.
- On keyboard, park the cursor near the centre so no station is more than three presses away.
- On touch, the speed ceiling is how fast you read the ticket — which is why the current-step ring matters so much.
- Six stations is the convergence of touch target size, scannability and keyboard travel distance.
- Belt layouts escape all three constraints, which is why they can carry eight ingredients.
- Every station needs a firing flash, or players double-tap and pay the wrong-ingredient penalty.
Frequently Asked Questions
Where should I park the selection cursor on a keyboard?
Near the centre — station 3 or 4 of six — so no station is more than three presses away. Parking at an end leaves the far station five presses distant.
Is tapping faster than using the keyboard?
For travel, yes — tapping selects and fires in one action regardless of distance. Keyboard players tend to read ahead better, so overall ceilings are comparable.
Why only six stations?
Three constraints converge there: six touch targets fit across a phone at comfortable size, six items can be scanned in one glance, and six keeps maximum keyboard travel to three presses.
Why does Conveyor Kitchen have eight ingredients?
Because a belt has no travel cost, no fixed row to scan and no button grid to fit. The extra ingredients add reading difficulty only, which is cheaper than adding navigation.
Why does a station flash when used?
So you know your input registered. Without immediate confirmation players double-tap, and in a game where a wrong ingredient costs two seconds that is expensive.