POLYTRACK, MEASURED
PolyTrack platforms: browser, app stores
PolyTrack runs in a browser and ships as an app in two stores. The listing is specific about where it runs and silent about whether the builds differ.
| Platform | What the listing says | Our check |
|---|---|---|
| Browser | Desktop, mobile and tablet; HTML5 | NEEDS CHECK |
| CrazyGames app | iOS and Android | NEEDS CHECK |
| Google Play | Linked from the listing | NEEDS CHECK |
| Microsoft Store | Linked from the listing | NEEDS CHECK |
| Orientation | Landscape only | NEEDS CHECK |
OFFICIAL ONLY
Platform list is the store listing’s, read on 2026-11-02.
What we want to compare
- whether the version number printed in the client is the same on each host
- whether the browsers build carries ads or a “play next” frame that the app builds do not
- whether leaderboards are shared between hosts
- whether a track code made on one host imports on another
IN-GAME
The client speaks the host’s language, not the browser’s. On a Chinese CrazyGames session the in-game text stayed Chinese after we forced the browser locale to en-US through the debugger. If you want English in-game, change the CrazyGames site language before launching.
Why host differences are worth a page
The same HTML5 build can behave differently depending on who frames it: portals add their own shell around the canvas, pause it when a tab loses focus, and sometimes inject an ad between the menu and the race. A time set on one host is not automatically a time on another if the build numbers differ.
The comparison that matters is narrow and checkable: the version string printed in the client, whether a leaderboard is shared, and whether a track code made on one host imports on the other. Those three answers decide whether “played on CrazyGames” and “played on the app” mean the same thing.
What we will not compare
Frame rate, load time and ad density are differences between hosts, but they vary by machine, connection and the hour of the day. Reporting them as facts about a host would be inventing precision, so this page sticks to the three checkable things: version, leaderboards, and whether a track code crosses over.