I've worked with Cordova, and in many cases, I don't think it's appropriate. In particular, apps that: * require native functionality (i.e. access to photos,

I've worked with Cordova, and in many cases, I don't think it's appropriate. In particular, apps that: * require native functionality (i.e. access to photos, GPS, notifications) * are sufficiently complex UI-wise ... are not well served by Cordova. Why? * when you start needing native functionality, you will find that the plugin ecosystem is often lacking; having to modify or write your own plugins means that you have suddenly have three languages (JS, Obj-C/Swift, Java) to contend with instead of two (Obj-C/Swift, Java) * iOS and Android development kits make it easy to create apps that feel like they belong on their respective platforms — there is no need to spend developer or UI/UX looking for a library with lots of UI elements or developing a look/feel Moreover, even relatively simple things like table layouts that "feel nice" — e.g. highlight when you tap on them, implement swiping to delete elements, allow for re-arranging — are significantly more onerous to implement in JS as opposed to natively. If your app is sufficiently simple and doesn't fall prey to these pitfalls, you might want to consider Cordova. But if you really don't need native functionality, you might as well just get `UIWebView` working yourself.