The first 72 hours after release are the most intense. Crashlytics shows a crash-free rate of 94% instead of the expected 99%. Firebase Performance reports cold start time of 8 seconds on mid-range Android. App Store reviews start appearing: "crashes at level 3". The team has no response process — developers moved to the next project, support isn't set up. We've seen this scenario dozens of times and know how to prevent it.
On one project (a hyper-casual Unity game), the crash rate hit 8% after release due to a memory leak on Android. Within 24 hours we found the bug — incorrect Addressables handling — and shipped a hotfix. Crash rate dropped to 0.5%. Such situations require a clear protocol and ready infrastructure.
Post-release technical support isn't "answering user emails". It's monitoring, diagnostics, hotfixes, and regular updates with a predictable cycle. Our experience: 5+ years in post-release game support, over 50 releases, from hyper-casual to large RPGs. We guarantee product stability and SLA compliance. Request a free project assessment.
Monitoring: What We Watch in the First Days
Firebase Crashlytics is mandatory. After release we monitor the dashboard in near-real-time: crash-free users percentage, new issues by version, devices with disproportionately high crash rate. Immediate hotfix trigger: crash-free users < 98% or a Fatal severity crash on top devices.
Crashlytics provides stack traces, but for Unity IL2CPP builds you need dSYM files (iOS) or symbol tables (Android) to decode native stacks. Without symbols, traces look like libil2cpp.so line 0x00034abc — useless. Firebase Crashlytics Symbol Upload via Fastlane or manual upload using firebase-tools is set once during build. Our engineers configure this during the initial audit.
Firebase Performance: monitor app_start trace, _st screen traces, custom traces for critical game paths (level load, IAP transaction). Anomalous load times on specific devices/OS versions are early warning signs.
Google Play Console and App Store Connect: ANR (Application Not Responding) rate on Android — target < 0.47% (Google's threshold for poor state). If ANR rate rises, we examine main thread blocking via Android Profiler.
Hotfix Process
Severity 1 (startup crash, broken IAP, progress loss): response within 1 hour, hotfix within 24 hours. Pipeline: diagnose via Crashlytics + local reproduction → fix → test on target devices → build via CI (GameCI) → expedited review for App Store (typically 24 hours with justification) → rollout on Android via staged deployment (10% → 50% → 100%).
Severity 2 (gameplay bugs, UI issues, performance): hotfix or planned patch within 1-2 weeks.
Staged rollout on Google Play is critical. Fastlane's supply supports rollout: 0.1 for 10% audience. We monitor crash rate and rating for 24-48 hours, then expand. A hotfix that itself contains a critical bug is worse than no hotfix. Our rollout approach reduces the chance of a broken update by 2x compared to full deployment.
Why Regular Updates Matter
Outside crises, a planned update cycle is key. For mobile games, optimal: patch updates every 2-4 weeks (balance, bugfix), content updates every 6-8 weeks. Regular patches maintain store rating and reduce churn.
Every update requires regression testing. Automated tests via Unity Test Framework (Edit Mode + Play Mode Tests) cover critical paths: game start, save loading, IAP flow. Manual testing on 5-10 target devices before each release isn't about economizing — it's because automated tests don't reproduce GPU-specific bugs.
How We React to Critical Bugs
Severity 1 requires immediate action. We use a dedicated communication channel (Slack/Telegram) with on-call rotation. Diagnostics start with Crashlytics and device logs. In 80% of cases, the root cause is identified within 30 minutes. Then code fix, hotfix build, and submission for review. For App Store, we prepare expedited review justification to meet the 24-hour SLA. On Android, staged deployment as described above.
Monitoring Tools Comparison
| Tool | Data Type | Cost | Notes |
|---|---|---|---|
| Firebase Crashlytics | Crash reports, stack traces | Free | Best for Unity IL2CPP, integrates with Google Play |
| Unity Analytics | Events, crash reports | Free | Simple integration, limited detail |
| GameAnalytics | Events, FPS, memory | Free (up to 100k MAU) | Flexible dashboards, segment filters |
What's Included in the Support Contract
- Daily monitoring of Crashlytics, Firebase Performance, store reviews
- Issue diagnostics and severity classification
- Severity 1 hotfixes within 24 hours
- Planned patch updates per agreed schedule
- Monthly report: crash rate, ANR rate, average rating, DAU trends
- SDK updates for new OS requirements (iOS major updates require verification annually)
| Severity | Example | Response Time | Fix Time |
|---|---|---|---|
| S1 | Startup crash, broken IAP | 1 hour | 24 hours |
| S2 | Gameplay bugs, UI issues | 4 hours | 1-2 weeks |
| S3 | Minor visual bugs | 1 day | Next patch |
Typical Mistakes in Post-Release Support
- Missing dSYM files for crash symbolication
- Ignoring ANR rate until rating drops
- Full rollout without staged deployment
- Skipping regression testing on real devices
Timelines and Formats
| Support Format | Contract Duration |
|---|---|
| On-call support (4-8h response) | from 1 month |
| Full support with planned patches | 3–12 months |
| One-time audit + monitoring setup | 1–2 weeks |
Pricing is determined after analyzing project complexity, target platforms, and required SLA. We offer a free project assessment — contact us for a consultation. Get reliable technical support for your game without missing deadlines.