[MUSIC PLAYING]
FRANK VAN PUFFELEN: We had a lot of updates
this past month, which I distill down to five topics for today.
Firebase Extensions lets you add functionality to your app
quickly with prepackaged configurable solutions.
Once installed, each extension performs
specific tasks in response to HTTP requests,
Cloud Scheduler events, or triggering events
from other projects, like Firestore or Cloud Messaging.
You can now find relevant extensions for many products
right inside the Firebase Console for those products.
So the Firestore panel in the Console
now shows the extensions that we see here,
while we show similar relevant lists for Auth, Storage,
and Realtime Database.
And before you install an extension from extensions.dev,
you can now see how many developers
have dev extension installed already, as a quick way
to gauge its popularity.
And if you find an extension that
engages in abusive or malicious behavior that
has other problems, you can now report it to our team right
from extensions.dev too.
Now for an embarrassing topic.
It turns out that I missed multiple updates
to the Firebase C-line, as they were no longer being published
to our Firebase Release Twitter feed.
And while we caught up with most of the updates
to web frameworks over Google I/O,
here are a few of the other updates that I missed.
The CLI now supports Node.js version 20 for web frameworks
and Cloud Functions for Firebase.
And it has dropped support for Node.js version 14.
We edit a set of ext:dev commands to publish and manage
extensions.
So these are for developers who build extensions
for themselves and others that they want
to publish on extensions.dev.
And you can now manage Firebase app distribution
groups with the new app distribution group
create and delete commands, and we
added a group alias option to the app distribution testers
add and remove commands.
And the good news is that we now have a dedicated documentation
page for CLI releases, as we can see here.
And we're including the CLI updates
in the main release patches too, so that I can't forget them
anymore.
So check the link to catch the updates yourself going forward.
A few years ago, we added support
for the so-called long polling connections
under the hood of our Firestore JavaScript, just in case.
Long polling allows decline to continue
to function in some uncommon constrained network
conditions, such as when traffic is routed
through buffering proxies, enterprise portals,
or when anti-virus software tries
to filter network traffic.
We now enable the logic to auto-detect
the need for long polling in our SDKs,
so your users will see fewer connectivity issues
without you having to make any changes to the code.
And if needed, you can configure the timeout
for get requests with long polling,
as shown in this code example.
A few months ago, I told you that our engineering team had
started writing detailed papers on how Firestore works
internally, starting with an article called
"Understand reads and writes at scale."
These papers complement our existing documentation
on how to use Firestore in your app,
and they are great for those of us who want to learn more.
We now added a second article called, "Understand real-time
queries at scale."
This article adds guidance on scaling your serverless app
beyond thousands of operations per second
or hundreds of thousands of concurrent users.
The new article contains a wealth of information again,
including this diagram on how real-time queries for snapshot
listeners are fulfilled in nine easy steps.
Well, OK.
Maybe it's not that easy, so be sure to read the entire article
that I'll link below.
And finally, some quick updates for developers
to use our SDKs for iOS and other Apple platforms.
Since SDK version 10.10, calling Cloud Functions from Apple
platforms can now opt into using limited use App Check tokens
that I mentioned last month.
That reduces the risk of abusive replay attacks,
but it adds extra overhead to the calls,
so you should only use it for use cases that require
the extra level of security.
And if you use Cloud Storage on Apple platforms,
our SDK will now report progress if you pass an optional closure
to putDataAsync, putFileAsync, or writeAsync methods.
Those were all the updates we have time for today.
If you liked the video, be sure to give it a thumbs
up and subscribe to the channel below.
Now my name is Frank Van Puffelen,
and I'll see you on a future episode of "Firebase Release
Notes."
[MUSIC PLAYING]