Google recently announced the acquisition of Firebase, a back-end-as-a-service (BaaS) provider that supports real-time synchronization. The acquisition provides Google with an important component to support an end-to-end development platform for Web and mobile apps. The acquisition also has more strategic implications by providing the company a monetization strategy to capitalize on a new brand of collaborative real-time Web app.
Firebase’s BaaS enables individual developers to build real-time applications that rival sophisticated applications built by a crew of skilled developers. The technology built by the Firebase team is able to automatically synchronize changes made in applications built on Firebase, across any connected device. If the app is offline, the data is saved locally and synced when a connection becomes available. While not necessarily new for large-scale apps, for less-experienced developers with limited resources, to build this type of synchronization engine from scratch is much more difficult. The Firebase platform makes this capability more accessible to the everyday developer.
Google will integrate Firebase with its Google Cloud Platform, making it easier for Google Cloud developers to build real-time apps. The service will run on the Google infrastructure, supporting better performance and scalability. Google will gain access to the 110,000 Firebase registered developers and will be able to provide an end-to-end platform that supports apps on Web and mobile. Google has also indicated that it will keep the service platform-agnostic.
Beyond the press release, there may be some more strategic and perhaps darker motivations to Google’s acquisition as the company positions itself to control the next generation of collaborative applications.
The emergence of WebRTC, another Google standard that enables real-time communications without a plug-in, combined with AngularFire multiuser capability, puts Google at the center of the future of real-time communications. Firebase’s synchronization engine is designed to listen for changes on connected devices so it can synchronize data across other devices. The ability to listen for these events allows the service to identify incoming calls. This functionality positions Firebase to operate as a signaling server that sets up a peer-to-peer connection. Some developers creating collaborative applications using WebRTC are already leveraging the capabilities of Firebase to support the signaling piece of the app. Should Google expand and grow this capability and developers adopt it, Google becomes a mobile operator.
As integration with Firebase and Angular gets tighter, the already-popular Angular framework will become the de facto standard. Google will be better positioned to invest developer resources in the platform, improving the technology and pushing competing technologies to the margins. With limited competition and control of the back end of real-time mobile apps, Google is free to change policies around Firebase to maximize profits.
This is a familiar game plan and Google has essentially executed this strategy with its Mapping API. While it's a great API that enables developers’ access to previously unavailable mapping services over the years, Google has added fees and restricts.
Regardless of how the market plays out, with the combination of Firebase and Google, scalability and performance is increased, improving experiences. With greater developer access, more apps will feature compelling, real-time and collaborative experiences stimulating more innovation and new businesses. Just like Android and the Google Mapping API.