While PWA technology has been mentioned in previous articles on our blog, we've decided it deserves more attention. We're confident that delving into the history of PWAs will be intriguing for our readers. After all, understanding history helps anticipate the future, revealing the path, challenges, and transformations that have shaped PWAs into what they are today.
PWA History
Early 2000s - Mid-2000s
The beginning of Progressive Web Apps (PWAs) can be traced back to the early 2000s with the emergence of XMLHttpRequest, a technology that allowed fetching data from URLs without needing a complete page reload.
Fast forward five years, the introduction of AJAX marked a significant breakthrough, changing web technologies by using XML, HTML, CSS, and JavaScript to make them work better, faster, and more interactive. AJAX empowered web applications to interact with servers asynchronously in the background, seamlessly improving the user's browsing experience.
Steve Jobs and the First iPhone Presentation
Steve Jobs was the first to introduce the concept of PWAs during the first iPhone presentation . He envisioned applications seamlessly integrated with iPhone services, distributed via the internet, easily updatable without complicated processes, and as secure as banking systems, all developed using web standards like Web 2.0 and AJAX.
Shift in Focus
However, the initial excitement for Web Apps decreased as the focus shifted towards increasing the iPhone's popularity. Within a short span of four months, Apple changed direction, announcing an SDK aimed at making it easier to develop higher-performing native iOS apps.
2000s to 2010s
For nearly a decade, the idea of "universal apps" remained unchanged, overshadowed by the dominance of native applications. This period witnessed a significant shift in internet usage dynamics, with native apps reshaping the mobile landscape and solidifying the influence of tech giants like Google and Apple. Meanwhile, website owners, aiming for better accessibility, turned to responsive web design (RWD). RWD ensured optimal presentation across many devices and screen sizes using proportion-based grids and CSS media queries.
2015 - 2016
In 2015, Frances Berriman and Alex Russell noticed a new category of websites providing a superior user experience compared to traditional web applications. These sites shared a common trait: they operated independently of browser tabs while maintaining their versatility and appeal.
They later coined the term "Progressive Web Apps" in an article advocating for a paradigm shift in web development tools and understanding. This concept, essentially a modernized version of Apple's idea, gained significant traction with the robust backing of Google, who vigorously promoted PWA development. What distinguished these apps was their ability to function independently from browser tabs while remaining universally accessible and easily linkable.
A year later, during the Google IO conference , Eric Bidelman, a Senior Staff Developers Programs Engineer, introduced Progressive Web Apps as a groundbreaking standard in web development. Following their official introduction, PWAs were hailed as "The Next Big Thing" in the tech realm.
Google and Microsoft's Collaboration
However, similar to the "Year of Mobile," widespread adoption didn't happen overnight, even after Google and Microsoft joined forces to expedite PWA adoption.
Despite being longstanding rivals in the tech industry, Google and Microsoft collaborated closely on the PWA standard. Notably, Microsoft made the significant move of relinquishing its Universal Windows Platform concept to embrace PWAs, a concept promoted by Google.
Apple's Complex Relationship with Web Apps
In 2018, Apple's announcement of support for PWAs opened the way for their widespread adoption.
Following this, Apple attempted to balance profitability with user satisfaction by navigating the rise of Progressive Web Apps (PWAs). However, as PWAs gained popularity, Apple introduced restrictions on certain features. In February, Apple announced its decision to remove support for Home Screen web apps in iOS 17.4 within the EU, citing compliance with the Digital Markets Act (DMA) and concerns about security and privacy.
In other words, while Apple was required to support third-party browser engines, they aimed to prevent PWAs from utilizing non-WebKit engines, to have control over and don't lose native app's users over PWAs. So, they decided to remove support for Home Screen web apps to limit.
Apple's U-Turn
However, this decision sparked significant deliberation and feedback, leading to backlash from developers. The non-profit group Open Web Advocacy spearheaded an open letter addressed to Apple CEO Tim Cook, urging a reversal. By Friday, the letter had garnered nearly 5,000 signatures.
Apple had argued that the removal was necessary for compliance with the Act, citing security concerns with non-Safari browsers. However, ultimately, Apple chose to retain the existing Home Screen web apps capability in the EU. The EU had given Apple a deadline of March 7 to align its practices with the new law.
Besides, the EC clarified that blocking these apps was unnecessary for DMA compliance, particularly highlighting at-risk applications for public schools, hospitals, and transport systems. The European Commission positively acknowledged Apple's reversal, citing over 500 complaints about the initial decision. They clarified that removing Home Screen Web Apps was unnecessary under the Digital Markets Act, contrary to Apple's claims.
So, Apple gave up in this round. Once critical of Apple's initial decision, advocacy groups, developers, and average users now applaud the reversal, highlighting its significance in preserving a competitive and open ecosystem.