Tender Surrender

I came across this article on Twitter yesterday:

Any engineers who say PWA is coming, quit now

"Instagram's PWA is amazing! It's indistinguishable from native!" I heard some Google evangelist or engineer raving about it, so I gave it a try, but it was outdated."

Could this be it?

Instagram PWA is so impressive. I probably won't be able to distinguish it from its native app.
Instagram's PWA is so impressive. I'm not sure I can distinguish it from its native app. pic.twitter.com/DS8TfceBZ6

— Eiji Kitamura / えーじ (@agektmr) January 26, 2018

Admittedly, this statement may have been a bit provocative, but when it comes to Instagram's PWA, the scrolling experience, the ability to apply filters when posting, etc., I honestly thought, "I'm not sure I can tell the difference from a native app," and that was my first impression when I used it, and I still enjoy using it today.

However, at the time of this tweet, I had not yet tried all of the features, and there were some differences that I noticed later. Please don't get me wrong, of course, I am not saying that native apps are unnecessary. In fact, I would like to take this opportunity to explain PWA a little more.

This post is part 12/8 of the Chromium Browser Advent Calendar 2017. It is a translation of the English version posted on Medium recently, with some additions for the Japanese version.

Since the release of the Payment Request API, we've seen a huge amount of interest. However, due to its complexity, there have been some misunderstandings and excitement based on incorrect information. In this article, we'll address some common misconceptions we've seen and provide accurate information.

If you don't know what the Payment Request API is, I recommend you start by reading here.

As explained in our previous article, the Payment Request API has the potential to dramatically change the user experience for web payments. However, many people are wondering whether it will truly become mainstream, and whether they will need to adapt their sites in the future.

I believe there is a very high probability that most payments on the web will be made via Web Payments in the future. In this article, I will explain why.

In my previous post, I discussed ideas for improving web checkout flows by optimizing forms. Today, I'll explore an approach using a new standard API.

The internet has been around for over 20 years, and we've seen a shift from desktop to mobile. Mobile not only caters to smaller screens, but also demands a faster experience, and e-commerce businesses are no exception.

Data shows that 66% of mobile payments are made on the web rather than through native apps. This is likely because it is too much of a hassle to install an app from a search result and then purchase a product, so many people choose to pay directly on the web.

However, there is also data that shows that mobile websites have a 66% lower conversion rate than desktop websites, which means that there is still room for improvement in mobile web conversion rates.

So today, I'd like to introduce two ways to improve your forms to increase your mobile web conversions.