The short version
The Last Pawn strips chess down to one piece and one problem: you're the last black pawn on the board, the white army advances one step from every direction each turn, and your only goal is to survive as long as possible while capturing whatever you can when your capture meter fills. It's a clean, quick idea, and the touch implementation is a genuine one-to-one match for the keyboard — swipe to move in any of four directions, tap to pass a turn, confirmed working for every action by actually playing five consecutive turns entirely by touch. The one real miss is the in-game "How To Play" screen, whose instructional text is effectively invisible against its own background on both phone and desktop — a real bug for anyone learning the rules from inside the game rather than the README.
Biggest strengths
- Full touch/keyboard parity confirmed by playing five real turns entirely via simulated swipes and taps — swipe up, right, left, and down each moved the pawn in the matching direction, and a plain tap correctly passed a turn, with the score and turn counters advancing exactly as they do on keyboard
- Built on react-swipeable with the same handlers used for both mouse-drag and touch, so there's no separate, easily-neglected touch code path to fall out of sync with the keyboard version
- Clean, legible in-game HUD — score, turn count, and a capture-readiness meter are all clear at a glance during actual play
Biggest weaknesses
- The "How To Play" menu's instructional text is rendered in a light tan that is effectively invisible against the screen's own orange chevron background — confirmed present in the page (the exact wording reads back fine via the page's own text content) but not visibly readable on either a phone or a desktop screenshot, on the exact same build in both cases
- The core loop — move, avoid, wait for the meter, capture, repeat — is simple enough that its ceiling is more about how long you can maintain focus than any deepening mechanic; there's no escalation beyond the white army closing in a little faster over time
- A single sitting is likely to show most of what the game does; there's no unlock progression or mode variety to pull you back for a second session beyond beating your own score
Who it's for: Fans of short, turn-based "how long can you last" survival puzzles who want something that plays as well on a phone as at a desk
Our recommendation: Worth several rounds for the swipe-driven survival loop; read the controls before you start, since the in-app instructions won't actually tell you
7 / 10
Chess has been mined for spinoffs for decades, but "you are one pawn and the entire opposing army is closing in" is a clean enough hook that The Last Pawn doesn't need much else to hold attention for a few minutes. Each turn, every white pawn on the board advances one square toward you; you get one move — up, down, left, or right — or you can hold your ground and wait, and a capture meter fills as you survive, letting you take an enemy piece when it's full. The score climbs for every turn you're alive. That's the whole game, and it works because the tension is immediate: there's no menu of upgrades between you and the next decision.
Touch that actually matches the keyboard, verified by playing
The developer's own control diagram promises full touch parity, and this was tested rather than taken on faith. Starting a fresh game and issuing five real swipe gestures — up, right, left, down, then a plain tap — moved the pawn in exactly the direction each swipe indicated and advanced the turn counter once per action, with the score climbing by 50 points a turn precisely as it does when the same sequence is played with WASD on desktop. useInputs.js confirms why this holds up: both input methods write into the same movement handlers through react-swipeable, rather than a separate touch layer that could quietly drift out of sync with the "real" keyboard version. This is exactly the kind of touch implementation this shelf is built to reward — not a token gesture, a full substitute.
Read the rules somewhere other than the game itself
The one place this build falls down is, unfortunately, the screen whose entire job is explaining how to play. Tapping "How To Play" from the main menu on a phone or a desktop browser produces a mostly-empty orange chevron pattern; the instructional text — "Move: WASD (or swipe), Pass Turn: Space (or tap), Capture enemies by moving into them when the bar is full" — is genuinely present in the page, readable directly from its own text content, but rendered in a colour close enough to its background that it doesn't register as visible text on either device this review tested. Anyone learning the rules from inside the game rather than its GitHub README will come away with nothing from that screen, which is a real gap for a game that doesn't otherwise explain its capture-meter mechanic anywhere else in the UI.
Should you play it
Yes, once you know the rules going in — the controls genuinely work as advertised on a phone, and the turn-based survival tension holds up for as many rounds as you're willing to keep playing. Just don't expect the game's own tutorial screen to teach you anything; that part needs a real fix before it can be called finished.
Pros and cons
Pros
- Full touch/keyboard parity confirmed by playing five real turns entirely via simulated swipes and taps — swipe up, right, left, and down each moved the pawn in the matching direction, and a plain tap correctly passed a turn, with the score and turn counters advancing exactly as they do on keyboard
- Built on react-swipeable with the same handlers used for both mouse-drag and touch, so there's no separate, easily-neglected touch code path to fall out of sync with the keyboard version
- Clean, legible in-game HUD — score, turn count, and a capture-readiness meter are all clear at a glance during actual play
- MIT licensed with clear attribution; ships with zero analytics or third-party trackers
- Portrait-locked layout stays centered and correctly sized on both a phone viewport and a wide desktop window rather than stretching awkwardly to fill either
Cons
- The "How To Play" menu's instructional text is rendered in a light tan that is effectively invisible against the screen's own orange chevron background — confirmed present in the page (the exact wording reads back fine via the page's own text content) but not visibly readable on either a phone or a desktop screenshot, on the exact same build in both cases
- The core loop — move, avoid, wait for the meter, capture, repeat — is simple enough that its ceiling is more about how long you can maintain focus than any deepening mechanic; there's no escalation beyond the white army closing in a little faster over time
- A single sitting is likely to show most of what the game does; there's no unlock progression or mode variety to pull you back for a second session beyond beating your own score