(this is page 78 of 121)





Latest

I attended one of Scott's Nantucket Conference dinners last night to chat on a panel about how Boston tech companies can get better at going after the consumer and thoroughly enjoyed the distinctively hardware-focused crowd that Scott assembled (present company excluded).

As the web becomes more pervasive in everyone's lives, it is hard to imagine that our main interface to it will be governed by laptops and mobile phones, which is why there are a small group of us who've grown up on the web who believe that the next generation of successful consumer startups will be forged at the intersection of hardware, software, and services. Of course this statement is anathema to today's VCs who hear the word hardware and think of the millions of dollars that they would have to invest to get a product with the fit and finish of an iPhone. In reality though, looking at it from this perspective is like looking at the enterprise storage startups with EMC as the yardstick, or the semantic search startups from the perspective of Google. Every jungle has its own 800lb gorilla and it's important not to assume that just because you've got hardware involved you can't be a small nimble monkey.

Witness Bug Labs. Or even the Arduino community effort. On the panel last night, the highlight for me was Carl Yankowski, CEO of Ambient Devices and former senior exec from just about every company that's ever wrapped plastic around a chip. When I asked the panel how being in the hardware business with its relatively long product lead times, they could ever hope to achieve the same tight feedback loop that you get in building webapps, he told me that in his view hardware and software development had gotten to parity in terms of time-to-market, capital investment, etc.

Carl YankowskiWhile this may be hard to believe in products as complex as the iPhone, with Carl's current products at Ambient, this fast pace can be a reality. In the picture, he is holding an umbrella whose flashing LEDs communicate Accuweather information about the chance of likely precipitation (you can't see it from the picture but it was blinking at Cylon speeds last night).

The simplicity (or "dedicated purpose") of these products really does point the way forward for injecting network intelligence into things beyond the three primary screens in our lives (the PC, the TV, and the mobile). The elusive hunt for a generic "4th screen" on the part of investors and entrepreneurs seems to yield a number of dumb photo frame investments (trust me we see them when they run out of cash and want to be bought), or at best, products that are fundamentally flawed in their attempt at flexibility (witness the Chumby).

To borrow another one of Carl's insights last night: it's about wrapping hardware around individual applications (email, weather, sports scores, etc.) if what you are looking for is mass-market traction. To this point, I enjoyed hearing his stories about his time at Palm and particularly some of these hardware-wrapped applications that didn't see the light of day. It reminded me that there is indeed tons of opportunity to wrap a few more applications with net-intelligent hardware.

Comments Permalink

Rich Internet Browsers

Almost one year in, one of the biggest surprises about my new execujob is how little I've come to like the senior "technology architecture & strategy" discussions that I'm invited to sit in on. I had originally thought that being at the biggest tech company in the world would provide some unique perspective on the hot topics of the day (cloud computing, green computing, the semantic web, the blurring of the desktop and the web) that you wouldn't get out in the wild. In reality all I've done is develop an ability to breathe in really shallow atmosphere situations, as most of these discussions take place at such high altitude that I've taken to bringing Kleenex in order to stem the nosebleeds.

Naturally one of the hottest topics these days is the definition of the runtime for the next generation of Internet applications. With Microsoft and Adobe and their vendor sports death match (Silverlight versus AIR) fueling most of the recent debate, and Google/Yahoo/everyone else who matters looking to get more life out of the heavy server/light browser architecture that has become predominant over the last 10 years, it should actually be an interesting discussion.

But alas at 100,000 feet, all of the platform tradeoffs look like small dots in the distance. Everyone's got their favorite example: Microsoft is pushing the whole rich interactivity concept with their zoomable Hard Rock demo (and upcoming Olympics Silverlight-based coverage), and just today Adobe has entered their canonical example into the ring with Photoshop Express. I'm personally much more interested in every day applications that regular folks have gotten used to compromising on, either in their desktop version, or in their browser-based one. Apps like: email, instant messaging, or even word processing.

