And Cloud Functions for Firebase no longer needs "onFlow". There's direct support for Genkit in the new "onCallGenkit" function, which automatically turns a Flow into a Callable Function. Callable functions have always supported features like AppCheck natively.

For Next.js we'll use the firebaseContext middleware to enforce App Check and type safe client API. Again, if your flow supports streaming, so does the handler:

You can host this on any express path you want now. Streaming is automatic, and auth/context middleware is platform agnostic. Here, we use the "apiKey" middleware which stores, and optionally validates, an API key.

No matter where you want to deploy Genkit (on or off of Google Cloud) we can start with the following (streaming) Genkit code:

During this release, I helped focus on practical usability & portability. Genkit logic is decoupled from how you host it. A reusable Genkit action, can be easily hosted in Express, @nextjs.org, and Cloud Functions for Firebase with ~1LOC. Examples of each platform below:

Firebase’s IDX lets you build iOS apps in the browser.

And they keep coming in. They follow and like a few of my posts

firebase.blog/posts/2024/1... also, this week we’ve fixed a bug where enterprise users without a default compute account could not deploy. Every time you tried, it paged me personally, so I hope that’s sufficient apology 😅