FUD.
Ever heard of WebSQL for storing your data? After 10 months, you should have been able to work around nearly anything you mention in your article.
Ever heard of WebSQL for storing your data? After 10 months, you should have been able to work around nearly anything you mention in your article.
But that's exactly the point. Ages ago this comment on HN summarized the situation perfectly... https://news.ycombinator.com/item?id=7442766
"It takes less time to learn and build native instead of trying to hammer Javascript into a hole it doesnt fit into, and spending hours attempting to optimize it's performance to no end."
...depending on the size of the app.
I have an open source project that I devote a handful of hours a week to. I absolutely do not have the capacity to create native apps for desktop, iOS, and Android. It's great if the writer of that comment has either a tiny app that does nothing important or has a ton of free time, but not everyone is so lucky to be able to maintain an app on 3+ separate platforms.
Javascript is the one language all devices speak well, so as someone who is proficient in it, has an existing (somewhat complicated) app, and wants to port it to mobile as quickly as possible, rebuilding everything twice in two different languages and two different UI platforms is just not an option.
iOS has IndexedDB since v8.0 though the implementation is poor. I don't know if they've fixed it in any 8.x release. However, you're (mostly) not using IndexedDB directly anyway but a storage library, which supports IndexedDB, WebSQL and maybe localstorage as a fallback (e.g. localForage[1] for a simple key-value DB).
The problem right here, to have to "work around" for 10 month.