When considering the web versions of these guys, everyone gravitates towards the offline story because that is the place where the current generation of web-based applications falls down most dramatically. However, with every browser vendor embedding SQLite and efforts like Google Gears well underway, and with the ever expanding reach of the network into every offline nook and cranny, it is unlikely that this will remain a problem for much longer.

Where there tradeoffs get more interesting however, is when it comes to desktop integration. It is ridiculous that 24 years into the evolution of the GUI, the browser makes us take a step back when it comes to simple things like uploading files to a web service or slightly more ambitious ones like integrating across applications. Yet that is exactly where we find ourselves today.

To see how much I missed proper desktop integration in my everyday consumption of one of these apps (Gmail), I recently downloaded a $25 OS X program called Mailplane which puts a very thin rich client wrapper around the Gmail experience. Ideally this is the kind of thing that Google itself could build with something like AIR or Silverlight but while those guys take their time getting to the useful applications (instead of the eye-catching ones), I figured I would skip to the blended desktop/web future by tinkering with Mailplane.

My conclusion (after two weeks): integration really does make for a much better experience. Here are the things that Mailplane does that make me feel happier:

1. All of the standard keyboard shortcuts work as you would expect (i.e., command-N gives me a new message)
2. Inter-application stuff works as expected as well (i.e., "Mail this link" opens a new message in Mailplane with the link in the body)
3. Notification works: on OS X, the incredibly useful Growl notification system can show incoming/outgoing messages like Outlook does along with the icon in the Dock showing the number of new messages)
4. File attachment works as well: unlike the goofy behavior that most web browsers implement when you drop a file on them (to open said file), dropping a file into Mailplane results in it being attached to the outgoing email. This is a huge deal, especially as we rely more on apps and less on the Finder/Explorer to wrangle our data.

