Entries in in situ (1)

Wednesday
Sep282011

In Situ and in Sync

A small group of irregulars have been meeting on an ad hoc basis over the course of the past few months to consider mobile use of and influence on cloud-based (or, better said, network resident) services. From this group, Duncan Davidson of Bullpen Capital and Peter Christy of Internet Research Group have had a short conversation that was kicked off by a recent series of posts by Fred Wilson, venture capitalist and blogger, about the nature of content in use by mobile and less peripetetic devices.  The post in question, In Situ Content, prompted Peter to question "…whether remote acces to data and tools in the Cloud will ever be good enough."  He went on to support the idea of thick (or thicker) clients, and pointed to the recent Microsof Build Conference and which they showed off Windows 8 with Azure integration.

My thoughts in response.

I agree that for much of what wants to be done on a laptop/desktop, or on a tablet or smart phone for that matter, there is something 'thicker' than a dumb web browser required as the client.  

As the browsers acquire more heft, with both proprietary and more HTML5 based functionality, the browser becomes (at the very least) the fundament of any 'local client' technology.  Without this, the 'cloud applications' and the cloud storage of my data, my documents and collections will hit a wall.

In thinking about cloud storage of my personal possessions, I'd rather not think of things as 'documents'.  Rather, if one considers the active principle one of assembling and then 'rendering' a herd of data components (core data, meta-data, …) , we should use the term assemblage to replace the concept of document.  The assembly doesn't require physical proximity of data components, just a good and smoothly working linkage amongst them. 

I agree that, to the degree possible, the world will move toward the 'master data assemblage' (or what Duncan referred to as the ur-document) that resides in a cloud, and is sync'd for those situations where there is intermittent communication … which pretty much describes my iPhone and its use of AT&T Mobile's data plan.

The point is that it depends on accomplishing 'synchronization' well and correctly.  'Correctly', by the way, needs to cover issues of usability & user experience , safety (privacy & security), and economy (optimal utilization of compute, network and storage).  There is no single definition of 'correct' in these scenarios … the optimal recipe is going to completely depend on the context and the ability to adapt as the context changes for the mobile user.