The problem

Games are where interface and responsiveness get tested hardest — a fraction of a second of lag is the difference between fun and frustrating. We built ClickyCars partly as a product and partly to prove a point: that a genuinely engaging, real-time game with progression and competition can run entirely in a browser, install to a phone home screen, and work offline — with none of the friction of an app-store download and review cycle.

What we built

A complete casual racing game MVP that runs as an installable web app, with the full loop of play, progression, customisation and competition that keeps people coming back.

• Real-time racing with quick match, offline play and ghost races
• A garage with cars, paint, upgrades and a “chop shop”
• Global leaderboard and named racer identities
• Tournaments and daily missions for retention
• A coin economy with rewards and referrals
• Installable to the home screen (PWA), works offline, no app store
• Sound and full mobile-first touch UI

The interesting part

The interesting engineering in a game is state and feel. A racing game has to update speed, position, the opponent and the clock many times a second and keep it all in sync while feeling instant to the thumb — in a browser, on a mid-range phone, sometimes offline. Then wrapped around that twitchy real-time core is the slow, persistent layer: coins, upgrades, leaderboards, missions. Those two clocks — the sixty-times-a-second one and the across-sessions one — have completely different rules, and keeping them from corrupting each other is the actual craft. It is the same design principle behind our serious work: know which layer owns which decision, and never let one grade the other.

Built by SparkSols. A live, installable, offline-capable web game — proof that “just a browser” is no longer a limit.