Wow, what a month! October saw some big news drop:

Firefox version 63 enabled the Shadow DOM and Custom Elements (aka Web Components) APIs by default:

Tomorrow Oct 23rd, @firefox will ship v63, with support for Custom Elements & Shadow DOM specs by default (no flag needed anymore) 🎉 Can't wait! #WebComponents #Everywhere pic.twitter.com/jZ8jvBjIT7 — Julien Renaux (@julienrenaux) October 22, 2018

And, web components and Shadow DOM support are now stable across all major browsers, with exception of Microsoft Edge. However, ME’s team has started development, so that’s good news.

Naturally, we’re very excited about this over at Ionic, as the upcoming version of our open source UI toolkit, Framework v4, is built on web components.

Why is Ionic so invested in Web Components?

Ionic’s goal has always been to make it easy to develop apps using web technologies (HTML, CSS, and JavaScript). By using web technologies, Ionic is able to work across a wide range of devices, operating systems, and browsers, all while using the same codebase. Looking to the future, it’s clear that web components are the way forward:

Ionic framework UI components become more stable. By leveraging the built-in capabilities that all major browsers are standardizing on, our team has more time to innovate on new features and bug fixes.

Support for additional platforms without significant rework. Today, iOS and Android, tomorrow… no one knows. Platforms come and go (remember Windows Phone? Blackberry?), but Ionic is forever 💙.

Support for additional JavaScript frameworks. Traditionally, Ionic has been tied to Angular, but the possibilities are opening up. Soon, we’ll support React and Vue. Who knows what JavaScript framework will be popular five years from now? That’s OK – we’ll be ready for it!

What about Legacy Browsers?

While we focus on the future, we understand that some developers need to support older browsers, such as Internet Explorer 11. Good news: Ionic Framework v4 dynamically includes all the polyfills needed to support them! A polyfill “fills in” the code that modern browsers provide natively and traditionally, they are always downloaded by all users, whether the browser required them or not. Ionic takes the opposite approach: only browsers that require the polyfills (Microsoft IE and Edge) download them.

The result? You, the developer, don’t need to do any extra work – just use the feature directly.

The future, powered by cross-platform web components, is very bright. Have you checked out the Ionic v4 beta yet? Get started here.