Sandspiel

Mobile gaming has spent a decade refining the hook: login streaks, energy timers, a premium currency for every occasion. Sandspiel asks for none of it. There are no goals, no scores and no levels. On iOS there are also no ads, and the app collects no data. What remains is a grid, a palette of elements and a set of simple physics rules that can turn a few brush strokes into a long cascade of consequences.

Max Bittker first launched Sandspiel as a browser game, and that original is still playable at sandspiel.club. The native iPhone and iPad app, released January 21, 2026, brings the same idea to touchscreens. The lineage is openly acknowledged. Sandspiel draws on ha55ii’s Powder Game, a cornerstone of the falling-sand genre, where every pixel is a particle with its own behaviour. Sand piles into dunes. Water flows and pools. Fire spreads. Lava melts things. Plants and flowers grow. Put enough of these rules next to each other and the grid produces outcomes nobody drew.

The genre is well established, so Sandspiel’s case does not rest on a new concept. It rests on execution and on two additions that matter more than they first appear: a GPU-based wind and fluid simulation layered over the particle grid, and a community system where every creation is saved as a PNG image that carries its full game state, ready for anyone else to load and remix.

Reception is warm but thin. The iOS App Store listing averages 4.8/5 from 19 ratings, a small sample that nonetheless points the same way as the visible complaints, which concern button placement and missing options rather than the simulation. Sandspiel presents itself as a calm, open-ended toy for experimenting. Its business model is free with no ads or data collection on iOS, which removes the usual reason to treat a free mobile game with suspicion.

• Element palette: Sand, water, ice, lava, fire, oil, wall, plant, seed, fungus, acid, concrete and a chaotic “rocket” material, each painted directly onto the grid and each governed by its own rule set.
• Emergent chain reactions: Water pools, fire spreads and burns, flowers grow and lava melts other materials, so a handful of strokes can set off long sequences of interacting events.
• GPU wind and fluid simulation: A dedicated fluid layer lets players blow particles across the canvas, adding a force that acts on the whole scene instead of one cell at a time.
• PNG save format: Each creation is stored as an image that encodes the complete game state, so a save works as its own preview.
• Community gallery with remixing: Players upload creations, browse and vote on other people’s work, and load any upload to build on it.
• No ads, no data collection: The iOS version is free and carries neither advertising nor data harvesting.

A Loop Built on Cause and Effect

Sandspiel’s loop has three beats: choose an element, place it, watch. Nearly everything of interest happens in the third beat. Each material follows a local rule. Sand settles, water seeks the lowest point, fire propagates. As a result, the player authors initial conditions, not outcomes. A basin of wall, a pour of water and a scattering of seeds is a plan, and the simulation decides what that plan becomes. The pleasure lives in the gap between intent and result.

This is why the lack of goals reads as a design decision instead of an unfinished game. Objectives would push players toward specific end states, and specific end states are the least interesting thing a falling-sand engine produces. The interesting output is the unexpected one: the fire that finds a path nobody intended, or the dune that collapses into the reservoir. Bolting a scoring system onto that would turn experimentation into optimisation, and we think Bittker was right to resist it.

The cost is real, though. With no goals or scores, there is no scaffolding to teach the more interesting interactions. Discovery depends entirely on the player’s curiosity. Someone who never thinks to put two particular elements side by side may never see the best reactions in the palette. For a curious player, that self-directed discovery is the appeal. For everyone else, it is onboarding friction with no tutorial-shaped exit.

The Palette as a Design Statement

The element list is compact, and the design is better for it. Each entry earns its place through its relationships with the others. Wall provides structure. Sand and water provide motion. Fire and lava provide destruction. Plant, seed and fungus provide growth. Ice, oil, acid and concrete widen the space of possible interactions without bloating the menu. A shorter palette means each element gets used more and its behaviour becomes familiar faster, so the combinations, not the inventory, carry the depth.

The rocket material is the most useful inclusion. Its role is to be the one element that refuses to behave. An otherwise orderly set of rules needs a disruptor, and the rocket gives the calm sandbox a pressure valve. It turns careful construction into spectacle on demand.

