I agree that if you have the resources to build something on native, go right ahead. But as someone who has very limited time to work on a passion project (http

I agree that if you have the resources to build something on native, go right ahead. But as someone who has very limited time to work on a passion project (https://turtl.it https://turtl.it), I will be damned if I split up my efforts writing different apps for iOS, Android, and desktop. Thanks to things like Cordova, node-webkit, and various other tools, I can write my interface/logic once and run it everywhere (with a bit of wrapping). No, it will not be perfect. Yes a native app would perform better. But I don't think my users (who continually ask me for a mobile app) are really going to care that much if the page transitions jump a tiny bit. And once Safari pulls its head out of its ass and supports AES-GCM in its WebCrypto implementation, I can do fully-native crypto in my app, and the largest performance hit goes away. HTML5 is the poor person's write once, run everywhere. Although not perfect, it continually strives to be better. It enables someone like me, who can only work nights and weekends, to build something useful and usable for a lot of people in a minimal amount of time. If people don't like Turtl mobile because it doesn't have seamless transitions, they can use Evernote instead and have their plaintext data leaked all over the web.