In a recent webinar, Perfecto CTO Uzi Eilon and I took a look at some of the issues related to PWA testing; we offered a full testing strategy consisting of 6 pillars: Validate PWA Manifest, Validate PWA Service Workers, Validate PWA Specific Capabilities, Properly Test Across Platforms (Responsive Web Design), Object Identification Strategy, Google's PWA Checklist Compliance
PWAs provide a fresh (& lean) start for major brands apps It seems as if development teams have taken the new rebirth/relaunch of PWAs (finally iOS 11.3!!!) as an opportune time to start with a fresh, clean slate. In fact, all 7 apps on our list actually got a jump before iOS/Safari had PWA support and are now well-positioned and realizing real benefits in user experience with their PWAs. What these companies seem to have in common is taking this (PWA) opportunity to use create the lowest bandwidth, friendliest-to-2G, fastest possible performing app without all the feature/code bloat evolution that can happen when you’ve been building off the same codebase for 10 years.
Part I: The Fundamentals A brief history Progressive Web Applications. They’re a hot topic these days, yet it seems like we’ve been hearing about them for years. And we have. In fact, the first high profile mention of the concept came from none other than Steve Jobs at Macworld 2007. “The full Safari engine is inside of iPhone. And so, you can write amazing Web 2.0 and Ajax apps that look exactly and behave exactly like apps on the iPhone. And these apps can integrate perfectly with iPhone services. ”