Home / Companies / Firebase / Blog / April 2019

April 2019 Summaries

4 posts from Firebase

Filter
Month: Year:
Post Summaries Back to Blog
Firebase introduced scheduled Cloud Functions through a new Pub/Sub function type that automatically configures Cloud Scheduler and a Pub/Sub topic, providing a more secure and manageable alternative to publicly accessible HTTP endpoints, App Engine, third-party schedulers, or manually managed Pub/Sub messaging. Available with firebase-functions Node.js version 2.3.0 and Firebase CLI version 6.7.0, the feature lets developers schedule functions using either standard cron expressions or plain-English intervals, such as daily execution at a specified time or every five minutes. Setup can be completed using Firebase tools rather than the Google Cloud console, with documentation and a GitHub sample available. Use requires the Blaze billing plan because it relies on Cloud Scheduler and Pub/Sub; Scheduler jobs cost $0.10 per month each, although three jobs per Google account are free, in addition to standard Cloud Functions, Pub/Sub, and related service costs.
Apr 18, 2019 419 words in the original blog post.
Firebase Hosting now integrates with Google Cloud Run, enabling developers to route Hosting requests to fully managed, stateless containerized backends rather than relying solely on Cloud Functions for Firebase and its Node.js environment. Developers can deploy any Docker image that serves HTTP requests through the required port and responds within 60 seconds, then configure Firebase Hosting rewrites in firebase.json to direct specific paths or API routes to a Cloud Run service. The integration supports languages and frameworks such as Go, Ruby, Java, Dart, and others, while Cloud Run automatically scales containers horizontally and permits up to 80 concurrent requests per container to help reduce cold starts. Firebase Hosting’s global CDN can also cache dynamic Cloud Run responses through Cache-Control headers, improving performance for content that changes infrequently. Although Cloud Run is managed through the Google Cloud console, Firebase projects already include an associated Google Cloud project.
Apr 11, 2019 849 words in the original blog post.
At Cloud Next 2019, Firebase announced several platform updates and encouraged attendees to visit its App Dev expo booth, while directing remote developers to documentation and future blog coverage. Paid Google Cloud Platform support plans now include Firebase products, offering services such as faster response targets, phone support, and enterprise technical account management alongside existing free community support. Firebase Hosting can now integrate with Cloud Run, allowing developers to deploy HTTP-invoked, stateless containerized microservices in languages beyond the Node.js requirement associated with Cloud Functions for Firebase. Google Analytics for Firebase is expanding event-report filtering to support multiple user properties and audiences simultaneously, with the rollout applying retrospectively to data from December 2018. Dynamic Links also gained support for any owned custom domain, provided the domain or a suitable subdomain is hosted on Firebase Hosting.
Apr 10, 2019 914 words in the original blog post.
ML Kit has introduced two on-device natural language processing APIs, Language Identification and Smart Reply, expanding the platform beyond its prior image and video-focused capabilities for iOS 9.0+ and Android 4.1+. Smart Reply generates suggested responses from up to 10 recent chat messages through a stateless process that neither retains conversation history nor sends it to servers, initially supporting English and incorporating safeguards to avoid suggestions for sensitive topics or unsupported languages. Built with TensorFlow Lite, SentencePiece encoding, and Transformer-based models, it is designed for simple integration into messaging applications and has been adopted by textPlus. Language Identification recognizes text across 110 languages, usually using only a few words and returning results in roughly 1–2 milliseconds, with BCP-47 language codes, an undetermined result when confidence is insufficient, and optional confidence-ranked language alternatives.
Apr 02, 2019 893 words in the original blog post.