Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Progressive Web Apps, a year later

Progressive Web Apps, a year later

Analysis of the impact, adoption and maturity of PWAs once year after they were announced. The slides for my talk at ISELTech17 Lisbon.

More Decks by Enrique García Navalón

Other Decks in Technology


  1. What is this talk about? 1. Review of what are

    PWAs 2. Status update on technologies 3. Analysis on the impact so far 4. Conclusions and predictions
  2. The quick and dirty PWA timeline The past The future

    Google announces PWAs at I/O 16 Hype begins, bazillion example PWAs appear Twitter announces mobile site is a React PWA Many real-world PWAs start to go live Google news at I/O 17 may february may
  3. The quest for the sweet spot between app and web

  4. The holy trinity 1. Reliable 2. Fast 3. Engaging •

    Lightweight and fast-loading • Installation through app manifest • Offline caching through service workers • Notification using Web Push and service workers • Top performance through good ol’ coding
  5. New, not sexy but useful stuff from I/O 2017 •

    215 (!!!) new general web APIs since I/O 2016 • AMP + PWA = PWAMP • Lighthouse integrated with chrome devtools
  6. Is not only a Google thing, it’s an open web

    thing 1. Frameworks and tooling in react, angular, vue, polymer, etc. 2. Service worker libraries for offline first support 3. Ionic framework support, PWAs are packageable using Cordova
  7. Microsoft is slowly hopping on too • Packaged as Windows

    Store apps sandboxed in Appx containers • PWAs could function as UWP apps • Edge will have full support by fall 2017
  8. Case study: Twitter • 1M visits from home screen •

    75% increase in tweets • 70% data savings (in Data Saver mode) • <1MB (!!!) mobile.twitter.com
  9. Case study: OLA • Reach tier 2 and tier 3

    cities with low-end smartphones and bad connection • First load in under 3 seconds in the worst network • Repeat loads in under 1 second • <0.5MB (!!!) www.olacabs.com
  10. Conclusions 1. PWAs are not the final solution, but are

    here to stay 2. PWAs outperform native apps in size, load times and data consumption 3. Not all features are cross-platform, hardware access and security are an issue 4. Trend is clear: Google as distribution hub and kill competition stores
  11. My predictions 1. PWAs will slowly replace “one time apps”

    and other simple apps 2. Twitter style, PWAs will coexists with native app version until we get closer to the unicorn 3. Apple is going to announce full PWA support in 2018 4. Keep Web Assembly in the radar… (2019+)