The short version
This is a real, working Klondike solitaire — a legal move (a black Jack onto a red Queen) was dragged into place with a mouse and resolved correctly, revealing the card underneath exactly as it should. The problem is that moving a card is the entire game, and moving a card only works with a mouse. Reading the shipped code confirms why: card dragging is wired to `onmousedown` and `click` alone, with no touch event listener anywhere in the bundle. A tap on the draw pile still works, because Chromium (and real phones) synthesize a click from a motionless tap — but an identical drag gesture, dispatched as real touch events, produced no movement at all, while the same coordinates as a mouse drag worked immediately. On top of that, the board has no viewport meta tag and lays itself out at a fixed pixel width of roughly 650-900px depending on measurement, so even the parts of the interaction that do work would need to be dragged around a desktop-sized board squeezed onto a phone screen. Neither problem is a guess; both were measured directly.
Biggest strengths
- The actual game logic is correct and complete: a legal tableau move was dragged into place with a mouse, the flip-capture rule was honored, and the card underneath was correctly revealed
- A tap on the stock pile does work on touch, since a zero-movement tap synthesizes a click event that the draw logic listens for — confirmed by tapping it and watching the waste pile receive a new card
- Clean, legible classic Windows-solitaire-style card art, entirely self-contained as inline base64 image data with no external asset requests
Biggest weaknesses
- Moving a card between piles — the only thing you actually do in solitaire — does not work on touch at all. This was confirmed two ways: reading the shipped JavaScript shows drag handling attached only to `onmousedown`/`mousemove`, with no `touchstart`/`touchmove` anywhere in the file, and a live side-by-side test dispatched an identical drag gesture as real touch events and as mouse events on the same board — the mouse drag completed the move instantly, the touch drag produced no change at all
- The page ships with no `<meta name="viewport">` tag and a fixed-pixel-position board (columns at hardcoded x-offsets 91px apart, spanning roughly 650-900px total), so it does not adapt to a phone-sized screen even for the parts of it that do respond to touch
- No keyboard support of any kind was found, so there is currently exactly one way to play this game: a mouse
Who it's for: Desktop mouse users who want a clean, no-frills Klondike; not phone players
Our recommendation: A solid desktop solitaire that has not been adapted for touch at all
3.2 / 10
Solitaire is a clean, self-contained Klondike implementation, and as a piece of desktop software it does what it says: seven tableau columns, four foundations, a stock and waste pile, and correct move validation. Reading the underlying rules out via testing rather than assuming them, a legal move was made by dragging a black Jack from one tableau column onto a red Queen in another — the game accepted it, moved the card, and correctly flipped up the card that had been sitting beneath it. That's the whole of Klondike working as it should.
The core mechanic has no touch support at all
This shelf exists specifically because Flash games can't be played on a phone, so every review here treats touch as the test that actually matters, and this is where Solitaire fails outright rather than partially. Reading the shipped main.js directly turns up exactly one relevant pattern: onmousedown for picking a card up, with drag tracked through subsequent mousemove events. There is no touchstart, touchmove, or touchend anywhere in the bundle. That was then tested rather than just inferred: the identical drag gesture — same coordinates, same path — was dispatched twice on the same board, once as real touch events and once as mouse events. The mouse version moved the card immediately. The touch version, despite the events reaching the page correctly (a tap on the stock pile elsewhere on the same board did successfully draw a card, since a motionless tap synthesizes a browser click event that the draw logic happens to listen for), produced no movement whatsoever. A player on an actual phone can watch cards get dealt from the stock and can do precisely nothing else, because there is no way to move a card into place without a mouse.
The layout doesn't help either
Separately from the touch problem, the page ships with no <meta name="viewport"> tag, and the board itself is laid out with hardcoded pixel positions — measured directly at 91px column spacing, putting the full seven-column tableau somewhere between 650 and 900px wide depending on how the browser resolves the missing viewport tag. Nothing in the CSS scales that down for a 390px-wide phone screen. Even a hypothetical touch-enabled version of this exact code would still hand a phone player a board sized for a desktop window.
Verdict
The game itself, judged purely as Klondike, is honest and correctly built, and that's reflected in gameplay and visuals here. But this section's admission bar is built entirely around whether a game can be played on a phone, and Solitaire's answer — checked directly in the source and confirmed by testing the exact interaction a phone player would need — is that it cannot. A draw-only interaction with no way to move a card is not a diminished experience; it is not solitaire at all.
Pros and cons
Pros
- The actual game logic is correct and complete: a legal tableau move was dragged into place with a mouse, the flip-capture rule was honored, and the card underneath was correctly revealed
- A tap on the stock pile does work on touch, since a zero-movement tap synthesizes a click event that the draw logic listens for — confirmed by tapping it and watching the waste pile receive a new card
- Clean, legible classic Windows-solitaire-style card art, entirely self-contained as inline base64 image data with no external asset requests
- MIT licensed, no analytics anywhere in the shipped bundle, loads in well under a second
- Fully self-contained (a single HTML file plus one JS bundle), easy to host cleanly
Cons
- Moving a card between piles — the only thing you actually do in solitaire — does not work on touch at all. This was confirmed two ways: reading the shipped JavaScript shows drag handling attached only to `onmousedown`/`mousemove`, with no `touchstart`/`touchmove` anywhere in the file, and a live side-by-side test dispatched an identical drag gesture as real touch events and as mouse events on the same board — the mouse drag completed the move instantly, the touch drag produced no change at all
- The page ships with no `<meta name="viewport">` tag and a fixed-pixel-position board (columns at hardcoded x-offsets 91px apart, spanning roughly 650-900px total), so it does not adapt to a phone-sized screen even for the parts of it that do respond to touch
- No keyboard support of any kind was found, so there is currently exactly one way to play this game: a mouse
- Sound was not verified either way in this environment; headless testing has no audio output