Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Learning Progressive Web Apps: Characteristics of PWA Vs Native?

Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

What makes Progressive Web Application PWA ?, some times we can see there are some overlaps between
PWA and Native applications.

Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are two views of what makes a PWA - one of them is essentially Google's which says that to be a PWA, the app must be Reliable, Fast, and Engaging ( I don't agree with this assessment - as I could build a PWA that isn't fast, reliable or engaging.

The other view comes from Jeremy Keith ( and it's the one I agree with. It basically says (and this is all in Chapter 1):

▪ PWAs are installable: mobile and desktop users can quickly install them on their phone’s home screen or desktop using an installation UI provided in the app. Mobile phones have pretty much always had the ability to ‘copy’ a web site’s URL to the device’s home screen, but this is better. I’ll explain more about this in the next chapter.
▪ PWAs cache the app’s core UI on the local device, so when the user opens the app, the UI loads quickly before the app tries to go out and get updated data from the network. PWAs feel snappier than traditional web apps because of this.
▪ PWAs run background tasks, enabling resource caching and background processing. Traditional web apps can’t do this (well, they can, but takes a lot of hand-crafted code or a third-party library).
▪ PWAs can receive push notifications from a backend server regardless of whether the app is running.

The reason you see overlap between PWAs and native applications is because these PWA capabilities listed above are the same capabilities that make native mobile

Rototillers convert rich soil into dirt. Please note that this tiny ad is not a rototiller:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic