Here I'm going to tell you what nobody is going to tell you from the business and technical standpoint. The opposite side of the PWA word, the myths that might become the dark side of it for you. But first, let's cover what you hear from 99.9% of the agencies and developers, the good points. For those who understand more deeply the technology, I'm covering here PWA Headless which is the most sold solution.
Disclaimer: I prefer PWA, I love the benefits that it provides to customers and merchants. I want to show what agencies and developers won't tell you about the experience working with PWA that they had. Some things will be hidden from you but will impact a lot your business decisions. The best method for anyone to apply PWA is when it wasn't a blind decision.
When you hear about PWA, everyone will share the good points. You might hear it in a such manner, that seems like there no reason why you're not on it now. It's faster, cheaper, prettier and you won't have any problems anymore. The real silver bullet already exists and you're missing out. Ok, ok, telling like this you know it's not true, but when a developer or agency that usually has the more technical experience and shows many examples faster than your current store, then it feels like it's going to solve all the problems.
It's very usual to see as a sales argument numbers like these below.
- 68% increase of mobile traffic
- 15-fold improvement of load and installation speed
- 25-times reduced use of device storage
- 52% average conversion increase
- 78% average session increase
- 137% engagement increase
- 42.86% lower bounce rate when compared to that of mobile websites
- 133.67% increase in page views
Usually when I go deep into the analyses made they aren't reporting the real truth. The words are true, but the intentional feeling looking at it, it's not. We didn't see the entire scenario to have been prepared to make a decision based on someone's words; Most of the time who sell it's hiding the bad points for a reason.
I don't believe into take a decision alone. Without explain to the client and evaluate with them if it makes sense to their business. So, let's cover some of the main points.
PWAs do not require different versions for various devices; a single progressive app meets the requirements of all endpoints on which it operates. It significantly reduces of efforts that developers provide, and as a result, the cost to create a PWA decrease. The cost is three or four times lower than that of a native mobile app.
- If you don't have or you're not planning to have a mobile app soon, it doesn't make sense to consider. The cost of development reduces just when you have to maintain Web / Android / IOS vs PWA.
- If you just have a web store to maintain the maintenance cost is going to increase.
- 50% of your application will be running into another application. It means that if you use a Shopify or Adobe Commerce store (Magento Commerce) and you usually install apps that change something in the frontend, like apps and modules that improve the customer experience as soon as you install them, forget it, a developer most customizes the 50% of your store that's not you Shopify or Magento store anymore, but a PWA technology running in another server. It usually represents more time to implement something and more money invested to customize 100% of those apps that you usually just have to install.
- The new 50% custom part of your project will be in another language, probably Vue, React, or Angular. Probably your devs aren't familiar with these technologies, since they aren't not using them now to develop your store.
Progressive web applications (a.k.a PWA) provide an advanced user experience by combining the look and feel of mobile applications and the best of website performance. They have the design and settings that are very similar to those of native mobile software. Regardless of technologies, tools, and frameworks on which PWAs are developed, they provide the same user experience as native mobile apps do, and it is considered to be superior to that of websites.
At the same time, they have the same speed, responsiveness, and comprehensive capabilities as websites with database access and automatic data. As a result, search engines index them, which is why systems such as Google or Bing can find PWA pages. When compared to mobile software that keeps its internal data only for its own use, the pages of these applications can be found on the internet, which may have a favorable impact on the number of page views.
- There are many PWA capabilities to match the same experience of a mobile app, each PWA solution offers its own possibilities, and it comes to the agency of developer dedicate more time to implement them, 99% of the PWA implementations that I've seen, just implemented the most basic features.
- This is unbelievable but there are companies that sell PWA as Headless then when the project is launched, the project is headless and the experience is not PWA, it doesn't even pass in the Google PWA validation tool.
- If you don't track your KPIs you will have the costs and complexity of headless PWA applications but not the advantages that paid for.
Unlike regular mobile applications, PWAs do not require a long and complex installation process, which significantly improves user experience. Users just download an app, quickly and directly to their devices, and they do not need to go to the App Store or Google Play. It streamlines the procedure and significantly reduces user abandonment. After users have downloaded an app, they can access it via a desktop icon.
Some browsers even offer call-to-action-like teasers that prompt users to download these apps when they visit respective websites. This functionality comes built into browsers and allows the apps to enhance their credibility and reliability. As this software does not require installation on devices, users can easily access the PWA via a URL, which significantly contributes to the high shareability.
- If you just want the basic features of PWA, measure if the agency is overselling a whole new project attached to it.
- Basic PWA features might be achieved in a couple of days of work, but migration from Magento 2 to a Magento 2 headless structure might take a couple of months.
PWAs cache and serve text, images and other content in a specific, efficient manner, which enables them to operate like websites and significantly improves the running speed. Along with quick operation, impeccable performance is another attribute that has an impact on user experience and conversion rates.
Retailers and content providers should adopt this type of software as it enables a more positive user experience than mobile apps by improving retention and customer loyalty.
- There are many projects that migrated to PWA aiming performance, and the final result was a slower Google Page Speed or GTMetrix ranking and even worst SEO.
- The analyses if essential to define the performance KPIs, the styles and static files and pages must be offline, but without consuming time of the first rendering.
- In general, make sure if you have the possibility of spending 500x less time and money doing performance improvements in your current installation that would bring the same performance result to your current performance metric.
Unlike regular applications that are very demanding on operating systems and the technical capabilities of various devices, PWAs work everywhere. A single app can satisfy the needs of various consumers and provide a uniform user experience on different endpoints. At the same time, this type of application enables cross-support to users that switch between their devices by providing them with a continuous experience. Users can access an app that has the same settings and data like that on another device.
This fact also significantly contributes to business automation, as companies that rely on PWAs know that the software their employees use performs seamlessly regardless of the platform or app version. Also, PWAs are highly responsive to various form factors, as they adapt properly to various screen sizes.
- Your store won't be responsive just because you migrate to PWA, it's something that might be in place today.
PWAs have specific functionality that allows them to update automatically, without notifying users and bothering them with permission requests. These apps update themselves every time when users visit them, thus eliminating the need to download batch changes and install them. They just provide a renewed look with no human participation.
However, some of the producers of progressive apps send push notifications to users to inform them about the arrival of a new update. All the same, producers have full control of the information and content, to which users have access.
- If you have an app today you know that it's a huge challenge. Basically, it's the same web experience, you deployed it, it's there for everyone.
- Make sure you have the right "cache" invalidation to different kinds of pages and files. Styles might be saved in the client machine for more time than structural files.
The capability to operate offline or in compromised networks makes PWAs much more convenient than websites. Built-in service workers cache important progressive web apps' features and information automatically, which eliminates the necessity to download it and allows users to access it without an internet connection.
It is based on the saving of information that users previously accessed, for example, pages. If they try to open those that they have not visited online, an app can show a custom offline page. This capability is crucial for retailers, as it allows them to prevent users from abandoning their catalogs and enhances customer retention.
- Make sure you make the offline content be saved in the client's device during the first access. Check if it won't be requested from the server in the subsequent pages.
- Dynamic contents might be loaded via AJAX. All public static content of your store will be saved to everyone but the dynamic content will be distributed differently.
Usually, app distribution services, such as the App Store, Google Play or Microsoft Store, set high requirements to software that is included in their databases. Meeting their requirements may become quite a time- and effort-consuming process. Also, in some cases, services remove applications from databases without notice if a company fails to meet some of the requirements. So, PWAs allow producers to avoid complex reconciliation procedures as they do not need to be stored in similar services.
- You might want to push your PWA app in the Apple and Google App stores, it will help you to achieve a bigger audience.
Like native mobile applications, PWAs have access to device-specific functionality, such as push notifications. This capability can be performed in various ways and allows companies to make the best use of content advertising.
Why are push notifications especially efficient when it comes to PWAs? According to some statistical data, almost 60% of users allow their progressive applications to send them notifications, which significantly increases opportunities to promote products or services. Moreover, these notifications are displayed on the screens of mobile devices, which is why there is a high probability that they attract users' attention, especially when compared to email newsletters, blog entries or posts in social networks.
In such a way, a company can better access its target audience, and chances are, the audience will respond. Another valuable outcome is that these bouncing notifications, along with app icons on device desktops, considerably add to brand recognition, as they allow a business to draw attention to itself. However, users that have numerous applications installed on their mobile devices and that allow a great number of them to send notifications risk making their digital experiences cluttered.
- Most of the time that's a third-party system in the background that is going to handle it for you, have in mind that you might not need a PWA for it.
PWAs rely on HTTPS to provide data safety and minimize the risk of security issues, as this protocol allows to preclude snooping and content tampering. Also, the applications take advantage of Web Bluetooth technology that includes certain security capabilities.
- More security is completely relative, you might have even less security depending on how the structure was made.
- It seems to be 100% guarantee by migrating to PWA but it's not.
I love web development and the power of PWA capabilities, I truly believe that PWA is the future and everyone can take parts of its advantages to improve their customer experience. What I don't like is when someone sells some PWA to merchants without telling the points to consider, it results in frustration, huge cost and the client thinks that PWA is what has been delivered by the agency and not what it really is. An awesome method to improve your customer experience.