(this is page 103 of 121)





Latest

In reading a great piece on the future of social networking in today's NYTimes (via Pete Cashmore's great Mashable blog), I learned that Cisco has been snapping up "social networking" assets— a move that is being universally ridiculed in the blogosphere because Cisco is only apparently supposed to know about routers and switches.

This is indeed a bogus move but not because "social networking" is a perfect example of a feature and not a product. After all, Cisco is the king of buying features and making products out of them. The real elephant in the room on this one is that there is absolutely zero business model overlap here— and this is what will ultimately lead whatever assets they acquire to get marginalized, ignored, and finally written off as a hangover during that crazy "Web 2.0 bubble."

So far as I can tell, the only business model that works with social network sites, once they are at scale, is an ad-based media model (this of course begs the question of why you'd buy a social network site that is not at scale if you don't have the tools to bring it to scale). And I may be wrong here— but I'm not sure that I've ever seen Cisco's ad salesforce pounding the pavement on Madison avenue.

I remember that people laughed when Cisco bought Linksys and commented that the company didn't know the first thing about marketing and selling consumer networking equipment. But at least in that case, the business models (sell chips with RJ-45 ports, make money) was pretty complementary. In this case, I'm afraid of what the ultimate fate of these social networking folks is going to be 12 months from now. Unless of course, then can get good at writing router firmware.

Comments Permalink

I've been cynical about the One Laptop Per Child project ever since I first saw Nicholas Negroponte talk about it at the D conference two years ago. That said, I'm really happy to be wrong in that it seems like it's way more than a science fair project and that millions of kids may actually reap enormous benefit from this little $100 laptop that could.

This morning I was reading an article in Businessweek about the OLPC's innovative UI (which the guys tell me was apparently shown on a real X0 at Pycon this year [it's mostly written in Python]) which talks about how innovative the UI is because it abandons a lot of the WIMP metaphor we've been stuck with for the past 30 years.

While I am all for innovative interfaces, I wonder if starting with the world's poor is the best approach to take. It's not that I don't think that an OLPC alum couldn't pick up a WIMP interface very quickly (after all my first "computer" was a Milton-Bradley Bigtrac and that helped me understand programming probably more than any other single toy I had growing up)— it's just that building up a whole new set of interaction primitives seems like a big risk to take on an audience which is already taking on a lot in using the OLPC in the first place. It's taken 30 years to polish windows, menus, and gestures (which of course the OLPC team will no doubt leverage experience from) and it seems a little strange to dump it in favor of something radically different.

Plus, I'm not sure that fancy New York graphic design firms (the article talks about how Pentagram is doing design for the OLPC) are best positioned to take on this job. After all, even the folks at Apple cribbed heavily from Xerox PARC back in the day.

However, I've learned my lesson with the OLPC and my pragmatic cynicism, and am thus optimistically awaiting the release of Sugar and the X0.

Comments Permalink

Adobe on a tear

In further helping to middle the line between desktop and web, Adobe held an event this week to showcase the promise of the Apollo platform. For those that don't know, Apollo seems to be the Flash runtime bundled with an HTML renderer and Javascript VM in a desktop application harness. It's supposed to allow developers to write hybrid web/desktop applications that can run offline and take advantage of local services.

Then just yesterday, Adobe's CEO announced that they are going to launch a hosted web-based version of Photoshop for those "light-weight" photo editing tasks.

I continue to scratch my head over the Apollo platform mostly because it seems so incredibly ambitious and because I really do have a hard time understanding whether it is going to do anything meaningful for adoption (the real problem that rich client software which does not ship on the platform has these days).

My guess would be that the devil will be in the details— after all, the JVM could have owned this layer on the client 10 years ago if a) it wasn't a 10MB download, b) it didn't take 45 seconds to boot, and c) it didn't run and look like a pig. Instead Flash beat it to the punch because it was less that 1MB and much less ambitious. Less is more— which is what is also something that is weird about Apollo. Why dial the ambition back up when they could do so much by just continuing to extend Flash?

