Last week the Firebase team released version 4.1.0 of the JS SDK. This minor version introduces lazy loading of the Firebase SDK.
…Let that sink in
In the words of David East:
The Firebase JS SDK provides a lot of functionality (Authentication, Realtime Database, Storage, FCM), but providing a simple interface to these powerful APIs comes at a cost, in this specific context, a byte cost (107KB gzip/min to be precise).
Being able to load that 107KB, on an as needed basis, enables developers to build performant experiences, while still getting the benefits of Firebase. To illustrate this, using WebPageTest, I took some comparisons of a simple lazy loading implementation using the Firebase Web Codelab.
Check out the comparison for yourself here.
In this test (testing an emerging market 3g connection), the lazy loaded implementation consistently loads almost a second faster (~0.9 seconds) in every measured metric.
Web page test even made a nice video: https://www.webpagetest.org/results/video/17/06/02/6f8dde4cdb789bba61dd16bae29ba553511c29ac/video.mp4
If you’ve ever been to the Firebase console, you’ve probably seen the following box before:
firebase-app.js is the only required file. It defines the firebase namespace, and provides the hooks for the rest of the components. You can then pick and choose which components you load (i.e. database, auth, storage, messaging) and can load them on demand as needed. Giving developers complete control.
Take a look at this JSBin following JSBin to see this in action.
You can take a look at the source code for the Firebase JS SDK on Github: https://github.com/firebase/firebase-js-sdk