July 2024 Summaries

Firebase App Hosting, a serverless hosting service for server-rendered web applications that manages builds, CDN delivery, and server-side rendering, has expanded its public preview capabilities following its Google I/O announcement. New features include wildcard custom subdomains for routing many tenant-specific domains to one backend, initial Nx monorepo support that automatically builds dependencies and deploys a selected app, and the ability to create multiple backends within a Firebase project for environments or separate applications. Developers can also use FirebaseServerApp and Firebase Authentication within Next.js middleware to protect routes, redirect users, and enforce authorization, while accounting for CDN caching behavior. Other updates include support for deploying GitHub repository subdirectories, a multiple-environment deployment guide, Node 20 as the default build version, improved GitHub credential handling and rollout triggers, plus fixes involving pnpm, custom domains, and Angular SSR. Planned enhancements include regional backend creation beyond the United States, apphosting.yaml environment overrides, usage and billing metrics, improved deployment failure visibility, manual GitHub rollouts through the Firebase CLI, and continued SDK improvements for Next.js, Angular, and SSR use cases.

Firebase Cloud Messaging delivery reports classify Android push messages as delivered, pending, collapsed, dropped because of excessive pending messages, dropped after an app is force-stopped, dropped for inactive devices, or expired by their time-to-live setting. Delivered messages do not necessarily mean a notification banner was displayed, while offline devices, Doze mode, stopped users, and throttling can cause expected or unexpected delivery delays. Developers can reduce avoidable drops by using collapse keys where appropriate, setting suitable TTL values, managing stale registration tokens, handling the onDeletedMessages callback with server synchronization, and avoiding large queues of non-collapsible messages for disconnected devices. For deeper analysis, FCM supports analytics labels, aggregated delivery data, and troubleshooting tools, although delivery metrics should be interpreted as trends because not all statuses are included and totals may not equal 100 percent. The post also notes that Google Play Services may proxy eligible high-priority notification messages, which can affect how delivery and app-receipt analytics are reported.

Gemini in Firebase is an AI assistant integrated into the Firebase console that provides conversational guidance on Firebase products, app design, troubleshooting, and code generation. The account describes using it to plan a habit-tracking application, select appropriate Firebase services, design a data structure, configure authentication, locate project keys, set up the Firebase Web SDK, and generate HTML for a user interface. It is presented as a way to accelerate development and make Firebase more approachable, though users are advised that outputs can vary, generated code should be tested before production use, and licensing restrictions may apply.