To be specific--and maybe this only pertains to version 1.x--I found managing navigation state in our largest app to be quite clumsy and at times, downright perplexing. In Swift, managing navigation state is relatively…
Agreed. For me, that was another reason to move away from Ionic. That its largest dependency came to differ so greatly from that of the previous version, was enough for me. If I was going to be forced into learning…
We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova…
Do you have something specific in mind, regarding the low-end of the market? Maybe a couple of examples? I'm really interested in understanding what you mean.
To be specific--and maybe this only pertains to version 1.x--I found managing navigation state in our largest app to be quite clumsy and at times, downright perplexing. In Swift, managing navigation state is relatively…
Agreed. For me, that was another reason to move away from Ionic. That its largest dependency came to differ so greatly from that of the previous version, was enough for me. If I was going to be forced into learning…
We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova…
Do you have something specific in mind, regarding the low-end of the market? Maybe a couple of examples? I'm really interested in understanding what you mean.