4 ms·

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

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.

jthoms1 10y ago
Ionic2 is quite a bit different. In my opinion it scales really well especially with Typescript. Most of features that would have required thirdparty solutions are baked into ionic-native.
- deleted 10y ago
  [deleted]
EugeneOZ 10y ago
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.
- alexkavon 10y ago
  I don't believe I ever mentioned ionic v2... I don't doubt v2 brought many improvements. However you just can't beat the power of not operating in a Webview.
  - timrichard 10y ago
    However, Webviews do give you a very predictable container to target. If you use something like Intel Crosswalk [1] as part of your project for Android, you can bundle a recent Chromium webview to much older devices. And Flexbox is very well suited to solve phone/phablet/tablet layout problems. [1] https://crosswalk-project.org/ https://crosswalk-project.org/
    - pikzen 10y ago
      Because people seemed to love 80MB Chrome runtimes being bundled with terrible Electron applications on the desktop, Crosswalk allows you to bundle 40MB of chromium for your terrible application on Android.

jthoms1 10y ago

Ionic2 is quite a bit different. In my opinion it scales really well especially with Typescript. Most of features that would have required thirdparty solutions are baked into ionic-native.

deleted 10y ago
[deleted]

EugeneOZ 10y ago

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.

alexkavon 10y ago
I don't believe I ever mentioned ionic v2... I don't doubt v2 brought many improvements. However you just can't beat the power of not operating in a Webview.
- timrichard 10y ago
  However, Webviews do give you a very predictable container to target. If you use something like Intel Crosswalk [1] as part of your project for Android, you can bundle a recent Chromium webview to much older devices. And Flexbox is very well suited to solve phone/phablet/tablet layout problems. [1] https://crosswalk-project.org/ https://crosswalk-project.org/
  - pikzen 10y ago
    Because people seemed to love 80MB Chrome runtimes being bundled with terrible Electron applications on the desktop, Crosswalk allows you to bundle 40MB of chromium for your terrible application on Android.