I think the web platform is awesome.
Moreover, it got some impressive APIs that make it even more powerful. The web platform is easy to access (very low friction), no installs, easy distribution (without walled gardens), immediate redeployments and no single organization own it. Let’s see what do we mean when we are talking on progressive web apps.
Progressive Web Apps
- Fast loading – Because we know users love speed and for every delay we are lossing a smile (and a user).
- One click away from accessing content – You should have an icon on the screen and with one click you could get to your content (or task) and smile.
- Smooth animations and navigations – Good UX comes with these aspects.
- Re-engages with push notifications – In many cases, we wish to be able to notify users even when the browser is not open in-front of them. We can!
- Good experience on flaky network connections – Our web app is offline first, so we can deliver our content (just the deltas) on flaky networks much better/faster.
- Consistent experience across browsers – After all, we are talking on the web here. You can’t control from which device users will come to your work. So make sure, you serve them all.
PWAs are about the experience, no the tech: these apps _feel_ better and more app-like. The technology behind Progressive Web Apps is called “Service Worker”; it’s available only since mid 2015 and is seeing large, growing adoption. PWA is expected to be for mobile what AJAX meant for the desktop web.
Enabling app-like capabilities
At the foundational level, there are two core pieces of technology that enable PWAs: Continue reading