https://afanasev.net/categories/android/Recent content in Android on afanasev.netHugoen-USThu, 23 Apr 2020 23:18:12 +0700https://afanasev.net/android/crashlytics/2020/04/23/in-house-crashlytics.htmlThu, 23 Apr 2020 23:18:12 +0700https://afanasev.net/android/crashlytics/2020/04/23/in-house-crashlytics.html<h2 id="why">Why</h2> <p>For years, Crashlytics by Fabric was the gold standard for mobile crash reporting. It was fast, reliable, deeply integrated with Android tooling, and free. Teams adopted it without hesitation, and it became load-bearing infrastructure for mobile development at companies of every size.</p> <p>Then Google acquired Fabric.</p> <p>The migration from Fabric Crashlytics to Firebase Crashlytics was manageable for many teams, but it immediately raised a set of questions we could not get clear answers to. Firebase tools, as a rule, depend on Google Play Services — a hard requirement that excludes Huawei devices running HMS (Huawei Mobile Services) and the Chinese Android ecosystem more broadly, where GMS is not available. China represented a significant portion of our user base, and the prospect of running two parallel crash reporting systems — one for GMS markets, one for HMS — was operationally unappealing.</p>