Embedded play area
The arena scales inside its own section, so the page can still have navigation, copy, and support blocks above and below it.
One-page browser game
Flick an AI skater through neon firewalls.
This is a proper one-page site, not just a full-screen app shell. The game lives on the page, the controls are explained, and the whole thing stays in one HTML file.
1 file
Single HTML page with the site and game together.
Touch-first
Built for finger flicks, quick swipes, and short runs.
Arcade feel
Combo loops, trick gates, data shards, and hazard hits.
AI skin
Neural charge, firewalls, reboot language, and neon UI.
What is on the page
A real one-page site around the game.
The game section sits inside a scrollable landing page with context, controls, and supporting content instead of taking over the whole browser like a raw prototype.
Cleaner product feel
There is now a header, hero, features, how-to-play section, FAQ, and footer, so it reads like a playable microsite.
Still one artifact
You can upload a single HTML file and get the whole thing in one page instead of juggling separate site and game files.
Playable section
Play Finger Skater AI.
Short-run score chase. Pull, launch, carve, boost, survive. On mobile, the game area captures touch input while the rest of the page still scrolls normally.
What changed from the raw game build
The page now scrolls like a small product site. The game no longer assumes it owns the whole viewport, and the arena is sized inside a dedicated section.
What stayed the same
The core loop is still pull-to-launch, swipe-to-boost, collect shards, hit gates, avoid firewalls, and chase a higher score before your charge runs out.
FAQ
Three practical notes.
Is it really one page?
Yes. The site and game are in one HTML file. The only external dependency is the Phaser engine script from a CDN.
Will it work on mobile?
That is the main target. The arena is touch-first and the rest of the page remains scrollable outside the game area.
Can it be made fully offline?
Yes, by bundling Phaser locally instead of loading it from a CDN. That would still keep it as one deployable page if you inline or self-host the engine.