Tender Surrender

In my previous post, I wrote about ideas for improving the web checkout flow by optimizing forms. This time, I'll discuss an approach using a new standard API.

More than twenty years have passed since the dawn of the internet, and the era has shifted from desktop to mobile. On mobile, users don't just expect adaptations for smaller screens—they demand a much faster, smoother experience. E-commerce is no exception.

Data shows that 66% of mobile checkouts take place on the web rather than in native apps. Installing an app from search results just to purchase an item requires too much friction, which is likely why so many people prefer to complete their purchases directly on the web.

Conversely, data also shows that mobile websites have a 66% lower conversion rate compared to desktop websites. Looked at another way, this means there is still tremendous room for growth in mobile web conversion rates.

In this post, I'd like to introduce two ways to boost mobile web conversions by improving forms.

On March 13, the Chrome Beta blog post was published. The personal highlight for me is that push notifications are now available in Chrome for Android.

If you thought, "Sure, push notifications might be handy," you're not shocked enough. You should be blown away. You should be dancing for joy. Let me explain why.

This article is a crosspost of an article on webcomponents.org.

As explained in previous articles, by using Template, Shadow DOM, and Custom Elements, you can build modular UI components. However, loading the HTML, CSS, and JavaScript for each of those components separately is inefficient.

Resolving dependencies is also no easy task. Think back to jQuery UI or Bootstrap: you had to include separate tags for various resources like JavaScript, CSS, and web fonts as needed. Especially with Web Components, where each custom tag is meant to be treated as a standalone component, it's easy to see how quickly things can get complicated.

HTML Imports is what allows you to bundle and load these resources in a single HTML file.

This article is a cross-post from an article on webcomponents.org.

Needless to say, HTML is the most important building block of web pages. However, because the features it provides are low-level, trying to build complex components often quickly leads to a confusing structure filled with endless divs. What if you could build custom components packed with the functionality you need? What if you could give those components tag names that accurately describe what they do? What if you could extend existing tags to add new capabilities? Custom Elements makes all of that possible.