Skip to content

Technical · 6 August 2026

Touch latency, frame pacing and why a puzzle feels sluggish

Smoothness is not one number. A board can render quickly and still feel unresponsive, and the reason is usually the gap between your finger moving and anything happening on screen.

Ask someone why a puzzle game feels slow and they will say the frame rate is bad. Sometimes that is right. More often the frames are fine and the problem is elsewhere in the chain that runs from the glass under your thumb to the pixels under your eye.

What actually happens when you swap two sweets

The touch digitiser samples your finger at a fixed rate. The operating system batches those samples and hands them to the app. The app decides on the next frame whether that gesture counts as a swap. The frame is drawn, queued, and finally shown at the next display refresh. Every one of those steps adds a few milliseconds, and they add up to the number that matters: the delay between your intent and the game's response.

This is why a game locked to a steady thirty frames per second can feel crisper than one running at sixty with a long input queue. Consistency and responsiveness beat raw throughput for something you touch directly.

Frame pacing versus frame rate

Frame pacing is whether frames arrive evenly. Twenty frames arriving at regular intervals looks smoother than thirty arriving in clumps, because the eye notices the stutter, not the average. Cascade animations are exactly where this shows: pieces falling should describe a straight line down the screen, and when pacing is poor they visibly hitch on the way.

If you want to see it without any tools, watch a long cascade and look at a single falling sweet rather than the whole board. Hitching that is invisible in the chaos becomes obvious when you track one piece.

What you can change on your own phone

  • Close the background. Puzzle games are not demanding, but they compete for the same processor as everything else. A phone with fifteen apps resident and a sync running will pace frames worse.
  • Check the display refresh setting. Many Android phones ship in an adaptive mode that drops to a lower refresh rate on static screens. A puzzle board is mostly static, so the phone may be dropping down exactly when you start to move.
  • Turn off battery saver while playing. On both platforms it throttles the processor and caps the refresh rate, which is precisely the wrong trade for a game you touch constantly.
  • Take off the thick screen protector. A cheap, badly bonded protector genuinely does add touch latency and dead zones near the edges.
  • Let the game finish downloading. These titles stream level assets in the background on first run; playing during that is the worst it will ever feel.

What the developer controls and you do not

Animation length is the big one. If a clear takes eight hundred milliseconds to celebrate before accepting the next input, no phone setting will fix it. Some games offer a fast-animation toggle in settings, and it is the first thing worth looking for after installing. The other is the loading model: a game that fetches every level from a server will feel slow on a poor connection no matter how fast the phone is.

An honest caveat

Everything above is observation by hand on ordinary consumer phones, not laboratory measurement. This site does not have high-speed capture equipment, and no number on it should be treated as one. What it can tell you is which of these games feels like it is waiting for you and which feels like you are waiting for it — and for a game played with a thumb, that is the difference people actually notice.

Back to the comparison data