The 30-second pitch
Casual gaming has a friction problem. Every "free" mobile title hides a 200 MB download, a tracking SDK
budget, mandatory account creation and a hardware compatibility list as long as your arm. HTML5 in the
browser quietly side-steps every one of those obstacles. Open a tab. Click play. That's it.
That isn't an opinion — Google, Apple and Microsoft have all spent the last decade making sure modern
browsers are first-class game runtimes. WebGL 2 ships in every evergreen browser. WebAssembly lets game
engines compile directly to the page. Web Audio handles spatialised sound. The Gamepad API exposes
controllers natively. The technology is here, and it has been for a while.
What changed in the last 24 months is the content finally caught up to the platform.
How we got here
For most of the 2010s, browser gaming meant Flash — and the death of Flash in 2020 looked, briefly, like
the end of the entire category. It wasn't. It was just a hard reset. Studios who had spent a decade
building Flash titles ported their work, and a new generation of developers built natively for HTML5
from day one.
The result is a catalogue that, as of 2026, is genuinely bigger and more diverse than the iOS App Store's
casual-games shelf. Hyper-casual hits, .io multiplayer, idle clickers, full-fat 3D platformers,
roguelites, racing sims — all of it now runs in a tab on a six-year-old laptop.
The three things HTML5 still does better than mobile
1. Zero-install discovery
Mobile gaming has trained a generation to associate "trying a game" with a 5-minute install loop. Browser
gaming flips that on its head. Most of our players try four or five games per session, finding the one
they want to settle into. That's almost impossible on iOS — you're not going to install five 300 MB apps
just to browse.
2. The link is the game
A browser game has a URL. You can share it. You can tweet it. You can drop it in a Discord. Your friend
clicks once and is playing — not "downloading", not "creating an account", playing. This single property
turns out to be huge for organic distribution.
3. Cross-device save state
Modern browsers sync localStorage and account-bound storage across desktop and mobile. Start a session
on your laptop at lunch, finish it on your phone on the bus. No "platform" lock-in. No "Game Centre"
plumbing.
Where it still falls short
We'd be lying if we said the browser was a perfect gaming environment. Three honest weaknesses:
- Long-form RPGs. Anything with 60+ hours of content still benefits from a native install — the asset
pipeline isn't optimised for that scale.
- Anti-cheat. Competitive multiplayer at scale still needs server-authority that's hard to retrofit on
WebSockets-only stacks.
- Audio latency on iOS. Safari's audio context wake-up is still a gotcha for rhythm games. (We've
open-sourced our work-around — see the Spinappy engineering notes.)
What we check before calling a browser game "ready"
The phrase "runs in a browser" hides a lot of messy detail. A game can technically load in Chrome and
still be a poor browser game. It might ignore touch input, trap the player in a broken full-screen mode,
or fail silently when a third-party asset host is slow. That is why our review process starts with the
boring checks before it gets to taste.
First, we look at the loading path. A good HTML5 game gives the player visible progress and a reasonable
first interaction within a few seconds on a normal connection. We do not expect console-level production
values from a lightweight browser title, but we do expect the player to understand whether the game is
loading, asking for input, or broken. A blank iframe is not a mystery; it is a failed first impression.
Second, we test controls before we judge design. Browser games live across keyboards, trackpads, touch
screens and sometimes gamepads. A clever puzzle with tiny drag targets is not clever on a phone. A racing
game that depends on analog steering but only exposes arrow keys is not really cross-platform. When a
title only works well on desktop, that can still be fine, but the review needs to say so plainly.
Third, we watch for the moment a game interrupts itself. Browser games are often supported by ads, and
some publishers handle that respectfully. Others break the first session before the player understands
the rule set. We separate those cases in our notes because friction matters. A game can be free and still
ask too much of the player's patience.
Finally, we test whether the loop survives repetition. Many HTML5 games are brilliant for three minutes
and thin at minute fifteen. That is not automatically a failure; short-session design is a legitimate
form. But the review should be honest about the shape of the experience. A coffee-break arcade title
does not need to pretend it is a season-long hobby.
Why curation matters more now
The technical barrier has fallen so far that publishing a browser game is no longer the hard part.
Discovery is the hard part. Players are not short on links; they are short on reliable signals. That is
where a site like Spinappy has to earn its place. If all we do is embed everything and call it a day, we
have added almost nothing. The useful work is in testing, sorting, explaining, and sometimes saying that
a popular game is only popular because it is loud.
That also means our catalogue will never be perfectly static. Games disappear, partner builds change,
controls are patched, and mobile browsers alter behavior without asking permission. A strong browser
game site has to treat its pages as living notes, not one-time uploads. The review date matters because
the runtime underneath the review can change.
HTML5 is not the future because it is glamorous. It is the future because it removes enough friction that
the actual game has to stand on its own quickly. That is good for players, and it is good for reviewers.
The weak titles reveal themselves faster. The strong ones do not need an install funnel to make their
case.
How Spinappy fits in
Spinappy is a curation layer on top of this ecosystem. We don't build the games — we partner with
licensed distributors to surface the best titles, then we
add the editorial layer: original reviews, control breakdowns, beginner guides and category tours.
The bet is simple. The browser is the most accessible game platform that has ever existed. Players
deserve a curation experience that matches.
What's next
Over the coming weeks the editorial team will publish:
- Genre tours: deep dives into our favourite titles in each category.
- Beginner's guides: how to get started with .io games, idle games, and the roguelite revival.
- Hidden gems: the titles that never went viral but deserved to.
If you want to suggest a topic, let us know. We read every message.