Progressive web Applications (PWA) have been around for a while now, but only now are they starting to see real traction in eCommerce. As always, with technology getting traction, the bandwagon starts to roll. Many decide to jump and cling on even if they don’t understand what a PWA is or think they can get away with it. What makes it worse is that a PWA is not an actual specified technical architecture or framework, just a set of principles/characterises that an App/website should demonstrate.
After a fair amount of research, I came up with a way of describing when something is a PWA and a high-level set of architecture enablers for building a PWA.

Find out the key differences and understand each term’s key concepts. See more of my articles on LinkedIn
  / jjwilliams  

Most of what I have learned in the MACH / headless architecture world has been while building Amplience headless cms, DAM, and dynamic media services. Take a look at the Amplience Website and see a MACH platform in action
https://amplience.com

00:00 introduction to what is a PWA
01:14 PWA description
02:15 PWA characteristics - What makes a PWA a PWA
03:49 PWA architecture enablers