[Bahamut]

We just built a mostly done prototype of one of our products with Ionic in 4 weeks at my company, rewriting existing components to take advantage of Ionic. We ran into a bunch of Ionic bugs (on beta 13), and took a dive into integrating the beta 14 candidate with Angular 1.3 into the prototype (and came upon what looks like ng-animate bugs in 1.3) last night. We are also using CCA.

Ionic has pretty much been a joy to use, and fit exactly our requirements (we do hybrid web/mobile apps on my team, mobile being Android only since we do native iOS development). The article is pretty much on the mark, and you need to be careful when it comes to performance on mobile. Optimizing stuff like using the track by syntax with ng-repeat is vital. Taking advantage of Angular's superior testability and structure conducive for rapid app development (and having 3 Angular contributors on the team doesn't hurt) allowed us to build an impressive app very quickly, as well as avoid some of the nasty Ionic bugs we came upon (mostly related to their $viewHistory service and broken back button).

I haven't gotten to play around with the beta 14 candidate yet, but I was unhappy with how opinionated Ionic was when it came to the history and how it's expected that everything would inherit from a state with tabs.

I will say this though - if it wasn't for the decision to use Ionic, we would have been in a lot of pain trying to meet our deadlines trying to write a lot of this functionality from scratch, and we would not have had stuff like the native feel with the tapping & scrolling behavior that Ionic provides. Overall the Ionic team did a great job with the product, and I'm pretty happy with it.