Wind: The Second Axis of Control

Gravity alone makes a particle simulation feel like a terrarium: interesting to watch, limited to touch. The GPU-driven wind and fluid layer changes the relationship. Instead of painting cell by cell, players can push whole regions of the canvas at once, scattering dust, shaping drifts and steering reactions already in progress. The dust and wind effects are the most satisfying part of the system, and the reason is structural. Wind lets the player intervene during the reaction instead of only setting it up. That makes Sandspiel feel like an instrument rather than an aquarium.

Saves as Images, Creations as Starting Points

Storing every creation as a PNG that holds the full game state is a neat piece of engineering. The save file is its own thumbnail. A gallery of saves is literally a gallery of images, and each one can be revived as a live simulation. It is the kind of decision that disappears into the product, which is the point.

The community system builds directly on it. Upload, browse, vote and remix is a short list, but remixing is the feature that matters. It turns the gallery from a showcase into a library of starting conditions. A strong creation becomes raw material for someone else’s experiment, which extends the life of a toy that has no content pipeline of its own. Voting adds a light curation layer that surfaces the best of the community’s work without any leaderboard pressure.

Where the Design Runs Thin

Players have asked for a few control options, and the requests point at real gaps. itch.io players want adjustable simulation speed, a reasonable ask for a game whose best moments are fast chain reactions that could reward a slower, closer look. Slow motion would make the simulation more readable. Fast-forward would shorten the wait on slow-growing scenes. An App Store reviewer asked for a black background, a cosmetic request that still shows how much players care about how their creations look as images. Neither request is a fundamental flaw. Both are the kind of polish that separates a good toy from a very good one.

Sandspiel’s art direction is the simulation. Every pixel is a particle, so the look is whatever the rules produce at that moment. This is honest, functional pixel art, and the detailed animation of each element carries the aesthetic. In a game with no characters or story, the way water ripples or fire spreads carries the entire visual burden. The emphasis on per-element motion is the right priority.

The interface follows the genre convention of a palette of materials alongside the canvas, which keeps the UI simple at the cost of screen space. One concrete flaw is built in. On iPhone the bottom control row sits hard against the home bar, a safe-area layout problem on a device where every millimetre of the screen counts, and precisely the sort of issue a native port should have solved.

On performance, the engine’s architecture is designed with mobile in mind. The simulation is written in Rust and compiled to WebAssembly, with WebGL rendering, and it was built to run smoothly on both desktop and mobile. Falling-sand games are computationally busy because the whole grid updates continuously. Moving the wind and fluid work to the GPU is the right call, and a 2D simulation of this scope should sit comfortably within the capabilities of modern iPhones and iPads.

The App Store version covers both iPhone and iPad as a native app, and it is free, with no ads and no data collection. The browser original remains available at sandspiel.club, so the iOS app’s job is to deliver the same sandbox in a touch-first form. The element set carries over intact: acid, oil, lava, fire, sand, water and the rocket.

Touch input suits the genre in principle. Painting materials with a finger is about as direct as interaction gets. Precision is the trade-off. On a phone, a fingertip covers the very spot being painted, which a mouse cursor on desktop never does. The iPad should be the more comfortable home for Sandspiel, since a larger canvas gives both the brush and the chain reactions more room. The iPhone build carries the same safe-area tension, so the smaller device has the rougher edges for now.

Sandspiel knows what it is and declines to be anything else. Max Bittker took a well-established genre, kept the rules simple, and added two features that justify its place: a wind layer that turns observation into participation, and a PNG save format that makes every creation a shareable, remixable starting point. Releasing it on iOS with no ads and no data collection makes it an easy recommendation for the right audience.

Its limits are equally clear. There is no structure to fall back on when curiosity runs out, no speed control for studying the reactions it does best, and an iPhone layout gap that a native port should not have shipped with. None of these damage the core simulation, but together they keep Sandspiel a good toy rather than a great one. We recommend it to anyone who finds a chain reaction more rewarding than a high score. Players who need a finish line should look elsewhere.