WHAT IS PWA Website Top 5 things to know about Progressive Web Apps

Published by Science Hub on

Progressive Web Apps

PWA Full Form > Progressive Web Apps 


A progressive web application (PWA) is a type of application software delivered through the web, built using common web technologies including HTML, CSS and JavaScript. It intends to work on any platform that uses a standards-compliant browser, including both desktop and mobile devices.

While web applications have been available for mobile devices since the beginning, they have generally been slower, have fewer features, and fewer native applications. PWA reduces the gap between user experience in web-based and native applications, features include.


  • Ability to run offline
  • High performance
  • Background processing in service workers in a separate thread
  • Access to the phone’s sensors
  • Support for push notifications
  • An icon on the phone‘s home screen

Progressive web apps (PWA) are increasing and hence the demand for PWA developers. This article is an introduction to PWA and talks about the benefits of PWA and PWA over traditional web and mobile apps.

The number of web and cloud apps is increasing every day. Today, there are 2 billion websites in the world and 400 million of them are active. Mobile apps are growing even faster. There are around 4.2 billion mobile apps in the world consumed by 4 billion mobile internet users. If you look at the global mobile app market, it is occupied by two companies.

Progressive Web Apps

The web server is served and web pages are served through a web browser.

  1. Internet connectivity is required.
  2. Runs within the Visible range of a browser.
  3. Does not support notifications.
  4. There is limited access to device resources.
  5. The performance of a web application may deteriorate on a slow Internet connection.  

They’re more of an idea than a thing.

The term was introduced by Google’s Alex Russell in 2015 to apply to app-like web technologies. There’s no single standard for a PWA, but there are some agreed upon things they need.

PWAs need a manifest. 

This is a JSON file that defines things about the look–like the name of the app, the icon for the home screen, background colors, and whether to show the browser UI or take over full screen.

PWAs need to work offline. 

This is usually achieved by locally saving JavaScript and CSS for faster load time, though some PWAs save almost everything the app does.

They need something called service workers. 

Service workers create a layer between the app and the network. They cache new content, synchronize local changes with a remote server, and enables notifications and fast loading.

PWAs need security. 

These may sound obvious, but it’s worth emphasizing–you should not skip security. PWAs should use HTTPS when it does send data.

Progressive Web Apps

Top 10 Build Progressive Web Apps

  1. Introduction to PWA
  2. When should you use a PWA
  3. PWA development cycle
  4. Make a static website work offline
  5. Installing a PWA on the home screen
  6. Introduction to Service Worker
  7. Intro to Promises
  8. Using the Fetch API
  9. Advanced Promises
  10. Debugging Service Workers in Chrome

There are other things you may not use for your PWA such as WebAssembly, Houdini, or WebRTC, but it provides you with the basics. There are more and more progressive web apps out there (like the Amazon Luna mentioned earlier), but Twitter, Flipkart and Pinterest also have PWA versions, Be progressive – try a web app.