Hacker News new | ask | show | jobs
by EGreg 3428 days ago
What do you all think of Cordova? Do the author's comments apply there also? Does it crash from using too much memory after a while of loading objects? And does it make things not work on older devices and platforms making it a dealbreaker for anyone?
2 comments

My recent experience with Cordova has been much better than I expected. It's quite a bit easier to work with than I thought, and the performance is fine for the relatively 'standard' UI and animations/transitions I needed. And with a few specific tweaks I could even make it seem pretty native (momentum scrolling, etc.).

All that said, I'd still recommend going native or React Native if 1) you can afford it (time/money/properly skilled employee), or if 2) the app's needs are beyond what a 'typical' in-browser web app does.

In regards to the latter I've found quite a number of plugins that let you do notifications, or use the accelerometer, but on the whole I've found that cordova plugins can be finicky. Plus, the more plugins I need to add and the more native functionality I need to use, the more nervous I get about not fully grasping the underlying stuff.

Basically, I used to think Cordova was never really an acceptable option, especially with the release of React Native. Now, I think there are plenty of situations where it's the best solution for a client.

I haven't used Cordova recently, but when I last did a couple of years ago I had similar problems with image handling resulting in memory running out on low spec devices. From the comments I've read here probably for similar reasons as well, the camera capture API was passing a Base64 encoded image to the application rather than a file URL.