I'm always afraid of investing a lot of time into this type of frameworks and then having the rug pulled from under me. Most of the time I spent learning angular ended up being a waste of time and I'm still scarred from then. Also that logo looks familiar?
You're not wrong. I've worked with Ionic v1 a fair amount. The framework is good for mockups and prototypes but nothing more. What ends up happening, as you app grows to include notifications, deep linking, etc, is you need to rely on more and more hacky thirdparty solutions. These days I either code natively or use Xamarin.
You are wrong. I have few mobile apps, made with Ionic and Ionic 2, some have been used on warehouse as part of huge WMS (to scan items and manage whole business process of warehouse worker), some were apps for business as part of CRM (with geolocation, maps and handwritten signatures). And every time product owners were very satisfied with the result and with speed of development.
Ionic 1 had too hacky API and not great performance, but Ionic 2 is much more mature in both of these fields.