3 ms·

"The main advantage of React over Vue and Angular is: React Native. Vue doesn't have anything close to it." Have you tried Quasar? (http://quasar-framework.org

"The main advantage of React over Vue and Angular is: React Native. Vue doesn't have anything close to it." Have you tried Quasar? (http://quasar-framework.org/ http://quasar-framework.org/) We're using it right now for a customer project and I'm very happy so far. Performance feels better than Ionic2.

WA 9y ago
I haven't tried it, because the components don't look native. Buttons with text that have a shadow? What on earth is that? It looks less polished than Ionic and suffers the same problems of all Cordova-based hybrid apps: No native input controls. For me, this is a dealbreaker.
- renesd 9y ago
  Cordova is all about plugins. You can use a native datepicker plugin for example. If you need native functionality, use a plugin. (there's probably one already there, but maybe you need to write a tiny bit of native code). I guess that's the whole point of hybrid that people don't understand - it's a hybrid, and you get to choose the best of both, making the trade offs you need to make for the best result. Not ideal for every app/budget, but I think people just don't get this part - use the native plugins if you need them! :) Ship fast, and slowly replace all the bits with native (if you need to). [fast|cheap|good] pick two! (then the third).
  - WA 9y ago
    So, the idea of Ionic/Cordova is: You can release an app without writing native code. Your suggestions certainly work, but they bring up questions: - How do I write the native code you mentioned? - How do I plugin the native datepicker in Ionic? - How do I deal with different native plugins for iOS and Android? I bet there are solutions for all of these problems, but then again, I might just want to consider React Native, because Ionic doesn't bring any more benefits over React Native. With Hybrid, it's all a compromise, and it might be worth it. That's not my point. My point is: Don't use Ionic/web-based hybrid, if native input controls play an important part in your app. It might simply not be worth it, because there are better tools to achieve the same outcome.
    - renesd 9y ago
      The datepicker native input plugin exists, so it's just installing it. Then you get a JS api for it. If it doesn't exist somewhere in the thousands of plugins available, you'll have to make it yourself. The other thing that happens, is perhaps a plugin is only available for Android. Maybe there's another one with a slightly different JS api for iOS... or none. I've also done emscripten compiled C++ mixed in there. Which replaced various native apps. Since it was mostly OpenGL anyway... the few controls were easily implemented in JS/Html. Anyway... just trying to share some options. Lots of native cordova plugins available (which I guess is it's main point). I really don't care what other people do... and somehow got drawn in to this discussion again!
      - WA 9y ago
        Thanks for the suggestions. While trying Ionic, I didn't install Cordova plugins to fine-tune input control. I will give it another shot.
  - franciskim 9y ago
    Really nicely put.
  - positivecomment 9y ago
    I mostly agree, just a silly nitpick: Fast usually means cheap, especially if you are talking about software engineering. So I'd say the choice is between "fast & cheap" and good.

WA 9y ago

I haven't tried it, because the components don't look native. Buttons with text that have a shadow? What on earth is that? It looks less polished than Ionic and suffers the same problems of all Cordova-based hybrid apps: No native input controls. For me, this is a dealbreaker.

renesd 9y ago
Cordova is all about plugins. You can use a native datepicker plugin for example. If you need native functionality, use a plugin. (there's probably one already there, but maybe you need to write a tiny bit of native code). I guess that's the whole point of hybrid that people don't understand - it's a hybrid, and you get to choose the best of both, making the trade offs you need to make for the best result. Not ideal for every app/budget, but I think people just don't get this part - use the native plugins if you need them! :) Ship fast, and slowly replace all the bits with native (if you need to). [fast|cheap|good] pick two! (then the third).
- WA 9y ago
  So, the idea of Ionic/Cordova is: You can release an app without writing native code. Your suggestions certainly work, but they bring up questions: - How do I write the native code you mentioned? - How do I plugin the native datepicker in Ionic? - How do I deal with different native plugins for iOS and Android? I bet there are solutions for all of these problems, but then again, I might just want to consider React Native, because Ionic doesn't bring any more benefits over React Native. With Hybrid, it's all a compromise, and it might be worth it. That's not my point. My point is: Don't use Ionic/web-based hybrid, if native input controls play an important part in your app. It might simply not be worth it, because there are better tools to achieve the same outcome.
  - renesd 9y ago
    The datepicker native input plugin exists, so it's just installing it. Then you get a JS api for it. If it doesn't exist somewhere in the thousands of plugins available, you'll have to make it yourself. The other thing that happens, is perhaps a plugin is only available for Android. Maybe there's another one with a slightly different JS api for iOS... or none. I've also done emscripten compiled C++ mixed in there. Which replaced various native apps. Since it was mostly OpenGL anyway... the few controls were easily implemented in JS/Html. Anyway... just trying to share some options. Lots of native cordova plugins available (which I guess is it's main point). I really don't care what other people do... and somehow got drawn in to this discussion again!
    - WA 9y ago
      Thanks for the suggestions. While trying Ionic, I didn't install Cordova plugins to fine-tune input control. I will give it another shot.
- franciskim 9y ago
  Really nicely put.
- positivecomment 9y ago
  I mostly agree, just a silly nitpick: Fast usually means cheap, especially if you are talking about software engineering. So I'd say the choice is between "fast & cheap" and good.