What Makes a PWA a PWA?

Jillian MacNulty Picture

by Jillian MacNulty | Last Updated: Sep 12, 2017

Last week Google announced the schedule for this year’s Chrome Dev Summit. The Lumavate office was abuzz, because the 2015 Dev Summit was where Google introduced the concept for Progressive Web Apps (PWAs). Much to our excitement, we scrolled through the schedule and saw that the majority of this year’s sessions are PWA-centric! It’s technology that Google is moving full-speed ahead with, which is why we want to dive into a few high-level PWA concepts for you in the coming weeks. We’ve already put together a handy infographic that serves as your crash course to PWAs, but let’s dive a little deeper and talk about the technical elements that differentiate a PWA from any other native mobile app. Technical Requirements Although the list of technical requirements found in the Google PWA checklist is lengthy, these four elements take care of the bulk of the functionality: UX Outcomes Here’s the real reason we’re convinced that PWAs are the future of mobile; With a compliant PWA comes a beautiful, frictionless user experience. A fully PWA-compliant mobile experience meets these three UX standards: The good news? If your PWA has properly implemented each of the technical elements listed above, then these UX outcomes are inherent. Once you nail down the technical elements, your users are guaranteed a reliable, fast, and engaging mobile experience that will keep them coming back time and time again. In a few weeks we’ll be revisiting the topic of PWAs with a deeper dive into those three UX outcomes, so stay tuned to the Lumavate Blog!

See Lumavate in Action

Meet with one of our experts to see how easy it is to centralize your product data, manage digital assets, and create digital product experiences. Trust us…you’re going to be wowed.