Unity Mobile Optimization: A Practical Checklist

A mobile game that stutters on a mid-range phone loses players before it earns them. The good news: most mobile performance problems come from a small number of causes, and profiling finds them fast. Here's the checklist I work through when tuning a Unity mobile game.

Profile first — always

Optimization without measurement is guesswork. Before changing anything, I profile on a real target device (not just the editor) to see where the frames actually go. The bottleneck is rarely where you'd assume, and fixing the wrong thing wastes time.

Draw calls and batching

• Reduce material variety so the renderer can batch — every unique material is a potential extra draw call.
• Use sprite atlases and shared materials for 2D and UI.
• Watch dynamic UI: a canvas that rebuilds every frame is a common, hidden cost.

Memory and garbage collection

On mobile, GC spikes cause the stutter players feel most. The fixes are unglamorous but reliable:

• Pool objects that spawn frequently instead of instantiating and destroying them.
• Avoid per-frame allocations — cache references, reuse collections, and keep hot loops allocation-free.
• Keep textures and audio at the resolution the device actually needs; oversized assets quietly eat memory.

Frame pacing

A steady 30 FPS feels better than an average of 45 that constantly dips. Target a frame rate the device can actually hold, cap it deliberately, and smooth the spikes rather than chasing a higher number you can't sustain.

Verify the win

After each change, re-profile on device and compare against the baseline. If the numbers didn't move, revert and look elsewhere. The goal is measurable, before-and-after improvement on the hardware your players actually own — that's what I deliver on mobile optimization work, from published RPGs to online arcade titles.