DEV Community ๐Ÿ‘ฉโ€๐Ÿ’ป๐Ÿ‘จโ€๐Ÿ’ป

Tom Karwatka
Tom Karwatka

Posted on

PWA or Native App for eCommerce?

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

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 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 we made.

Top comments (4)

Collapse
 
ehutch79 profile image
Eric Hutchinson

I can say as a user, I REALLY don't like stores that try to push me to use a mobile app if i visit them on my phone. It tends to make me bounce fromt the site, let alone not buy the thing i clicked on the ad for.

I'm also very unlikely to do the 'add to homescreen' for any ecommerce site, especially random tshirt stores or whatnot. Also, be really carefull about adding other features like notifications and location services with your pwa, if all you're doing is selling 5 products.

I've clicked on a bunch of ads on facebook, only to go from 'take my money!' to 'why do i need to sign up for a newsletter to see a price?'

Please be careful your user engagement is not preventing people from giving you money!

Collapse
 
tomik99 profile image
Tom Karwatka

Agree! First thing is to offer value to the user. PWA is just a tool.

Web Push Notifs are the most overused feature now :(

Collapse
 
chchrist profile image
Tolis Christomanos

PWAs are getting there but are not mature enough especially on Safari iOS.
This is a good article that explains the problems.
medium.com/@firt/whats-new-on-ios-...

An Animated Guide to Node.js Event Lop

Node.js doesnโ€™t stop from running other operations because of Libuv, a C++ library responsible for the event loop and asynchronously handling tasks such as network requests, DNS resolution, file system operations, data encryption, etc.

What happens under the hood when Node.js works on tasks such as database queries? We will explore it by following this piece of code step by step.