As I think about a site like Tabblo, I realize that we would just love to see Apollo deployed on every computer— our users constantly have to struggle with the pain of crossing the desktop-web membrane with their big photos, our engineering team is well-trained in the ways of the browser frame and ECMAscript/Javascript, and there is tons we'd love to see done with the local CPU that we could completely offload from our image front-ends. At the same time I have a hard time believing that if this was going to such a huge win for us, we wouldn't find other clever ways of putting a footprint down on the desktop (see this clever OSX-specific way to run a browser frame as a full flown application).

And while I am on the devil in the details, one huge win from Adobe betting on Apollo internally could be a properly instrumented version of Online Photoshop that sites like Tabblo could easily embed into our experience. We've had tons of inbound interest to partner with the myriad of "online photo editors," that are out and while the promise is always there, for the most part, startups are like mosquitoes looking to sting: not all that likely to work for all when done in groups. On the other hand, easily being able to integrate with the 800-lb gorilla is a tide that would truly lift all boats.

Comments Permalink

Though I am really happy to see Google experimenting with revenue models outside of advertising, yesterday's launch of their premium business applications left me thinking that they are either a) gleeful about the possibility of putting a stick in Microsoft's eye or b) not yet clued in to what makes things work on the web if they don't have a search box in them.

Software as a service (SaaS) delivered in the form of dynamic and rich web applications is a really great thing— in fact probably the most significant thing to happen on the Internet since the coming of the web itself. However this does not mean that every possible thing someone wants to do with a PC can be crammed down the HTTP-pipe and decorated with pretty Javascript effects. Below are some of the standard reasons:

  1. FIOS-enabled homes and offices notwithstanding, there is still just too much latency on the Internet, plain and simple. This is the main reason why taking any old desktop application and webifying it usually doesn't work. Word is faster than Writely, Excel is speedier that Google spreadsheets, and no matter how hard we may try, iPhoto or Picasa will always be faster than Tabblo for manipulating photos. Therefore, if you've got an application which sits open on your desktop all day ready for you to edit, compose, and otherwise author 20-50 times a day as is the case with Word, Excel, and Outlook for most office workers, taking that online is a big bet to make.

  2. There are things you just need calls into the OS for which most modern browsers do not give you access to yet. For instance, office applications often produce documents that people want to print, and yet most browser-based printing is still stuck in the stone ages (how many times have your printed Mapquest directions only to get that hanging chad of a last turn on the last page?) Ditto for really rich APIs into other sources of data that live on the local filesystem (Outlook pst files, OSX Spotlight index), or even for rich access to the local filesystem itself. Try as we might, if you have things that you need to either source from the local disk or output to the local peripherals (printers, CD burners), the browser is not your friend. Interestingly enough, Adobe's Apollo project may solve this (a big "may" though as many have tried).

  3. Where the data lives is a pretty important thing to think through, especially if you are a business. Sure no one backs things up properly, and for sure your office is more likely to be burglarized, burned down, etc. than a world-class datacenter, but for most people knowing that the data is under their control is more important at times than the data itself. Sure, a service provider can encrypt the data and partition it accordingly, but in much the same way that big financial institutions with liability exposure don't allow their employees to use standard IM, I suspect most big companies will be leery of trusting Google with sensitive, mission critical data. On the consumer side this is also a problem, albeit one that is mitigated by the fact that most consumer data that makes is to the web is not as sensitive (and the fact remains that most savvy consumers see uploading the data to a service as a poor man's backup).

These reasons by themselves should serve as powerful motivators for thinking carefully about trying to move any major desktop application to the web. If an application is going to take on the encumbrances mentioned above, the benefit of living on the network have got to be very high— in terms of ubiquitous access, collaboration, or best of all, the symbiotic relationship that the application can have with its users as it grows up.

