Creating an Ionic PWA with Firebase Offline and Service Workers

Progressive Web Apps or PWA are rising.
As the name suggests, they are web applications. The only difference is the progressive aspect.
This word represents what we have been doing for years. We could have stayed at the Web 1.0 with static websites and funky blinking links, but thank god we didn’t.
The web evolved with client-server communications, serverless architectures and more is coming.
Progressive web apps are quite hard to define because they evolve with time.
Google’s definition is quite complete, identifying a PWA as an application that can be used offline, installed directly from the web, responsive, etc.
Five years from now, this might change and a PWA might become a web application with new features like Virtual Reality or Augmented Reality.
It might seem frightening to know that most of what we learn today might not serve tomorrow with new frameworks (Angular 45, Ionic 39, React 900, etc) but that’s the reality and also why we generally get paid a lot of money.

In this tutorial we are going to see one aspect of a current PWA: the offline support.

In my opinion, this is one of the most important features for a progressive web app.
From previous projects, this feature was always on the todo list. Allowing people to keep using a web app if they lose their internet connection.

Our first PWA will use:

  1. A Service Worker to cache the web page’s logic. A Service Worker is similar to a Web Worker, it will silently do the work in the background. In our case, it will cache the data received from the server. If an atomic bomb falls on your remote servers, your minified JavaScript files will stay on the user’s computer and it won’t matter (PWA for the win!)
  2. Firebase to handle the database synchronization
  3. The Firebase offline plugin to keep the data consistent once the disconnection happens

The TODO-firebase Ionic app from this previous tutorial will be used as a base (you should check it because it contains Firebase’s configuration). You can grab the code there.

Only one additional plugin is required. In the terminal:

And the app.module.ts file:

Offline Web Application

We can now activate our Service Worker in the index.html by uncommenting those lines:

If the navigator supports the Service Worker feature, we register the service-worker.js file as a Service Worker.

Here is the content of our Service Worker:

We use Google’s sw-toolbox library.
This toolbox contains properties and methods specific to Service Workers patterns. Just like classic design patterns, Service Workers have their own patterns.

Here are two bad examples:

  1. Don’t cache anything and always ask for the files
  2. Cache everything. Every requests will always give the same results even if the data have been modified by somebody else

Our service-worker.js already has a very good pattern, it’s been created by the Ionic (or Angular) team.

Subscribe to my mailing list to get access to a Free 7-day Ionic 3 introduction email course!
100% Privacy. I'll never spam you!

Firstly, a name is given to a cache.
The key files will be pre-cached, they are all located in the “www” folder:

ionic PWA firebase offline service worker

The last two lines focus on the access pattern:

By default the network is preferred.
If the network is down or a local asset is required, the cache will be used first.

And … that’s it.
Thanks to Google’s technology creating an offline application is very easy!

Let’s handle the Firebase section now.

Offline Database

The previous project used AngularFire Services to handle the data sync.
However, this library is not yet ready for offline usage which is crucial for our progressive web apps.

We already installed the Firebase offline library, all we need to do now is using it in the home.ts file:

Our tasks are now AfoListObservable and the AngularFireOfflineDatabase Service is injected then used to access the list of tasks located on Firebase.

That’s it!
All the methods we created in the previous tutorial stay the same, no need to modify them.

The final step: hosting the PWA on Firebase.

We build our Ionic application:

This command generates production-ready files in the “www” folder.

The firebase commands now:

Once logged in, the init command will create some important files.
We need to show Firebase where the files are located, this is done in the firebase.json file:

Finally we deploy the files:

ionic PWA firebase offline service worker deploy

Unlike other web applications, our app is still available for offline use alongside Firebase’s data which are propagated to other users once we are back online:

ionic PWA firebase offline service worker result

Enter your email address in the box below to get access to this tutorial (and others) source code.


Progressive Web Apps (PWA) are top-notch web applications implementing many useful features.
We have seen in this tutorial how to implement the offline functionality.
Offline applications rely on Service Workers, they are easy to implement thanks to Google’s sw-toolbox library, instead of writing every instructions by hand, we tell the toolbox where the files are and which pattern should be used.
By coupling Service Workers with the Firebase offline library we can create an application that will record our disconnected users’ progress and update the database once they are back online.


  1. Tom Tom
    September 22, 2017    


    thanks for the great tutorial. It will be good to reiterate the issue related to “Module not found: Error: Can’t resolve ‘promise-polyfill’ in …” from the previous tutorial and the fix to it (worked great here when doing ionic build), but also reference to as ionic build –prod yields errors when using angularfire 4.0.0-rc2

    • Matthieu Drula Matthieu Drula
      September 22, 2017    

      Hey Tom.

      I thought about that in the past. In order not to repeat the same thing everywhere, I generally start with a basic tutorial. After that every tutorials start with “you should have a look at the intro there”.
      As for the RC version, I generally use stable versions. When it comes to packages, it can quickly become a nightmare when package A needs package B which needs package C which doesn’t work because one is in alpha, the other is stable …

      • Tom Tom
        September 24, 2017    

        Hi Matthieu,

        Reason for me mentioning is that this tutorial ranks pretty high on google search (good job!, btw) and it didn’t cross my mind to go back to a tutorial at a more basic level to figure out a solution to a problem.

        But I get your point.

        I guess, with the comments section explaining stuff, you get best of both worlds.



  2. Matthieu Drula Matthieu Drula
    September 24, 2017    

    Thanks for the comment.
    I’m linking to the previous tutorials but it might not be visible enough. I’m starting to think about adding an area specifying the previous tutorials to read (something user-friendly, a big blinking box might not do the job).

  3. elisa elisa
    January 4, 2018    

    this is exactly what I’ve done. But I’m always having a cached version of my updated website. any idea why?

  4. Tho Tran Tho Tran
    January 24, 2018    

    Hi Matthieu,

    How can we pre-cache one specific page such as HelpPage or AboutPage? Thanks for your advice

  5. Bruno Bruno
    April 19, 2018    

    I’ve done these steps but offline doesn’t work :/

Leave a Reply

Your email address will not be published. Required fields are marked *