I recently asked: Is desktop software is dead?
Increasingly, I am of the opinion that desktop software is well on its way to extinction.
In its place, Synced-Data Applications (SDAs) have emerged.
One of the best examples I’ve recently run across is Evernote. Native Evernote applications exist for desktops (as well as handhelds) and for the cloud (e.g., via a Web browser). Your data is replicated between the cloud (in this example, Evernote’s Webstores) and your desktop(s)/handheld(s). Synced-Data Applications.
And with Google Gears, Google Docs has also entered the SDA software paradigm.
With SDAs, it’s not just about the cloud, and it’s not just about the desktop/handheld. It’s all about the convergence that this software paradigm brings.
A revised version of the figure I shared in the previous post on this thread is included below.
Once again, it emphasizes that interest is focused on the convergence between the isolated realm of the desktop/handheld on the one hand, and the cloud (I previously referred to this as the network) on the other.
It’s much, much less about commercial versus Open Source software. And yes, I remain unaware of SDA examples that live purely in the Open Source realm …
Another quote from Chris Anderson’s The Long Tail:
Likewise for Google, which seems both omniscient and inscrutable. It makes connections that you or I might not, because they naturally emerge from math on a scale we can’t comprehend. Google is arguably the first company to be born with the alien intelligence of the Web’s “massive-scale” statistics hardwired into its DNA. That’s why it’s so successful, and so seemingly unstoppable.
Author Paul Graham puts it like this:
The Web naturally has a certain grain, and Google is aligned with it. That’s why their success seems so effortless. They’re sailing with the wind, instead of sitting becalmed praying for a business model, like print media, or trying to tack upwind by suing their customers, like Microsoft and the record labels. Google doesn’t try to force things to happen their way. They try to figure out what’s going to happen, and arrange to be standing there when it does.
I’ve never read a more-concise distillation of the very essence of Google.
I’ve blogged a lot about the GMail client for the Blackberry over the past few weeks.
There’s been enough interest to warrant a Top Ten list – something along the lines of “The Top Ten Reasons You’ll Want GMail on Your Blackberry”.
Before I release my Top Ten, I thought I’d consult the collective wisdom of those who happen by my blog.
Please share a comment to this post, or drop me an email (ian DOT lumb AT gmail DOT com), and let me know what you think should be on this Top Ten list.
I’ll summarize and share in about a week.
With thanks in advance.
In a recent post, I blogged:
Now picture this: A J2ME client application for Google Docs & Spreadsheets.
This is interesting on a number of levels:
- It’s feasible! Google Docs & Spreadsheets is likely written in
some variant of Java (J2*E) already, so paring it down to J2ME is (in
Alas, Google Docs & Spreadsheets (GD&S) isn’t based on some variant of J2*E.
Clearly AJAX and J2ME are completely different environments/platforms.
Thus it would seem that Google has the options summarized by a two-dimensional platform versus motivity grid.
On the vertical axis, platform ranges from self-contained to service-oriented.
Motivity is a bona fide word that is synonymous with locomotion (the power or ability to move). I intend here to coin a slightly different meaning, a juxtaposition of mobility and connectivity. More precisely, I propose to use motivity as a semi-quantitative measure of the degree of mobility relative to the degree of connectivity. As mobility increases, connectivity decreases, and motivity therefore increases. This is illustrated by the horizontal axis of the two-dimensional grid. It is also important to note that connectivity is itself a proxy for bandwidth and latency. More precisely, high connectivity is taken to imply high bandwidth, low latency connectivity.
Thus the options in taking GD&S to the Blackberry are:
- Port GD&S to the Blackberry operating environment (i.e., develop a native J2ME client version of GD&S) – the lower-right quadrant of the 2D-grid
Thus a revised two-dimensional grid of the possibilities is shown below.
Either way, it may be some time before Google Docs & Spreadsheets makes it to the Blackberry.