Google's Firebase adds support for Google Cloud Functions and gets closer integration with Google Cloud Storage
At its Google Cloud Next conference in San Francisco today, Google is announcing updates to its Firebase portfolio of mobile-oriented cloud services.
Context & Ripple Effects
This update extends the arc Google started when it turned Firebase into a unified platform with analytics and notifications in May 2016: the mobile backend is being wired directly into Google Cloud's own primitives. Announced at the Google Cloud Next conference in San Francisco, the addition of Cloud Functions gives Firebase apps serverless compute, while the tighter Cloud Storage integration moves file storage onto Google's infrastructure.
The timing matters because 2017 became Firebase's heaviest expansion year — months later came Cloud Firestore, then AI-powered predictions and Crashlytics integration — making this Functions/Storage bridge the first step in folding Firebase into the broader Google Cloud stack rather than leaving it a standalone mobile suite.
First-order effects
- Mobile developers building on Firebase can now trigger Google Cloud Functions from app events and read/write files through Google Cloud Storage, replacing custom server code with managed cloud services.
Second-order effects
- The free plan Google introduced in 2016 becomes a funnel: apps that adopt Functions and Storage accrue Google Cloud consumption, giving Google a direct path from hobbyist mobile projects to paid cloud accounts.
Third-order effects
- If the cadence holds — unified platform in 2016, Functions and Storage here, Firestore and AI features later in 2017, enterprise-grade support by 2018, extensions and app distribution by 2019 — Firebase consolidates into a single app-lifecycle platform that makes Google Cloud the default backend for mobile development.
The trend: Google is steadily converting Firebase from a standalone mobile backend into the developer-facing front door of Google Cloud, one integration release at a time.