Infrequently Noted

Alex Russell on browsers, standards, and the process of progress.

Comments for What, Exactly, Makes Something A Progressive Web App?


I've been trying to find the best documentation out there to do that App Install Banner notification. Most of them are stating the same things. I am following everything from all these documentations and none of them work. Nice post..

Hey Nino:

Lighthouse is a great way to verify that your site meets the installability criteria: https://github.com/GoogleChrome/lighthouse

Regards

by alex at
Hi,

Great article! Ive been trying to find the best documentation out there to do that App Install Banner notification. Most of them are stating the same things. I am following everything from all these documentations and none of them work. What I am missing?

by Nino Ross Rodriguez at
Nino: are you sure your app and all content is served from an "https" address? Either using "http" or having mixed content warnings is something people often overlook.
by Adam at
Alex, Thanks for pointing out about this extension

https://github.com/GoogleChrome/lighthouse

Sounds great :)

by Julia at
Hi Alex,

Nice post about what makes/doesn't make a PWA. Every business' web app should be progressive, based on the criteria you listed. If your web app isn't loading quickly, mobile-friendly, etc., a business is just hurting itself. Building a PWA takes time, energy, and money, but is invaluable for businesses.

Thanks, Dennis

I think that progressive web apps can be best summarized as the experiences that combine the best of the web and the best of apps. They are useful to users from the very first visit in a browser tab and as the user progressively builds a relationship with the App over time, it becomes more and more powerful. It loads quickly, even on flaky networks, sends relevant push notifications, has an icon on the home screen and loads as top-level, full-screen experience.