4 ms·

Could you explain what you think of the pros and cons of flutter VS IONIC? I think flutter and it's astonishing number of issues on github + their lack of manpo

Could you explain what you think of the pros and cons of flutter VS IONIC? I think flutter and it's astonishing number of issues on github + their lack of manpower + their lack of major features + the presence of major performance and behavior bugs + the extremely small lib ecosystem (dart) is a major, useless risk for a startup for the benefit of tech hype. (just my point of view, don't take it personally)

MarkMc 7y ago
One of the pros of Flutter is that its popularity is growing strongly while Ionic's is basically flat: https://insights.stackoverflow.com/trends?tags=flutter%2Cionic%2Cionic4%2Cionic2%2Cionic3%2Cionic-framework https://insights.stackoverflow.com/trends?tags=flutter%2Cion... I haven't tried Ionic myself, but I have tried both React Native and Flutter for a small project and found Flutter to be more enjoyable and productive.
dragonsh 7y ago
I build a small ionic app when it was based on angularjs with dependency on Cordova and later moved to webview. I didn't like the experience and personally I still prefer Python syntax over Javascript, so that was another factor. Now I think IONIC has moved to web components using stencil.js as the base. Web Components is still an evolving standard and will still take time to gain traction, moreover the available documentation and help is limited. So if you compare ionic vs flutter I will still go with flutter given it generate binary app store package file by compiling dart code into native platform code. But given choice between native vs flutter I think except few use cases native still makes more sense.
Diesel555 7y ago
I've been writing in Ionic for a while now. I enjoy their philosophy. They put out their own description of the differences with Flutter (biased I'm sure). https://ionicframework.com/resources/articles/ionic-vs-flutter-comparison-guide https://ionicframework.com/resources/articles/ionic-vs-flutt... Ionic lets me build a web app and publish it to any device pretty easily. I don't have to use their components either... in fact after using Ionic, you may not use Ionic anymore at all. All you need is Capacitor to publish it. Flutter is it's own rendering engine, non-standard web language (Dart), and ecosystem. Ionic is just a CLI and collection of web components. Capacitor is Ionic's version of Cordova. It gives you access to device capabilities such as storage, camera, etc with very little code. So you can build a website, ask if it's Native on a device, and do more cool things if it is. Then push it to Android, iOS, and the Web. Ionic supports Angular, React (now in RC0), and Vue (Beta). This allows you to learn popular frameworks while still developing with one code base. Lastly, Ionic's Web Components are built using standard-compliant Web Components generated by a tool they made called StencilJS. So, now you can build a component in Stencil and publish it for simply the Web (No framework) or have them work with Angular, Vue or React. Larger corporations have started using StencilJS to manage their components when they use many frameworks. I use it because I don't know which framework I'll use next, or if I'll even use one.
- The_rationalist 7y ago
  What are the pro and cons of ionic Cordova vs ionic capacitor? How feature complete and stable is capacitor vs Cordova?
  - Diesel555 7y ago
    Cordova is time tested and has a large community behind it. I choose Capacitor if it's available and then go to Cordova if it's not. Ionic has a collection of easy to use Cordova plugins (https://ionicframework.com/docs/native/overview https://ionicframework.com/docs/native/overview). I have honestly found they they are not that well maintained. I ran into enough issues that I avoid them if I can. To be fair, the contributors are people contributing on their own free time with no financial incentive. Hence, I choose Capacitor when I can. They have a financial incentive (Ionic is open about this https://ionicframework.com/blog/ionic-2019-business-update/ https://ionicframework.com/blog/ionic-2019-business-update/) I joined when Capacitor was in beta and figured I'd use the up and coming. From research, it appeared there was a good reason Ionic created their own product. They didn't do it to simply stop using a tried and true product. Also to be clear, Cordova is not an Ionic product. It was a great community thing for a while to talk to native devices.

MarkMc 7y ago

One of the pros of Flutter is that its popularity is growing strongly while Ionic's is basically flat: https://insights.stackoverflow.com/trends?tags=flutter%2Cionic%2Cionic4%2Cionic2%2Cionic3%2Cionic-framework https://insights.stackoverflow.com/trends?tags=flutter%2Cion... I haven't tried Ionic myself, but I have tried both React Native and Flutter for a small project and found Flutter to be more enjoyable and productive.

dragonsh 7y ago

I build a small ionic app when it was based on angularjs with dependency on Cordova and later moved to webview. I didn't like the experience and personally I still prefer Python syntax over Javascript, so that was another factor. Now I think IONIC has moved to web components using stencil.js as the base. Web Components is still an evolving standard and will still take time to gain traction, moreover the available documentation and help is limited. So if you compare ionic vs flutter I will still go with flutter given it generate binary app store package file by compiling dart code into native platform code. But given choice between native vs flutter I think except few use cases native still makes more sense.

Diesel555 7y ago

I've been writing in Ionic for a while now. I enjoy their philosophy. They put out their own description of the differences with Flutter (biased I'm sure). https://ionicframework.com/resources/articles/ionic-vs-flutter-comparison-guide https://ionicframework.com/resources/articles/ionic-vs-flutt... Ionic lets me build a web app and publish it to any device pretty easily. I don't have to use their components either... in fact after using Ionic, you may not use Ionic anymore at all. All you need is Capacitor to publish it. Flutter is it's own rendering engine, non-standard web language (Dart), and ecosystem. Ionic is just a CLI and collection of web components. Capacitor is Ionic's version of Cordova. It gives you access to device capabilities such as storage, camera, etc with very little code. So you can build a website, ask if it's Native on a device, and do more cool things if it is. Then push it to Android, iOS, and the Web. Ionic supports Angular, React (now in RC0), and Vue (Beta). This allows you to learn popular frameworks while still developing with one code base. Lastly, Ionic's Web Components are built using standard-compliant Web Components generated by a tool they made called StencilJS. So, now you can build a component in Stencil and publish it for simply the Web (No framework) or have them work with Angular, Vue or React. Larger corporations have started using StencilJS to manage their components when they use many frameworks. I use it because I don't know which framework I'll use next, or if I'll even use one.

The_rationalist 7y ago
What are the pro and cons of ionic Cordova vs ionic capacitor? How feature complete and stable is capacitor vs Cordova?
- Diesel555 7y ago
  Cordova is time tested and has a large community behind it. I choose Capacitor if it's available and then go to Cordova if it's not. Ionic has a collection of easy to use Cordova plugins (https://ionicframework.com/docs/native/overview https://ionicframework.com/docs/native/overview). I have honestly found they they are not that well maintained. I ran into enough issues that I avoid them if I can. To be fair, the contributors are people contributing on their own free time with no financial incentive. Hence, I choose Capacitor when I can. They have a financial incentive (Ionic is open about this https://ionicframework.com/blog/ionic-2019-business-update/ https://ionicframework.com/blog/ionic-2019-business-update/) I joined when Capacitor was in beta and figured I'd use the up and coming. From research, it appeared there was a good reason Ionic created their own product. They didn't do it to simply stop using a tried and true product. Also to be clear, Cordova is not an Ionic product. It was a great community thing for a while to talk to native devices.