A progressive web app (PWA) is a standard introduced by Google that was eagerly approved by Microsoft and reluctantly adopted by Apple. It has gained massive popularity among global leaders in online technologies. Companies such as Pinterest, Uber, Airbnb, Spotify, Aliexpress, OLX, and Forbes, which have already field-tested the abilities of PWA technology to boost user engagement, proved that it’s the best answer to the challenges of the mobile world.
Now, we can say that this technology is here to stay. For the last seven years, PWAs kept answering the needs for faster, leaner, and more rewarding user experience. They provide you with the flexibility to meet the rising expectations of internet users. In a fiercely competitive modern eCommerce environment, PWAs capture the interest of any customer-focused eCommerce professional.
We present to you the second edition of this PWA eBook that was prepared by the digital commerce experts at Cloudflight, formerly Divante. The first edition was a complex guide that served many eCommerce professionals and developers as a reference point. It’s been revised, updated, and redesigned to match the new challenges our industry is facing. Immerse yourself in the world of progressive web applications and the fast, reliable, and engaging user experience they provide.
What is a progressive web app?
A progressive web app is a type of application developed using web technologies such as JavaScript, CSS, and HTML. It closely resembles a regular web page in appearance and behavior. PWAs are easily discoverable in search engine page results and can be shared via links. What sets PWAs apart is their ability to provide functionalities similar to native mobile apps. They can operate offline, deliver push notifications, and leverage device hardware in a manner consistent with native apps.
The definition of a PWA
A progressive web app is a type of web application that can be used as a web page and mobile app on any given device. PWAs are created by fulfilling the majority of requirements listed in this checklist.
It doesn’t sound like a very precise definition of what a PWA is does it? PWAs seem to be a modern fusion between the mobile and desktop worlds, but, since the term doesn’t suggest any particular implementation, it may be challenging to craft a dictionary definition of progressive web apps.
According to Google, the PWA standard is an approach focused on the user experience, but the rest of the progressive web app definition intensifies confusion. When is a website fast and engaging enough to call it a PWA? Is it crucial to install it on the user’s home screen? Or maybe it’s all about an immersive full-screen experience? In short, what exactly makes a web app a progressive web app?
Google, probably deliberately, doesn’t clearly define a PWA. The idea of an open web seems to conflict with a strong standard defined by a central player in the market. The giant can’t allow for the suspicion that PWAs, introduced by the team from Mountain View, force web owners to use Google’s own standards, technologies, or implementation methods. Pointing out a general direction or, better put, a general philosophy to building online touchpoints is a safer choice than forcing a specific method of making them.
Because of this, Google introduced the PWA standard and delivered Lighthouse. Lighthouse is an open-source tool that enables developers to audit a web app for PWA features.
A short history of PWAs
The beginning of PWA history is as early as the year 2000 and the creation of XMLHttpRequest. This technology gave us the chance to retrieve data from a URL without having to do a full page refresh. Five years later, we got AJAX, a technique for creating better, quicker, and more interactive web applications with the help of XML, HTML, CSS, and JavaScript. With AJAX, web applications can send and retrieve data from a server asynchronously in the background without interfering with the display and behavior of the existing page.
The era of native apps
The idea of a PWA wasn’t invented by Google or Apple, but it was Steve Jobs who first presented the concept in front of the world during the introduction of the iPhone in 2007. However, Jobs wanted developers to build apps using standard web technologies to increase the popularity of the iPhone.
The idea of “universal apps” was frozen for almost a decade, and that time belonged to native apps that completely redesigned the way we use the internet. Native apps dominated the mobile network and helped build Google and Apple’s power on mobile. Meanwhile, web owners who wanted to make their data more accessible began to switch to responsive web design (RWD). With this approach, web pages display correctly on a variety of devices and screen sizes by using proportion-based grids and media queries in CSS. The PWA-specific approach had to wait for its moment.
PWAs strike back
In 2015, Frances Berriman and Alex Russell observed a new class of websites that were providing a better user experience than traditional web applications. All of these applications were characterized by one common feature: they gave up browser tabs to live on their own while still maintaining their ubiquity and linkability.
They called this new class of apps “progressive web apps.” A year later, during the Google IO conference, Eric Bidelman, Senior Staff Developers Programs Engineer, introduced progressive web apps as a new standard in web development.
After their official debut, PWAs were perceived as “The Next Big Thing” in the tech world. However, just like it was with the “Year of Mobile,” nothing changed overnight, even after Google and Microsoft forged an alliance to accelerate PWA adoption.
Google and Microsoft have been rivals in the technological arms race for decades, but when it came to the PWA standard, they decided to work side by side. Microsoft’s decision seems especially worth noting. The giant from Redmond was able to take a step back and sacrifice its idea of a Universal Windows Platform to make room for PWAs, a concept introduced by Google.
In 2018, Apple announced their support for PWAs, and that opened the way for its mass adoption.
Basic PWA requirements
Jeremy Keith, in the article wrote:
“If you’re talking to the business people, tell them about the return on investment you get from progressive web apps. If you’re talking to the marketing people, tell them about the experiential benefits of progressive web apps. But if you’re talking to developers, tell them that a progressive web app is a website served over HTTPS with a service worker and manifest file.”
The term “progressive web app” is more of an umbrella definition than the name of a specific technology, but despite that, it’s relatively easy to point out what makes a web app a PWA. To be considered a PWA, websites must meet at least 75% of the requirements from the checklist mentioned before. However, three of them, according to Jeremy Keith’s technical definition, are crucial.
HTTPS
The service worker, a core technology of PWA technology that delivers offline functionality and ultra-fast performance, requires a secure environment to run. Enabling HTTPS on the server is a must-have in creating a PWA. That shouldn’t be a problem since, for some time now, the Chrome browser already marks all websites not using that protocol as insecure. Providing the HTTPS protocol has become commonplace. Most host providers offer easy-to-use in-house tools to switch over to HTTPS. In other cases, the plugin “Let’s encrypt” may be helpful.
A web app manifest
A web app manifest is a simple JSON file filled with all the necessary PWA metadata, like the app name, language, icon, start URL, orientation, scope, theme, color, etc. It tells a browser how to display the app.
PRO TIP: It’s worth verifying whether or not the web app manifest is set up correctly with Lighthouse, which is available in the Chrome DevTools.
An exemplary manifest.json file for a progressive web app:
{
"short_name": "Name",
"name": "NM",
"icons": [
{
"src": "/images/icons-S.png",
"type": "image/png",
"sizes": "192x192"
},
{
"src": "/images/icons-M.png",
"type": "image/png",
"sizes": "512x512"
}
],
"start_url": "/name/?source=pwa",
"display": "standalone",
"theme_color": "#3367D6"
}
Service workers
This core PWA technology is a JavaScript file that runs in the background in the browser and is directly responsible for providing all core features of the PWA, such as push notifications or background synchronization. Developers can use them in many different ways, but, in general, they allow them to control how the browser handles network requests and asset caching.
The web standard used to create service workers is now Google WorkBox. That set of libraries and Node modules enables developers to wrap the boilerplate code with methods that they can use to implement service workers. WorkBox is a well-defined and easy-to-use tool to apply various caching strategies, like, for example, precaching, runtime caching strategies, and offline support. By using it, it’s possible to create a well-functioning PWA with less code and a lower risk of errors.
Features of progressive web apps
Progressive web apps became a hot topic in the media. However, media coverage is often a little bit shallow and focused on finding simple answers, like are PWA capabilities better or worse than those of native apps, for example. Meanwhile, we shouldn’t just compare progressive web apps’ features to their native app competitors. They can bring benefits even to a company that already has an app. They’re cross-platform, and dividing the shopping experience into a variety of platforms is less and less effective in the omnichannel era.
It’s evident that not every user is keen to install or use a native app. They may, however, still drop by the website from time to time. So, providing the best possible user experience on the web should be a goal in and of itself. PWA features, which combine the reach of the web and the user experience of a native app, allow you to do just that.
The core features of a PWA
Capability of offline work
Progressive web apps are not only ultra-fast apps. They can also continue to work even when the user is offline or has an unreliable or slow internet connection. Service workers, the technology responsible for that feature, allow the app to store things offline and flexibly manage network requests to retrieve them from the local cache. It leads straight to another benefit which is minimizing the amount of data we need to use to run the app.
Discoverability and easy installation
One of the most important PWA functionalities is its discoverability. A PWA, since it’s a website with some extras, can be found through regular search engines, like Google or Bing. There’s no need to dig through the piles of apps popping up every day in the sea of apps on the app stores. A PWA’s installation is a piece of cake: it happens in the background during the first visit.
Using device features
PWAs have a lot of functionalities to access device features on Android and a few less on iOS. The usage of a camera, GPS, or fingerprint scanner in an app-like way enriches the user’s experience.
Automatic updates
Launching a new version of a mobile app can be a nightmare for publishers. With a PWA, there’s no need to wait for Apple’s or Google’s acceptance to have users’ download the update. All we have to do is upload new files to our server. PWA features allow publishers to implement patches immediately, for example. It enables them to keep full control of the content. Customers always use the most current version of the application.
Safety
By using the HTTPS protocol, the data we transmit is encrypted, so it’s more difficult to intercept and change. Users also perceive HTTPS as a guarantee of the safety and reliability of publishers, and Google provides additional points in the search ranking for using it.
App-like experience
The whole idea behind PWAs is finding a way to connect the best possible experience, an app-like one, with the open nature of the web.
From a user perspective, the differences between PWA features and native apps can be barely noticeable, excluding the way of downloading. However, the methods of building, launching, updating, and sharing PWAs are entirely different from native apps.
Cost-effective development of PWAs
While talking about PWA features, we have to mention how cost-effective this technology is. Clutter in the app stores, a dangerous dependence on giants like Google and Apple, and fees have already pushed developers to look for an alternative to native solutions. Products like Windows Hosted Apps and Electron were the first trials to use web technologies to create apps that could exist outside the browser.
Progressive web apps, until now, have seemed to be the closest to reaching the primary goal of these efforts.
It wouldn’t be an exaggeration to say that progressive web apps prove the power of modern web standards. They use pure HTML, CSS, and JavaScript but in a way that no one could have imagined a couple of years ago.
The native-like approach is an entirely different story. Native apps are built with code used exclusively for the device and its OS. Developers write iOS applications in Objective-C or Swift, and Android apps are created in Java. Long story short, they require more niche skills, which increases their time and cost of development.
“PWAs escaped from the browser’s tabs to live as their apps but retained the ubiquity and linkability that make the web what it is.”
in “Progressive web apps”
PWAs are easy to launch
According to BusinessDIT, 93% of online users begin their online experience with a search engine. That’s where PWA features come in handy. They allow for omitting middlemen like AppStore and Google Play and reach users directly through an internet browser.
Mobile-first indexing has been the norm for over three years now, and PWAs are one of the best ways of embracing the mobile-first approach to design online services. Mobile users expect fast and seamless interactions with content that they can tap or swipe. Social media, like Twitter, Instagram, Facebook, and WeChat, have already embraced those needs and serve mobile-first experiences to users with PWA functionalities. Now their mobile entities, apps, and mobile websites are more engaging than desktop ones, and users are also more likely to click through. For instance, the introduction of Twitter’s PWA, Twitter Lite, increased the number of Tweets by a whopping 75%, and the average pages by session by 65%.
Mobile-first indexing means Google predominantly uses the mobile version of a page’s content for indexing and ranking. Historically, the index primarily used the desktop version of a page’s content when evaluating the relevance of the page to the user’s query.
Omitting the app stores is, however, the source of many more advantages:
Avoiding app store fees
Distributing apps through major mobile app stores is connected with the necessity of paying various registration fees. Google and Apple also keep a hefty percentage of any purchase made by the user, which leads to a considerable decrease in the developer’s profit.
Avoiding the censorship of app stores
Apple reviews every app in the App Store. The process is extensive, long, and drawn out, and the results are often disappointing and unpredictable.
Avoiding app clutter
The average number of new apps per day is 2,477. A PWA available directly from Google Search is a way of avoiding that crowd.
Instant updates are one of the most important features of PWAs
In app stores, update deployment takes time. Every update must be uploaded to a platform and then goes through a review process. It may be tricky, especially in the case of Apple, even though, in general, it’s clear what requirements must be met. The app has to be bug-free, links within it must be functional, and it has to contain accurate screenshots. Yet, in the details, there’s a grey area
“If your app doesn’t offer much functionality or content, or only applies to a small niche market, it may not be approved. Before creating your app, take a look at the apps in your category on the App Store and consider how you can provide an even better user experience.” App Store Guidelines
Since Apple relies on manual labor in the review process, the decision about good, better, and the best user experience may be highly discretionary.
Last year, Apple rejected 27% of submitted apps, according to the company’s Transparency Report. Apple emphasizes that many of them are approved after minor changes, but “others present a more difficult decision for App Review.” What to do if the application is rejected? Well, there’s a way out, but in Franz Kafka’s “The Trial” style. Developers can appeal the decision made by App Review to a board called the App Review Board, which has the right to change the decision or sustain it.
Sustained appeals can bring an app in front of the Executive Review Board. Apple calls the developer to find out the developer’s reason for wanting to overturn the decision, and, as the company says, reviewers make thousands of such calls every week.
When you leverage PWA capabilities, on the other hand, everything happens instantly. The updates, deployed to a server, are available to users almost in real time. And that’s it. No stress, no worries.
Sharing progressive web apps
Around 90% of a PWA is purely JavaScript, but the distribution model is the web. For that, organic search is vital. PWAs are optimizable according to Google SEO Guidelines.
PWA distribution, with its web-like linkability, is way more comfortable, faster, and more accessible than going through the app stores. They’re not attached to any particular platform, operating system, or app store. If the user wants, they can save it with one tap on their home screen directly from the browser and share it via URL.
Adding a PWA to the home screen
With PWA capabilities, users don’t need a typical installation but can directly add them to the home screen on a mobile phone or desktop computer. The first time the user visits the site, the service worker is installed behind the scenes. This enables developers to provide offline PWA functionality, send push notifications, and display a home screen banner.
“Add to home screen” is a feature that uses the information from the web manifest to serve the app on the home screen with an icon and name. It displays a banner indicating that it’s possible to install the app as a PWA.
In theory, if the user accepts the prompt, the PWA is added to the home screen and runs like any other installed app. In practice, however, the ways users can install the PWA differ depending on which browser or OS they use. Chrome and Opera display banner prompts, which are similar to requests for permission to access a person’s location. Firefox and Samsung show more subtle badges that inform the users that the website is installable. The main goal remains the same: the user can pin the PWA to their home screen and use it like a native app.
Benefits of progressive web apps
PWA benefits for users
“Don’t Make Me Think” is a book written by Steve Krug, a guru of usability, two decades ago. In terms of UX, that principle hasn’t changed a bit. Digital users hate when they’re forced to overcome obstacles in their path and will sooner give up than spend even a minute waiting on a page to fully load. Mobile users, since they often use smartphones on the run with a poor network connection or an expensive data plan, are the most impatient. But since their number is growing, especially in emerging markets like Asia and Africa, they have to have their expectations met.
Progressive web apps, a fusion between the features of web pages and mobile apps, are one of the best ways to do that. The most significant advantages of a PWA are its speed, the ability to work offline, and accessibility directly from the browser. People can add them to the home screen of their mobile device like a typical native app, skipping app marketplaces and saving valuable storage, especially on low-end devices. Users are now more likely to give a PWA a chance since, in the last few years, they have become quite reluctant to download new apps.
They treat their mobile devices like cameras, computers, notepads, assistants, and, most importantly, as a treasury of memories. If downloading an app means that they have to sacrifice precious photos or messages, they think three times before clicking “yes.”
Progressive web apps don’t force users to make such difficult choices because they’re much lighter than native apps. Also, users don’t see the typical installation process. They click on a dedicated button and a shortcut is created on their home screen. Of course, with downloaded content, PWAs also “steal” some space, but it’s still far less than a native app.
Long story short, progressive web apps have come about at just the right time. This is a time when mobile user behavior has become more demanding, and discovering, downloading, and using a PWA is as simple as it can be.
PWA benefits for businesses
- A progressive web app is easy to update. This process may take more time and effort on a traditional app marketplace.
- Thanks to these easy updates, home screen access, and notification features, having a PWA means that communication between a business and its customers will be smooth and effective.
- A PWA, by providing superb UX, increases visitors’ engagement and conversion rates.
With fast loading times, a PWA reduces server load and minimizes the danger of a crash or slowdown during periods of intense traffic, like Black Friday. Convincing users to install a PWA locally is priceless because it can be used as a communication hub with clients. It can reduce both the financial effort of cooperation and the risk of consumer data leakage or cyber fraud by avoiding third parties.
The usual problem is that, as we mentioned before, customers might appreciate an app’s UX but are no longer willing to download them in large numbers. By now, every smartphone user has probably established their favorite set of apps and, when it comes to downloading newer applications, is most likely very picky. This doesn’t mean that the number of downloaded apps is decreasing. The number of quarterly app downloads has stayed more or less the same since early 2020, but the number of smartphone users keeps growing. So, the average user downloads fewer and fewer apps.
App abandonment is also a big problem for the market. According to Appsflyer’s data, only 22% of Android and 25% of iOS users return to a new app the next day after downloading it. One month after the download, those figures fall to a minuscule 2% for Android and 4% for iOS.
One of the advantages of a PWA is the fact that convincing clients to install a PWA directly from a browser seems to be much simpler than forcing them to go through the app store. Avoiding dependency on Apple and Google is a blessing for marketers who aren’t aware of when, or even if, their app will be published or updated in app stores. They also don’t have to pay any middleman for distribution, which makes the customer acquisition cost (CAC) much lower.
We can clearly spot a couple of benefits of progressive web apps for business. A progressive web app creates an opportunity to use a shopping-like impulse. When the user sees exciting content during their digital journey, they may be more open to making a snap decision and pinning the app to their home screen. This works in much the same way as the various chocolates and snacks placed near the checkout in the supermarket.
Another PWA advantage is how lean it is. With its small size and fast installation process, it gives marketers a bigger chance of successful user onboarding from the website to the app. In the end, this leads to increasing marketing ROI and decreasing the cost of development at the same time. This cost reduction is achieved because using a PWA means having only one website that is used as a regular website on desktop, a mobile website on smartphones and tablets, and as a multi-platform app. There’s no need to build, test, and deploy a desktop website with RWD, an Android app, and an iOS app all at the same time.
In the era of omnichannel, this is crucial. PWA technology enables brands to unify and streamline their clients’ experience across all touchpoints with lower costs. Customers are willing to reward them with loyalty, especially since marketers can add native-app functionalities to PWAs like an “install the app” pop-up, a home screen icon for the app, and push notifications. A PWA’s tools help to re-engage clients, make them more aware of the brand, and allow for analyzing their preferences just like native apps.
Benefits of PWAs for businesses:
- No middleman involved in the app download and installation.
- Independence in the app update process.
- An undisturbed digital journey even with weak or nonexistent connectivity.
- A short loading time even in traffic peaks.
- Higher user engagement and conversion rates.
- Support in search results thanks to the mobile-first approach.
- Seamless onboarding from social channels.
- Higher marketing ROI.
- Decreased CAC.
- Increased cross-platform conversion.
- All-in-one processes of development, updates, and product information.
PWA benefits for developers
For developers, one of the biggest benefits of progressive web apps seems to be the fact that they’re based on common web standards, like JavaScript, CSS, and HTML. Compared to native apps, they’re easy to build. In not very sophisticated projects, it’s true: a PWA can be built from scratch by an internal team of front-end developers relatively easily.
However, in the case of more complicated sites, stores, or marketplaces, it could be tricky. When a company has plenty of different systems that are linked with one another very tightly, any changes, PWAs included, need to be made with extra caution. That’s the “dirty work” that rests on the shoulders of the techies. They must find a way to implement the marketers’ idea about seamless UX and make sure everything works. It’s an issue in most eCommerce platforms often due to old, outdated technology stacks.
However, with microservices and headless architecture, it’s a breeze. The newest PWA frameworks and ready-to-use solutions enable developers to turn a site into a PWA to reap the benefits of progressive web apps without any interference with the eCommerce engine. They can separate the front end from the platform’s back end while supporting sales and marketing teams with a new, agile way of doing UX.
We built Vue Storefront for that purpose. It helps developers build strong front-end and JavaScript competencies and gain experience valuable in more than just eCommerce projects. They also don’t have to wait an eternity to see the effects of their efforts. The time to market of products based on PWA frameworks is about several months, but it takes just 160 working hours to test out a full-featured Vue Storefront proof of concept for an eCommerce PWA.
Benefits of PWAs for developers:
-
- A modern approach to development.
- A positive experience for developers.
- The possibility to work with headless architecture.
- No need for separate app development for iOS and Android OS.
- No need for paid developer accounts on App Store or Google Play.
- A short time to market.
- The independence of the back end with PWA platform-agnostic solutions.
Progressive web apps vs. native apps vs. hybrid apps
PWAs and native apps aren’t the only way to create a smooth cross-platform user experience. With tools like React Native, Native Scripts, Flutter, or Ionic, there’s a third way: hybrid apps, also called cross-platform apps.
Native apps vs. hybrid apps
Modern frameworks allow for building apps that provide almost-native performance but without the necessity of writing three different code bases. This is what we call a hybrid app. Developers write the application once, and it’s available on three operating systems. For native apps, there is a need to use Objective-C (iOS), Java (Android), and, in the past, C# (Windows Phone). The cross-platform approach is less time-consuming, and the costs of writing a hybrid are incomparably lower.
A well-written and optimized cross-platform app should not differ from a native application, but in more complex projects, like games or expanded programs, it may be visibly slower or even suffer from serious lag. It’s also difficult to support Android-specific or iPhone-specific functionalities with hybrids.
Hybrid apps can be a reasonable choice, especially when the project is relatively modest and the budget limited. Otherwise, a native app will be a better option. They’re written in languages specific to Android and iOS, which guarantee the best possible performance and compatibility with a smartphone’s functionalities. Unfortunately, it also means that development takes more time and money and that the app is a lot harder to distribute and update.
Progressive web apps vs. native and hybrid apps
PWAs are still trending in the IT world, and there’s a good chance that they will soon replace native and hybrid apps. They are incredibly fast, in contrast to hybrid apps, and they use a single code base between platforms, unlike native apps.
Another notable advantage of progressive web apps is the significantly lower cost of development and the shorter time to market. But the list of PWA benefits doesn’t end there. If you want to learn more, jump to the “Benefits of progressive web apps” chapter of this eBook.
PWA statistics and implementation results
PWA eCommerce is ranked 21st in the eCommerce Trend Radar list of trends. In over seven years on the market, progressive web apps have repeatedly proven that they deliver a tangible efficiency boost and better business results. Here are a couple of case studies that track PWA statistics and monitor site performance after implementing PWA technology.
- Kubota launched their eCommerce PWA which resulted in a 192% growth in daily visitors and 26% growth in average monthly visits.
- Implementing PWA in Yope increased the conversion rate by 70% and decreased the time to first byte by 1100%.
- The Starbucks PWA has doubled the number of their daily active users.
- Deploying PWA at Lancôme made their website 50% faster than the previous one, and Lancôme’s mobile sales have increased by 16% year over year.
- With a PWA, the page-load performance of the Housing.com site increased by over 30%, and the average time-per-session increased by 10% across all browsers.
- Time spent on the Pinterest PWA site is up by 40% compared to the old mobile web experience, user-generated ad revenue is up 44%, and core engagements are up 60%.
- In a short time, the DW Shop achieved 75% of its traffic from Instagram with the use of PWA technology.
PWA examples
Progressive web apps were implemented by companies like Pinterest, Uber, Airbnb, Spotify, and Aliexpress, but here we’ll share with you some more relatable PWA examples. These are the progressive web app examples we had hands-on experience with, and we can vouch for the numbers mentioned in the case studies.
Staples
Staples is the second largest eCommerce retailer in the world, right behind Amazon.com. Over the years, this company grew both organically and by the acquisition of other eCommerce entities while still continuing to provide online services. At some point, Staples had to unify the user experience across all touchpoints to provide a consistent brand identity.
It wasn’t an easy task since Staples’ online services were based on multiple, highly customized systems written in .NET and Java. Changing all of them would be time-consuming and demanding, so the eCommerce team decided to build a unified user interface (UI) for two back ends available in the Staples technology stack.
The company considered the development of a native mobile app, a new front end, and various headless solutions. However, it eventually became clear that a progressive web app was the best option.
The idea was to implement the new PWA front end and integrate it via API with Genesis and Netshope-based back ends. The final product delivered features like barcode scanning and offline ordering, which enabled Staples to improve the overall user experience of mobile users and, at the same time, make it more consistent.
Yope
Yope is a well-known Polish brand that specializes in producing beauty and cleaning products that are natural, eco-friendly, and vegan. They decided to embrace PWA technology to enhance their online presence and provide an exceptional shopping experience. The goal was to develop a new version of their eCommerce platform that would incorporate cutting-edge features and captivate their customers with a visually appealing design.
Yope now boasts a user-friendly PWA online store that promotes the digitalization of their business, ensures the satisfaction of their customers, and facilitates revenue growth. This strategic investment in their future has yielded remarkable results, with an impressive 70% increase in overall conversion rate. The desktop conversion rate soared by 83% while the mobile conversion rate experienced a substantial growth of 64%.
Mirka
