Tender Surrender

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.

On March 13th, the Chrome Beta blog post was released. For me, the highlight was that push notifications became available on Chrome for Android.

If you're thinking, "Sure, push notifications might be convenient," then you're in for a surprise. You should be overwhelmed. You should be jumping for joy. Here's why.

This article is a cross-post of webcomponents.org article.

We've previously explained that using Template, Shadow DOM, and Custom Elements allows you to create UI components for each function. However, it's inefficient to call the HTML, CSS, and JavaScript of a component that uses these methods separately.

Resolving dependencies is also not easy. Think of jQuery UI or Bootstrap. You had to write various resources such as JavaScript, CSS, and web fonts in separate tags as needed. It's easy to imagine how things could get complicated, especially with Web Components, which are supposed to treat each tag as a component.

HTML Imports allows you to load all of these resources together in a single HTML file.

This article is a cross-post of webcomponents.org article.

Needless to say, HTML is the most important element that makes up a web page. However, because the functionality it provides is low-level, when you try to create a complex component, it can quickly become an unclear structure full of divs. For example, what if you could create a unique component that incorporated the functionality you needed? For example, what if you could give that component a tag name that accurately represented its function? What if you could extend existing tags to add new functionality? Custom Elements makes this possible.

This article is a cross-post of the webcomponents.org article.

Shadow DOM allows you to add a DOM tree to a DOM element, containing styles and markup that are local to that node, separate from the rest of the webpage. This article and video explain Shadow DOM.