Quick answer: Use fewer, smaller particles, reduce overlap and transparency, use simpler shaders, and cap particle screen coverage on mobile.

Particle overdraw on mobile is fill-rate cost. Reducing overlap fixes it. Here is how.

How to fix it

1. Reduce count, size, and overlap

Mobile is fill-rate limited, so large overlapping transparent particles are the main cost. Use fewer and smaller particles with less overlap — often half the particles look identical and cost much less.

2. Use simpler particle shaders

Complex per-pixel particle shaders multiply the overdraw cost. Use cheap additive or simple alpha-blended shaders for particles on mobile, reserving expensive shaders for opaque geometry.

3. Cap screen coverage

Limit how much of the screen particles cover at once, scaling effects down on mobile. A full-screen particle effect overdraws every pixel several times, which mobile GPUs cannot afford.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.