June 2022 Summaries

Firebase Crashlytics has introduced updates aimed at improving crash reporting, developer productivity, and setup workflows across Flutter, Android, iOS, and Unity applications. Flutter support now includes on-demand fatal error tracking, crash-free user metrics, improved crash grouping, and a simplified setup process that avoids platform-specific IDEs. Android developers can view and investigate Crashlytics reports directly in Android Studio through the App Quality Insights window, while Android crash reports can also be filtered by Google Play release track after linking a Firebase app to a Play developer account. For iOS, the Firebase console now supports drag-and-drop uploads of dSYM archives, and Unity reporting has improved with Android fatal crash reporting, C#-oriented stack traces and grouping, native crash symbolication, and automatic iOS crash-data symbolication. Crashlytics has also streamlined onboarding and expanded implementation-testing guidance to help developers begin monitoring app stability more easily.

Part three of the Make It So Android app series explains how to integrate Firebase Crashlytics into a Jetpack Compose application to automatically capture, upload, and group fatal and non-fatal errors by factors such as device, operating system, app version, and severity. It covers adding the required Firebase dependencies and Gradle plugin, testing the setup by forcing a runtime crash, and creating a LogService abstraction that records exceptions through Crashlytics. The article also demonstrates using CoroutineExceptionHandler instances in ViewModels to log unexpected coroutine errors and, where appropriate, show user-friendly Snackbar messages through a centralized SnackbarManager backed by StateFlow. To reduce repeated error-handling code, it introduces a shared MakeItSoViewModel base class with reusable handlers for logging errors alone or both logging and displaying them. The next installment will cover using Cloud Firestore to store and synchronize to-do items in real time, while noting that the demonstrated version uses callbacks and later versions replace them with Kotlin Coroutines and Flow.

Firebase Quickdraw was expanded from a single-player AI drawing game into a multiplayer web app where up to four users can join shareable rooms, draw prompted objects, view one another’s progress, and compete for scores across six rounds. The project uses Firebase Hosting for global static delivery, Realtime Database for low-latency game-state synchronization, Cloud Functions for secure room joining, external handwriting-model calls, leaderboard resets, and cleanup, and Firebase Authentication and Security Rules to limit database access. Development challenges included designing a simple room-based database model, preventing race conditions with transactions, handling abandoned lobbies through Realtime Database’s OnDisconnect feature, and retrofitting security after the initial prototype. The team relied on the Firebase Emulator Suite and Chrome DevTools for isolated local debugging, while Firebase Performance Monitoring and Google Analytics measured load times, API responsiveness, player completion behavior, and audience insights. The account emphasizes that Firebase’s integrated tools reduced infrastructure work and enabled the team to focus on the multiplayer experience, while noting that Vertex AI is now called Agent Platform as of August 2026.

The third #FirebaserFriday profile introduces Caitlin Chen, a Firebase team member who moved from working as a software engineer on Crashlytics to focusing on Firebase Test Lab and the Firebase Console, despite initially having no mobile development background. She describes meeting Firebase mascot Sparky through a desk sticker, enjoys the Japanese reality travel-dating show Love Wagon for its comedic editing and cultural information, and shares her fondness for Taiwanese pork blood rice cakes and marinated pig ears, foods that helped her remain connected to her family’s culture while growing up near Los Angeles. The post is part of a monthly series highlighting Firebase employees, their product work, backgrounds, and perspectives, and directs readers to Caitlin’s Twitter profile and the broader Firebase community channels.