By Josh Morony
I’ve touched on this point many times in the past, so I will only make it briefly now. Ionic and HTML5 mobile applications in general, make it super easy for people to build mobile applications, but it also makes it super easy to build bad applications. It’s not always easy to build good applications with Ionic – anything more than a simple application will require more intimate knowledge of web performance and how Ionic works if you want top notch performance. This is the case with any framework or if you’re building your application directly with native code, it’s never easy to build a complex application that performs well (Ionic just has a lower barrier to entry).
In the case of Ionic and other HTML5 mobile applications, I think it’s mostly a matter of “you don’t know what you don’t know” so people may end up building applications in a way that seems correct and that works, but really they are making critical mistakes that are going to impact performance.
If you want to read more of my thoughts on why the ease of which Ionic applications can be made is both a good thing and a bad thing, you might be interested in reading another recent article I wrote: Is Ionic the WordPress of the Mobile App World?