Ionic 4 is here!

Most importantly to some, Ionic 4 is now framework agnostic. It’s built using standardised Web Components rather than the Angular directives of the past, Shadow DOM APIs and standard web APIs. This means that developers can be confident that Ionic’s component APIs will be stable for many years to come; something we could only dream of before. Although it is still recommended to use Angular for performance reasons, it is now possible to use react or vue.js or any other component libraries within your project. This is especially powerful when building PWAs or apps that are just one part in an overall project delivery that needs both web and app capabilities, often integrating with existing systems.

Performance is often sighted as a reason not to use Ionic or other hybrid app development frameworks however with a combination of advancements in browsers (in terms of capabilities, javascript processing speeds and standardisation) and Ionic itself with version 4, these are less and less of an issue. Too often performance issues are blamed on the framework or webview rendering however it is impossible for an application to be performant if the code itself is not written in a performant way. I do not mean to criticise any other developers coding, but due to the easy road into javascript and Ionic development it is unfortunately far too common for applications to go into production environments working functionally, but not written in performant way. I would argue that this has much more of an impact on general Ionic apps performance than the framework itself. The Ionic team have run tests to show that Ionic Angular 4 is at least 1.5 times faster than Ionic Angular 3, taking 2.2 seconds to first meaningful paint rather than 3.8 for version 3 in the past.