Mobile Commerce Blog

The latest statistics have confirmed that there are  4.68 billion mobile users  actively surfing and exploring the web. Nearly 3 years ago,  mobile traffic surpassed desktop traffic for the first time  by claiming 51.3% internet users as mobile device users, and the number has been constantly increasing. As much as this term was being floated since the past decade, it is truly now that the Mobile-First’ era has begun.  Therefore, it won’t be surprising to see organizations working to provide better services and experience to mobile users first. However, Google jumped to the mobile bandwagon a couple of years ago when PWA and AMP were introduced. Both PWA and AMP were designed to enhance a user’s web experience while using a mobile device compatible platform. But users often get confused between PWA and AMP. Let’s save you some time and help you understand the difference between PWA and AMP. What is PWA? PWA stands for  Progressive Web App . It is designed to give users the look and fee

Mobile commerce on the rise The growth of smartphone usage has changed the retail landscape and consumer behavior drastically. A large share of online purchases are now taking place on mobile, especially in apps. In 2018, global time spent in app nearly doubled, up 45% from 2016, including a 70% increase in the US. And this trend is only increasing from here: By 2021, mobile transactions are projected to double on a worldwide scale, accounting for 75% of total ecommerce sales. (Data: Global M-Commerce 2018 Report, Researchandmarkets.com) People today have 2x more interaction with brands on mobile more than anywhere else, including desktop, in-store,.. Providing an intimate, direct channel to consumers, mobile has grown into the primary way for consumers to connect with their favorite brands. This represents a massive opportunity for brands to reach, influence and convert shoppers. On the other hand, it also raises the bar of what they expect from your brand. More than ever before, cons

With over 240,000 worldwide merchants, Magento has exploded in popularity in the eCommerce industry. And there’s no doubt that it’s because of its rich features and extensive customization options. A great deal of progressive web applications is released every year. The question is no longer whether a company need to have a web-based version of their software product or enterprise business application but to know how much does it cost to develop a PWA that would meet the company’s business goals in the era of the cloud. In order to help you better, here are some insights on Magento pricing and service. Who are involved in the PWA building process? From the PWA development lifecycle, we can identify the required participants in order to run the project smoothly. They are: The product owner, you as the client will be responsible to validate that the delivered project meets your expectations and needs The project manager: manage the project through its completion, mend the gap between th

In Magento developer community, we see that there is an arising question about how to deploy one's own custom theme based on Venia concept of Magento PWA Studio. Since doing this yourself can be somewhat tricky, we have created a package that helps you do just that in the simplest way possible. In fact, it takes you only 4 simple steps. Let's do it! 1. Clone pwa-studio pwa-studio repository Clone the PWA Studio repository into your development environment. git clone https://github.com/magento-research/pwa-studio/ cd pwa-studio cp packages/venia-concept/.env.dist packages/venia-concept/.env 2. Modify package.json Modify package.json file. You can change "simi-studio" to any name you want. Under "workspaces": "workspaces": [ ... "packages/upward-spec", "packages/simi-studio" ], Under "scripts": "scripts": ... "watch:venia": "yarn workspace @magento/venia-concept run watch; cd - >/dev/

Imagine that you have just launched your start-up and your website looks awesome, but you don’t have enough budget to develop a mobile app, which may be important to your business strategy. However, it is very expensive and a bit risky. You will also have to spend a lot of time building a  native app , but nobody knows your brand well. Will people trust your application​ enough to download it from the App Store or Google Play Store? What’s more – will your customers/readers be determined enough to take some additional steps like closing your website, opening Google Play or the App Store and then patiently wait till the app has installed? Remember that people are much more demanding these days. In other words, they are also very impatient – they expect fast solutions . Downloading such an app from an external store doesn’t sound like a very quick operation and native apps are not very accessible for every user. From the User Experience point of view, there are many obstacles for the cu

This Latest Beta Version Causes Excitement This week, a groan went through the ranks of many developers. New iOS 13 features are poised to change your iPhone software – they were announced by Apple at its WWDC 2019 keynote, and the first iOS 13 beta is available now. Well, things are a little different this year, as iOS 13 for iPad will actually be called iPadOS. Along with much-improved performance, a new Dark Mode and a completely overhauled Maps app, there are some new improvements regarding Progressive Web Apps and it totally made my day. We'll point out the newest changes of PWAs on iOS 13 beta compared to it on the older iOS versions. As we've known, one year after the first initial support for PWAs on iOS, Apple released iOS 12.2 (September 2018) for iPhone and iPads with what it seems to be  the biggest step forward in the last year, addressing the two most annoying problems we’ve been dealing with PWAs : reload effect and OAuth logins. Of course, we'll discuss more