| Interesting that you had so many pain points. I like Ionic, don't love it but I find it to be very very easy to work with. I don't mean to flame, I just want to provide a counter example as I was using Ionic on the day to day basis for about 5 months. - I find the router to be very easy to use, requiring no work arounds, you call the nav controller and push / set a view, nothing crazy here. - The build process, specifically for the TypeScript? Are you using the CLI? There's just about nothing you need to do -I was able to start fresh on a mac and have everything up and running for both Android and iOS within 2 hours (this is mostly installing the Android SDKS). - And the live reloading will reload your entire app within 20 seconds, and this was on a pretty large Banking application using most of the plugins that are available (Camera, fingerprint, maps, etc etc etc). Note that this is all done through using the Ionic CLI, which really eases the development process. I personally wouldn't try it without the CLI. |
When I only update scss that is very quick indeed. The start process is very quick also.
For the router, things have became messy when I tried nested ion-nav. A method is deprecated (getRootNav) and the new is not even ready to use! (getRootNavById)
I post many issues on github. Still using ionic router (no other choices now, but by using tricks like events), and ionic cli for building, some buttons also, and I avoid anything else.
ion-menu was too buggy on ios, I had to make a menu by myself
The general quality on ios is very poor
Some plugins are great but I have bizarre issues... Keyboard plugin for exemple, I had to "ngZone" it to make it work.
Using the grid was too verbose and too buggy also. I design everything in flexbox now. It fells that ionic is trying to build a good WYSIWYGs editor with ionic creator but making developpers "beta-testing" their frameworks (sorry to complain after a open source project)