Watch it.
The problem with native apps is the installation barrier- if I had apps installed to do everything that I'd love my phone to do, I'd be overwhelmed with hundreds of apps installed. Web-based apps have the potential to slip in and out of use as necessary, with more applicable discovery mechanisms (geo, proximity, etc).
The reason is that native apps can move so much more quickly than web apps. I'll bet Apple could get widespread adoption of a zero-install feature on iOS in six months, simply by mandating it for the app store and featuring early adopters. But HTML5 YouTube has been in beta for over two years, and the <video> tag was introduced over half a decade ago. The web moves at a snail's pace by comparison.
I did try to watch the video, but scrubbing didn't work, which sort of illustrates my point.
On the development side of things I believe we're going to see a massive shift back to web-app development simply because of economics. There is no way any small group of developers can build desktop, iOS, and Android versions of their application simultaneously. This iOS fad WILL DIE because of costs, and that fact that Android numbers are rising dramatically, and people need to come up with a way to support each mobile platform and be able to use that app from their desktops too -- mobile web apps are the answer.
Aren't webapps isolated? Funneled through a strict paradigm? And also at the other end of a comparatively slow link?
The idea of a general purpose computer as it exists in the current desktop form must be put aside. We can't head to a future of everything we do in one portable device and from there to ubiquitous life integration when every app can read all your data and send it to anyone for any purpose, Android is falling fowl of that right now, we have to have isolation and sandboxing, different trust levels, restricted access to more important data (contacts, for example), to make a solid and trustable future platform.
Playing Devil's advocate, Google Drive has an API for webapps to access the user's files (with permissions only to files created by the app itself or that the user specifically opens). The webapp chooses the MIMEtypes it can open and then the user can just do Open With → App.
Sure, it's GDrive specific for now, but the API is fairly generic and if it's successful, I can see other online drives implementing it themselves. Well, assuming Oracle loses this lawsuit, I guess :)
Aren't webapps isolated? Funneled through a strict paradigm? And also at the other end of a comparatively slow link?
APIs de-isolate them. Both the proprietary ones that already exist and open, distributed ones like http://webintents.org/
And besides, aren't native apps on mobile isolated too?
And the link between the user and the app may be slow, but it only needs to carry the UI. The data will flow from "cloud to cloud" at very high speed.
We can't head to a future of everything we do in one portable device and from there to ubiquitous life integration when every app can read all your data and send it to anyone for any purpose, Android is falling fowl of that right now, we have to have isolation and sandboxing, different trust levels, restricted access to more important data (contacts, for example), to make a solid and trustable future platform.
Uh, Android does have sandboxing and isolation, and apps can only access your data if you specifically allow them to. iOS was the one which didn't require permission to access your contacts (though Apple has said it will).
Wrong; The filesystem is FAT32, and has no additional permissions beyond a "read only" bit. Any data that's there can be accessed by apps, as things stand.
http://arstechnica.com/open-source/news/2010/12/ext4-filesys...
Relevant text: "Every Android-compatible device supports a shared "external storage" that you can use to save files. This can be a removable storage media (such as an SD card) or an internal (non-removable) storage. Files saved to the external storage are world-readable and can be modified by the user when they enable USB mass storage to transfer files on a computer."
I forgot to specify that in my original post. My mistake.
This is an old presentation by Gruber (Daring Fireball) from 2010, but it is still excellent. And only 10 minutes long. He argues that iOS vs Web is a false dichotomy, in fact, the Web was from the start a big part of iOS. He then differentiates between "Web Apps vs Browser Apps". Your notion is, that a Web App is something which uses html. But he argues, and I think this rings true, that a Web App is something which uses http.
"How can you say that Twitter, even though it is a native iPhone App, isn't really a Web App?"
Most people don't even understand what a filesystem is, nevermind whether it's open or not. I agree with you that data is moving online but that's orthogonal to the native vs web app question.
Current trends indicate user attention is shifting even more to native, BTW: http://blog.flurry.com/bid/80241/Mobile-App-Usage-Further-Do...
The web vs native debate is really just a debate about which technology is better suited to building cloud client apps. HTML5 + JS is just another UI stack like Cocoa Touch or Android.
I don't know you from a bar of soap but reading your comments, I get the impression of an American late-teen with a solid amount of technical knowledge, strong opinions but staggeringly little perspective.
Even amongst those who are capable of administering an 'open platform cloud infrastructure' there are few who have the time. In my own circumstances, ten years of programming experience, recently shifted from consultancy to an analysis role at a major financial institution, start up on the side, seven week old baby,ten year old daughter, wife, 33 years of age... Let me tell you: the more my technology 'just works' the better. I won't accept my rights bing trampled on but a system that is elegant and robust albeit a bit restrictive is far preferable to spending hour on end tinkering with something that I need to actually use as opposed to configure endlessly.
You are correct that data is moving into the cloud, and away from Apple's restricted file system (or any local file system). But that has nothing to do with native vs. web (HTML) apps. Native apps can easily store all their data in the cloud (ANY cloud, not just iCloud), and still be native apps in the usual sense of the word.
It seems to me that the trend is toward native, cloud based apps. And these two concepts are not in conflict. As cageface says, they are orthogonal.
Which is different from browser apps... how, again?
Web apps solved the problem of having to figure out how to find, install, or update software and not having it everywhere you go. App stores have caught up on discovery/installation/updates, and mobile has solved the problem of not having it everywhere I go.
Web apps will eventually catch up on performance and maybe someday they will feel like first class citizens in any given OS rather than being relegated to mess of throwaway tabs. We've been within 3 years of that for something like a decade, but maybe we really finally are within 3 years of that.
But we aren't within 3 years of having any two web apps looking similar and using familiar UI elements. Every web app is a new UI to learn, maybe not a problem for you or me, but mobile has reached 3 year olds and 90 year olds and everyone in between, most of whom have not acquired the skill to pick up umfamiliar UIs and don't want to.
As for data moving to the cloud, I'm with you. And I have a lot of native apps that interact with remote data.