PWA or Native App for eCommerce?
Tags: pwa, vue, magento, ux
Published: 2019-04-10 13:25:59

---
title: PWA or Native App for eCommerce?
published: true
description: https://divante.co/blog/pwas-vs-mobile-apps-ecommerce/
tags: PWA,Vue,Magento,UX
---
Despite differences in approach or design, native apps and Progressive Web Apps allow us to build strong engagement of mobile users, and thus sales. Which one is better for eCommerce?

Let’s look at the most important differences between these two solutions from the business point of view

#User acquisition process#

Native apps need to be downloaded from a dedicated app marketplace. For users already using the mobile website, it is an additional step in the user journey and a distraction. While visiting AppStore or Google Play the user is exposed to apps of other brands. Usually, eCommerce will pay extra to acquire users to their native app, even if the users are already visiting their website on mobile.

PWAs, with a “Add to homescreen” button, can be saved directly from the mobile web page. It lowers user acquisition costs and shortens the process. What’s more, the linkability of PWAs simplifies the sharing of information and favourite products among the users as the product page from a PWA can be copied as a link and used in any browser.

##PWA sites will acquire more users##

Progressive Web Apps are also supported by search engines (look at Google Mobile-First Indexing). In contrast to native apps, PWAs are easy to find and install directly from the browser.

#Costs of production and maintenance#

Native apps are rather expensive to build and maintain. Brands must build separate apps for each and every operating system and then update them regularly. What’s more, it is necessary to pay for access to app marketplaces and use extra promotion on them.

PWAs are built as webpages, and thus the cost of their development is much lower. Updates are done automatically as PWAs are connected to the eCommerce backend. They are independent of operating systems or marketplaces.

#Business model#

Native apps are covered by a marketplace commission of up to 30%. That’s rather high and businesses that are selling physical goods cannot afford it. Marketplaces also take control over the publishing of the app, which makes it difficult to plan new releases or promotions in the store.

PWAs are free of any commission or control. Online stores publish them by themselves and can freely plan diverse promotions and react to market changes in a short time.

#User experience#

Native apps often use a lot of storage on mobile and force users to update frequently. Also, native apps’ installation process takes a while and users must wait before diving into the app. These are high entry points for any new apps on the market. What’s more, as they require separate design for mobile, they lower the conversion rate among omnichannel users who move from one device to another.

#PWA Features#

PWAs are much smaller (Twitters’ PWA is only 0.6 MB in comparison to their 23 MB Android App) thus they are much easier to install. What’s more, installation happens in the background so the user can use the PWA during this process. PWAs have consistent design across all devices and this supports the omnichannel approach.

#PWA vs Native App#


Although native mobile apps offer a wider spectrum of functionalities for the user, Progressive Web Apps present themselves as the new standard for mobile-first solutions. PWAs are a rapidly developing technology and each day we see new engaging features within.

![PWA vs Native Apps](https://divante.co/blog/wp-content/uploads/2018/09/Native-Apps-vs-PWAs.png)


This standard is already used by major eCommerce and social media players which receive most of their traffic from mobile devices. You can ![download our benchmark study of eCommerces already using PWA](https://go.divante.co/top-30-progressive-web-apps/) to see how they implemented PWA and check the results.


If you have some time feel free to [check Open Source PWA Framework Vue Storefront](https://vuestorefront.io) we made.