There are two downsides to Mailplane. First, because it spins up a separate process with a browser in it (an embedded version of Webkit), it does consume RAM galore, especially in an AJAX-heavy webapp like Gmail). More importantly however, it is a traditional desktop application which means that in this case you have to pay ($25 per seat seems a bit steep in today's world) and that your app preferences are ghettoed in the client computer that you originally installed it on. Ideally, the rich runtimes would help to solve both of these problems.

While researching whether there might be something better out there that might address some of these shortcomings, I ran into this Mozilla Prism inspired project, Fluid, which allows you to create site-specific browsers that approach some of the same functionality that Mailplane provides (through the embedded Greasemonkey functionality). As I played with this "Site Specific Browser" approach however, I found that I wasn't getting enough of 1-4 to make it any better than keeping these webapps in separate tabs.

Here's what I'd love to author of Fluid to do (or some other such force out there on the Lazy Web): wrap a Javascript API around each of my points above so that if a website (or even a user via the built in Greasemonkey functionality) wanted to implement notifications or file uploads or whatever, it would be as easy as testing for the presence of the objects in Javascript and writing to their Javascript API. With a little luck, and a Windows version, you might get some serious traction with a project like this.

I first heard about this custom browser approach when Flock (remember the "social browser") first launched a couple of years ago and found it utterly idiotic that someone might replace their browser with one of these tweaked out custom jobs. But I've got to admit that using Mailplane has made me reconsider.

Or maybe it's just all of that lack of oxygen...

Update: It turns out that Fluid is making nice progress to exactly what I was asking for already as you can see from their developer page. The big missing feature for me at this point is webapps being able to register for keyboard commands (think command-N for new Message not new instance of Gmail).

Comments Permalink

Mobile MondayTurns out that if you mess around at all with dynamic web applications on the iPhone, you will suck its battery dry faster than you can hum the little do-da-dee song that Apple plays on the commercials. Like a bunch of other misguided folks that come from the world of watt-sucking laptops and servers, I have been thinking that this has to do with the use of XMLHttpRequest to poll for new content. But as I learned tonight from a clueful engineer at the Boston Momo event (Mobile Monday), a gathering of folks of all stripes interested in mobile, it turns out that the using the radio to send/receive IP packets is relatively cheap from a power perspective, especially when compared to running the CPU at Safari-induced speeds or even keeping the display on for prolonged periods of time.

That alone was worth the trip to Momo, especially because in the aftermath of Apple launching the SDK, there seem to be loads of folks commenting on the lack of background processing for user-developed applications (supposedly the big Achilles heel to sanctioned development for the iPhone) in only semi-informed ways. For instance, this otherwise solid post mistakenly argues exactly what I thought: that applications that indiscriminately used the network to poll servers in the background would be death for the battery thus forcing Apple to impose the "no background processing" rule.

It struck me last night that there are two different generations of folks attending events like this Momo gathering that are in need of retraining as we all get ready to embrace mobile— at least here in the Boston area. On the one hand, you've got all of the enterprise folks; broadly speaking these are the Digital/Lotus people that came out of minicomputers and PCs and mostly bypassed the web in favor of sucking Fortune 500 companies dry with ornate pieces of "industrial strength" software that did X, Y, or Z (and whose market is getting decimated by the combination of open source and SaaS). Then you've got all of the web folk (where I'd put myself) who have grown up with the web at the center of everything they've worked on. In both camps however, the lessons of the last decades have never forced us to deal with power-constrained devices which require a whole new discipline around opening sockets, powering the display, or even just using CPU cycles to do something as trivial as running a web browser.

And power consumption is just the first step on this steep learning curve: you've also got much smaller screens and applications whose total use cases need to be measured in 5-30 second interactive chunks. Overall it's going to be a huge mind shift for hackers, product managers—makers of all types— especially as devices like the iPhone put mobile computing into the hands of mainstream users.

Very very fun stuff.

Comments Permalink

The Economist has a great piece this week on what will undoubtedly come to be known as the "Facebook dilemma:" the fact that social networking is both a fun and useful activity for most folks but utterly impossible to make money from. The piece effectively argues that just as with email and IM, the basic verbs and nouns of social networking (friending and the nodes of the social graph) belong in every network-aware application and not just inside of these monetization ghettos created by VC-backed companies in attempt to mine for the next Google.

Making the comparison between Facebook and the AOL of yesteryear is something that has come up before, but is a rather apt way to look at the problem. The rest of the "open web" will build in social networky features and as they do, Facebook's only hope of staying relevant is to open up at a rate faster than AOL back in the day (which their app platform certainly does not do today). But of course as they do so, they will simultaneously limit the choices for their eyeballs-based business models.

And that right there is the challenge with huge horizontal plays in the Internet space— the more broadly applicable they are, the more they need to be baked into the fabric of the Internet and not held hostage by monetization theories. And in the absence of alternatives to the advertising based business models (other than e-commerce which seems to help the likes of Amazon & eBay build out very horizontal platforms), this dilemma is unlikely to be resolved anytime soon.

Comments Permalink

Steve Gillmor has a beautiful essay on the significance of Twitter which is well worth the read. In it, he explains the perfect storm situation that gave birth to the incredible success Twitter is experiencing. In his own words:

The key to this signalling network is the duality of Twitter posts - both personal and public in equal doses. Personal data such as what I'm reading or listening to conspire with public data such as what news is important to us and what news isn't to cut through the glut with surprising efficiency. Each of us has to perform an instant editorial calculation of the relative value of the data as divided by the nature of the cloud of followers into which the post is injected. Overlapping circles of influence and authority resonate like a pebble tossed in a smooth pond.

What results is an elastic and supple map of how to transit the information space, contoured by the relative effectiveness of the editorial agenda of each poster and its success at attracting the right audience. Just as the 140 character "limit" promotes clarity and focus, the decision to follow is not taken lightly for fear of upsetting the value of the aggregate flow by having it accelerate beyond the ability to absorb it. Each node must traverse a high wire between value and noise.

I've been looking at Twitter for the last two years trying to figure out why it is that despite its paltry featureset and it's extremely unreliable uptime there seems to be a core of something there that makes it more with "the grain of the (social) web" than anything else that's come along in the last 5 years. And it's great to see Steve nail it in his post (especially because so many other pundits have tried to feel this particular elephant in the dark to no avail).

Comments Permalink