February 2024 Summaries

Firebase has introduced a beta Release Monitoring dashboard in the Firebase console, powered by Crashlytics, to provide a real-time overview of recent mobile app production releases. Improving on the previous Latest Release page, it loads faster, supplies more information without requiring Google Analytics, and tracks release uptake, crash-free users, and the newly added crash-free sessions metric, which measures reliability across user sessions. Developers can compare the latest release with up to two previous builds to contextualize stability and use a “Top new issues” table to identify newly detected crashes and assess whether a rollout should be halted or rolled back. The dashboard requires supported minimum Crashlytics SDK versions across Apple, Android, Flutter, and Unity, as well as a newly published production version with sufficient user engagement, and is intended to support safer releases, progressive rollouts, real-time issue triage, and error alerting.

Firebase App Distribution has introduced Automated Tester in beta, an automated smoke-testing capability for Android applications designed to identify critical build issues before wider release. Developers can run tests on newly uploaded or existing APK and AAB builds through the Firebase console or CLI, selecting from various devices and Android API levels. The service checks core app functionality and delivers results in about 15 minutes, including identified issues, screenshots, and video recordings. Automated Tester is currently available at no additional cost up to a daily usage cap, after which Firebase Test Lab pricing applies, with future pricing details planned before general availability.

Firebase App Check expanded in public preview on February 14, 2024 to protect Google Identity OAuth clients for iOS, including apps that do not otherwise use Firebase. Using Apple’s App Attest service, the feature verifies app integrity and rejects iOS OAuth-client requests that lack valid App Check tokens, helping limit unauthorized or abusive interactions. Unlike App Check for Firebase Authentication, which protects supported post-sign-in Firebase Auth activities across multiple identity providers, Google Identity protection applies to specific user interactions through an iOS app’s OAuth client; both protections can be enabled independently or together. Enforcement can be configured individually for each OAuth client, with security restrictions including short-lived tokens and App Attest as the required production attestation provider, while the Debug provider remains available for development. The preview supports iOS 14 or later and requires Xcode 12.5 or newer, Firebase project and App Check registration, OAuth-client linking, and application changes to enable App Attest and configure Google Sign-In.

Firebase introduces two extensions, Build Chatbot with the Gemini API and Multimodal Tasks with the Gemini API, that let developers add generative AI capabilities to apps through Firestore with minimal AI expertise. A conference-assistant example uses a prompt containing event agenda data to recommend sessions and speakers, while retaining conversational context for follow-up questions. A multimodal example generates accessible image alt text by sending Cloud Storage images and guidance-based prompts to Gemini, then saving the resulting descriptions in Firestore for use in a gallery. The extensions incorporate Firebase security features including Secret Manager for API keys, Firestore Security Rules for data access control, and App Check for trusted-client protection, while Google AI Studio is suggested for testing and refining prompts before deployment.

Device Streaming in Android Studio, powered by Firebase, enables developers to remotely deploy, interact with, test, and debug Android apps on real devices hosted in Google’s secure data centers without leaving the IDE. Available in Open Alpha to Android Studio Jellyfish Canary users at no cost for a limited time, it supports various API levels and form factors, including Pixel phones, tablets, and foldables alongside select Samsung and other OEM devices. Developers connect through an ADB-over-SSL connection, can use familiar Android Studio debugging tools, rotate or unfold devices to assess app behavior, and avoid the performance demands of running local emulators. Access requires selecting a Firebase project with appropriate permissions, after which devices can be started from Device Manager or selected as deployment targets; sessions should be ended with the Return and Erase option, which securely wipes and factory-resets each device. Open Alpha usage is capped at four hours per Firebase project per day, and Google invites users to report issues and submit feedback on desired features and devices.