Skip to main content
Turntable is a mobile app where players scroll a vertical feed of instantly playable HTML5 mini games — and play them right there, no install, no loading screen worth mentioning. What makes Turntable different for you as a developer: games plug into a shared platform layer you don’t have to build:
  • Player identity — every player has an account from their first scroll (guests included), with a public @handle, stats, and achievements
  • Saved state — per-player, per-game persistence that survives app restarts and sign-ins
  • Scores & achievements — one call reports a score; the platform does the rest
  • A shared economy — platform-wide coins, per-game shop items with transparent loot-box odds, and purchases that always go through a native player confirmation your game can’t fake
  • Distribution — the feed algorithm puts your game in front of players; gameplay clips (recorded in-app) act as trailers that link straight to your game

​
How games work

A Turntable game is one self-contained HTML document. The platform serves it inside a sandboxed WebView and injects window.Turntable — the SDK — before your code runs. That’s the whole integration surface: no build step, no packages, no native code.

The game document contract

What a valid Turntable game looks like

SDK reference

Everything on window.Turntable

​
Building with AI

Turntable’s games are AI-native: players generate games in-app from a prompt, and external AI agents are first-class developers — the MCP server gives any agent (Claude Code, Cursor, your own) the full contract, and https://api.turntable.games/llms.txt serves the same reference to anything that reads the llms.txt convention.