Tiny WebGPU prototype to Rust game on eight platforms in two months A solo developer shipped Loot Hole, a Rust-based digging game, to Steam Early Access on 19 November, 55 days after the project's first commit on 25 September as a small WebGPU prototype. The game now runs on eight platforms — browser (via three.js WebGL 2), Windows, macOS, Linux, Steam Deck, Android, iOS (in TestFlight), Meta Quest and PC VR (development builds) — with a shared Rust core compiled to WebAssembly for the browser and natively elsewhere. The developer reports that AI models wrote most of the code, requiring custom tooling, and that a Galaxy A40 phone benchmark kept three.js in the browser after the game moved to Rust. ← All posts https://saltedcaramelgames.com/blog Tiny WebGPU prototype to one Rust game on eight platforms in two months Loot Hole began as a small WebGPU page and launched on Steam 55 days later as one Rust game that runs in the browser, on Windows, macOS, Linux, Android, iOS, Meta Quest and PC VR. The phone measurements behind each switch, the byte-exact world that co-op and saves depend on, and the AI tooling that made it possible for one person. Loot Hole is a game about digging up your front yard. It started on 25 September as a small WebGPU page and launched in Early Access on Steam https://store.steampowered.com/app/5389630 on 19 November, 55 days after the first commit. In between it moved to WebGL 2, then to a shared Rust core, and that core now runs on eight platforms. three.js draws it in the browser; wgpu draws it everywhere else. | | Distribution | Status | |---|---|---| | Browser | desktop and phone browsers, on Playgama https://playgama.com/game/loot-hole | Live | | Windows, macOS, Linux, Steam Deck | Steam https://store.steampowered.com/app/5389630 | Live, Early Access | | Android | Google Play https://play.google.com/store/apps/details?id=com.saltedcaramelgames.loothole | Live | | iPhone and iPad | App Store | In TestFlight | | Meta Quest, PC VR | Meta’s store, Steam planned | Development builds | Along the way a phone benchmark kept three.js in the browser after the game had moved to Rust, and co-op and saves came to depend on every build generating the same terrain, down to the byte. I built it alone, with AI models writing most of the code, which took tooling of its own. From WebGPU to WebGL 2 I started with Babylon Lite and WebGPU because a small scene with glTF models and shadows came to about 100 KB.