Also, I don't like the fact that webmail providers such as GMail cannot only track my e-mail, but also my reading/browsing behavior.
predictable shortcuts are like bookmarks, easily manageable (tabs expose for chrome) - https://chrome.google.com/webstore/detail/ackpfhlmgjdjlohhjm... your ISP is tracking, cookies are tracking, or basically its more of a hassle to minimize all tracking than to stop thinking about it.
Either way in the end it is about preference
There are also other effects of externalizing your tools that don't relate to continuity of uptime: levels of complexity, adaptability, security, and manageability of change all have different values for web-based and desktop software.
Maybe it's because I'm looking for solutions that will last for long years, not the apps that I have to change every three or so months. I guess this is not possible nowdays.
Browsers fail horribly at providing a desktop alternative.
The obsession with a web page as a document is the part that needs to be addressed.
Firefox's long lacking support for something as simple as overflow:ellipsis is one of the examples of the anti app ethos of browsers. You don't need it much on web pages, but it's pretty essential in business apps as you've got to present a lot of data but need to show it compactly. And it's essential to indicate there's more text to a comment or email.
That and the terrible support for non-fixed layout.
You (well, some of you) are already using Gmail seamlessly as a web app, on your laptop, your mobile phone and your tablet. Each with their own unique interface, but each with the same metaphors. Same with Twitter, Facebook and a slew of other services.
I think the definition of what constitutes an 'app' is blurring. Web-apps, in-browser Chrome apps, browser add-ons, native apps, site-specific browsers, web-content inside native apps, native content inside web apps, the Chrome book, all of that has some app-ness… Some web apps don't need an internet connection any more. Some native apps are completely dependent on an internet connection. Which of these is the web app, then? It is really only that some apps are executed within the context of a browser and some are not. That says little about their web-awareness, though.
Requiring Internet access or not has nothing to do with it.
For example, an OS X native app wouldn't run in Linux (at least as easily as a Linux native app would). A web app would.
For the workgroup that I support, I give them Mailplane for Google Apps. I find that some users just can't get past the idea of having a "shortcut" on their desktop, even when on a Mac.