Ephraim Schwartz interviewed me about Tabblo recently and wrote a nice piece on this co-development process where I make all sorts of bold claims about the productivity improvements that come from having an online app that lives and grows directly based on the use patterns of the community around it (which is itself growing). That same thin HTTP pipe I mentioned as a problem above becomes your best friend in this regard— by serializing every action into a very digestible set of log entries for subsequent analysis, it gives one a much better real-time view of what is working and what isn't. And because the user-facing application runtime is the web browser, UI flows can be changed near instantly without having to redeploy to an installed base.

The overall mental image I have of the process is that of an acelerated time-lapse movie of coral growing according to its environment and the actions of its co-habitants.

The main problem with trying to grow a coral from a word processor, a spreadsheet, or an email client is that the specs for these products are fairly known and have been pretty fixed in users' minds for about a decade now. Witness Gmail— every time I hear complaints about it, it is from someone who comes from the Outlook worldview and is almost certainly around the most innovative (and web-native) parts of the interface. The patterns are already well-worn so it becomes difficult for the application/community to take on a life of its own.

Paul Graham wrote an essay a while ago about Web 2.0 that argued that Google was succeeding because it was aligned with the "grain of the web." I completely agree which is why it is strange that they would use the office suite as their first beachhead into for-pay SaaS.

Comments Permalink

All of this hoopla over the new releases of PC operating systems has been bothering me lately, mostly because it's made me think back 10 years to when Windows 95 was released, or even 5 to when Mac OS X first shipped, and think about why today the releases feel like such non-events. Just the other day I was struck by an eager teenager who excitedly tabbloed his Vista unboxing, and at the office they have been relentless about some Vista-related quote I gave an AP writer (mostly because I just really don't care about Vista or its impact on our "lab").

Even this year's MacWorld— usually replete with pronouncements about how OSX is going to change the face of personal computing by introducing features which are long overdue on most client operating systems— was bereft of even a single OSX-related announcement. Craig Syverson over at Venture Cast had an interesting thought on this that got me thinking along a different line: he basically argued that the future of the Mac OS ("Mac OS XI" as he called it) was really iTunes in that more and more of what is relevant to users (media, iPods, mobile phones) was going to start to flow through iTunes, whether on the Mac or on Windows. In this case then, for media hungry consumers, iTunes is the new runtime and everything underneath it really is just a bunch of buggy device drivers.

The geek in me bristles at that, first and foremost because of how closed the whole iTunes ecosystem (including the forthcoming iPhone) is relative to POSIX, Win32, and even OSX. Even the relatively closed cellphone runtimes appear open as a commune by comparison. That said, plenty of valiant startups are finding ways to hack into iTunes to extract metadata and insert themselves into the flow of media— so if the desire is there and the resulting user experience doesn't end up being too encumbered, I'm sure that enterprising and curious geeks will find a way to make Apple's media-based OS XI a more open system.

A more relevant reason as to why OS releases are no irrelevant (hello Marc Andreesen?) is that all of the interesting things you can do with computers now (outside of specialized content creation like programs, video, music, etc.) has little to do with the OS itself unless you count the bits required to run a fast (and standards-compliant) web browser. I first heard Tim O'Reilly articulate this 4 years ago in a talk on the web as platform, but it has become dramatically more true with the development of Web 2.0.

Just this morning, I ran across a YouTube video that really captures the underlying sense of wonder in the possibility of it all when we start thinking of the network as the relevant runtime for innovation. After watching it, I'm sure you will come away thinking that the real innovation these days is as far from a shrink-wrapped box of device drivers as internal combustion is from a barrel of feed.

(the video was made by Michael Wesch, an anthropology professor, and came to me via Frank Gruber).

I highly recommend this video to any of the new web naysayers who think that the biggest things in the web over the last 5 years have been the return of pastels, rounded rects., and XmlHttpRequest replacing hidden iframes. Though it is gimmicky at points, it does a wonderful job of communicating why the folks on the leading edge get so excited about what's been happening in Silicon Valley over the last couple of years.

Update: A sadder but potentially more impactful of example of why the web-as-platform is so much more compelling than 3-D shading on windows and buttons is the search for Jim Gray via the use of a lot of the work/collaboration patterns that have really caught on in the last couple of of years.

Comments Permalink