What should I fix first to stabilize before a sale?

The highest-impact crashes, the ones affecting the most players, since with limited time those few fixes most improve the experience for the wave of new players a sale brings. Ranking your issues by impact makes them obvious. Then raise your crash-free rate on real hardware and harden device-specific issues. Focusing on the vital few high-impact crashes beats spreading effort across rare bugs.

How do I know if my game is stable enough for a sale?

Check your crash-free rate on real hardware, it should be at a level where new players won't regularly crash out during their first impression, with your top crashes fixed. Reviewing your crashes by device also tells you whether the new hardware a sale brings is likely to surface problems. A measured crash-free rate plus device hardening gives you a concrete readiness picture, rather than a vague hope that the game 'feels stable.'

How Do I Stabilize My Game Before a Big Sale?

Quick answer: Use impact data to fix the crashes affecting the most players, get your crash-free rate up on real hardware, and address the device-specific issues new buyers might hit.

A big sale is the worst time for your game to be unstable, new players forming first impressions amplify every crash into bad reviews. Stabilizing beforehand, with limited time, means focusing on the highest-impact issues. Here's how to make your game stabler before a sale.

Fix the Highest-Impact Crashes

With limited time before a sale, you can't fix everything, so focus on the crashes affecting the most players. Ranking your issues by impact tells you which few fixes will most improve the experience for the wave of new players a sale brings, the highest-leverage stabilization work.

Bugnet ranks crashes by how many players each affects, so your highest-impact issues are obvious. Stabilizing before a sale is largely about this focus, fixing the vital few crashes that cause most of your instability, rather than spreading thin effort across rare bugs.

Raise Your Crash-Free Rate on Real Hardware

The concrete target is your crash-free rate on real hardware, the share of sessions that avoid a crash. Getting it up before the sale means new players are far less likely to crash out during their crucial first impression. Track it as you fix, so you can see the stabilization working.

Bugnet tracks your crash-free rate and the issues dragging it down, so you can watch it improve as you fix. Raising your crash-free rate on real hardware (not your dev machine) is a measurable stabilization goal that directly protects your sale-period reviews.

Harden the Devices New Buyers Bring

A sale brings players on hardware your existing base didn't represent, so device-specific crashes you've never seen can surge. Reviewing your crashes by device and hardening the configurations new buyers are likely to bring reduces the chance the surge exposes new problems.

Bugnet's device-tagged crash data shows which hardware is fragile, so you can address device-specific issues before the wave. Stabilizing before a big sale is fixing the highest-impact crashes, raising your crash-free rate on real hardware, and hardening for new devices, focused work that makes the most of limited pre-sale time.

Fix the highest-impact crashes (you have limited time, so prioritize the vital few), raise your crash-free rate on real hardware, and harden the devices new buyers bring. Focus ruthlessly before the sale.