(this is page 109 of 121)





Latest

Making it stick

I really dig digg. I remember being at our VC's offices the day that the deal came in and thinking only one thing: wow this is going to be the end of Slashdot. But Seth Godin has recently written a brief but interesting piece about the challenges facing everyone's new media darling these days. In short, he argues that Digg is about the diggers and not so much about the larger community of readers that Kevin & co. like to talk about when the cite 900K uniques per day.

The problem with the diggers according to Seth? They are a "legion," an elite, and as such you have to treat them with kid gloves and manage them like talent. In my opinion, the real problem is that Digg as a site is built around too few publishers doing too little work to build the "media experience." To take an extreme on the other end, compare the diggers to your average World of Warcraft player and think for a moment: who is more likely to move elsewhere in the event that the guy running the hosting platform pulls a fast one? If I'm a digger, all I've invested in learning is the old thumbs-up/thumbs-down deal. How hard can this be to port to Reddit? If I'm a WoW player though, I know about my guild, I know about the 5 second rule, and most of all, I know a lot about the creative investment that I've made in my character(s).

If you're going to make a new media property, and if you're going to call it sticky, it seems to me that it makes sense to understand the nature of the creative investment you expect your users to make. Now, digg that!

Comments Permalink

Loving that cheap laptop

A long time ago in a faraway blog, I spent some time arguing that providing really cheap computers would have a really positive impact on society. Fast forward a year when at the Wall Street Journal's D4 conference Nicholas Negroponte got up and talked about the $100 PC for poor countries and I wrote that it seemed silly that he was spending all of this alpha geek energy designing something from scratch when there were plenty of cheap components that could be used to get mighty close to the price target. Well it's been a year, the OLPC (One Laptop Per Child) initiative has made good progress, and I guess it's time to color me wrong.

What I had not realized was how brainwashed I was by existing form factors in PCs/laptops, and how much innovation could truly be achieved by starting from scratch and designing the hardware so that it hit the right price/features/performance point. And to boot, getting luminaries like Alan Kay (and even Python's very own GvR because as it turns out a bunch of the GUI has been wrapped for quick dev. with Python) involved has definitely been good for the project, and I didn't realize just how many would jump on board.

But actually, outside of the progress that they've made in one short year, the thing that has most convinced me that going with a brand new hardware platform was the key was getting a Nintendo DS Lite, essentially a portable game player with a lot of clever design in it and the unbelievable price tag of $129 (for a computer with two displays, enough processing power to run a number of fun games and a wireless radio in it). Now I know we're supposed to think that all game manufacturers do the "blades and razors" thing and give away the console in order to make it up with the games, but I seriously doubt that Nintendo is really losing much money on every DS-Lite. And seeing it run for hours on a charge, dropping it several times on hard surfaces with no serious effect, and most significantly seeing how the most clever of games uses innovative input methods to enable gameplay (a graffiti-like character recognizer and even better, a microphone), that made me think of the $100 laptop again, and the promise that it could bring.

I still have my doubts as far as OLPC goes. Despite a seemingly well thought-out process for building software, and the aforementioned software gurus, I worry that the apps on it may stink. I worry that there may be hardware/software integration issues that require the concentration and effort of a single product management organization making trade-offs and compromises in the right direction. Perhpas now that these guys have been outed as being a world-class hardware manufacturer, maybe they could jump in and try to help?

But I do have to give it to Negroponte for thinking big, and getting out there to sell it big as well.

Comments Permalink

I've been following the raging debate around the alpha geeks who are dumping OSX for Ubuntu (and the beta geeks who are making a stink about following them) with some of the same detached interest that I save for the Ruby-Python debate or the emacs-vi throwdown of yesteryear. Mostly because there are only two good points being made over and over again, with the rest of the chatter being just line noise.

The whole thing started when Mark Pilgrim (who writes as well as he thinks and thinks very well) wrote about how he was switching to Linux from OSX due to Apple's braindead proprietary data formats in their iLife suite. And herein is great point #1: proprietary data formats suck, especially as more and more of your critical information (photos, movies, music) migrates on to your computer. You will always run into some kind of artificial roadblock that the vendor (in this case Apple) cares little about helping you with because when you're running into the problem, it is either because you want to leave their "ecosystem" or too far in the future for it to be worth their worry.

The important thing to keep in mind though is that Mark is talking about metadata that is being locked up in a propietary way, not actual data. Yes it would suck to lose your iTunes playlists, and your iPhoto albums/tags/comments, but it definitely would suck a lot more to lose all of your data due to lock-in (hello Outlook at PST fans!?!), and at least thus far, Apple has been good about keeping that data visible and transparent to common filesystem tools. While they keep that up, I think they've still got the best platform out there.

Why? Because of point #2: running Linux on a desktop/laptop blows, plain and simple. The debate raging in the blogosphere would be a lot more information-rich if Technorati provided a filter that let you remove posts from anyone who has never actually run Linux on a laptop before, and by running it, I mean using it as their main OS in day to day activity. I did it for two years (about three years ago) and I can honestly say that the only way you could talk about it favorably is if you were suffering from Stockholm syndrome. It's just no fun to deal with power management (especially around suspend/resume), video issues, font issues, and wireless networking issues. True, Ubuntu has made great strides, but having recently installed it on an IBM T43, I can still see all of the same holes that have always existed around "user-centered Linux distros," the main one being around the way that GUI configurators and the textfiles they twiddle can get out of state and send you right into a commandline/manpage hell. This is ok for ifconfig (because you should know this anyway) but for X? for apm? C'mon, almost anyone has better things to do with their time. (Rob Flickenger has the best blogpost outlining the issues as to why Linux is just not viable and he touches on a number of things that I don't mention here for those who are curious).

So, what to do? Get ready to lose your metadata (read: don't invest a lot of energy in it) and make sure you practice good platform independence hygene for the possible moment when Apple drives us all off the cliff. Learn how the iApps store your data, and get really cozy with rsync and ssh (investing time in these two tools will pay off for far longer than investing energy into configuring X fonts or Alsa sound drivers). I used to think that good platform independence hygene meant not using applications that weren't available on all platforms which is the main reason why I kept running all those buggy versions of Aqua Emacs but after years of pain I finally said basta! and got on the Cocoa groove train. Now I live in TextMate and NetNewsWire and am fully expecting the coming withdrawal that may come someday. I'm not sure it's worth punishing yourself now for true platform independence.

Anyhow, I realize this debate has probably been spent (for now anyway, as it seems to come back every six months) but I figured it would make a good Independence day post, so happy 4th!

Comments Permalink

Discovering the platform

Businessweek has a sensationalist piece, "So much fanfare so few hits," that argues that Google seems to just toss these half-finished products out there that don't do nearly as well as their core search product, and that as such competitors should stop worrying about them as the "new Microsoft/IBM." After the piece hit the blogopshere, others piled on with arguments about Google's poor marketing and even worse product management to second the opinion that the company really was a one-trick pony. Scoble has even jumped in and suggested that their lack of attendance at Gnomedex may be a sign of some bigger slip.

It takes time to build a new platform people, and we should all be as lucky as Google to be able to afford to have so many irons in the fire. The approach they have taken has two clear benefits that people involved in the discussion don't mention explicitly. First, it is clear that the world has changed, and that webapps running inside of the browser are the new platform. You don't have to look further than the amount of interest a small little startup like Tabblo has garnered in places like the Wall Street Journal (or fittingly enough alongside Google in the Washington Post a few days later) to see that it's suddenly interesting to regular folks when a company stands up and says: we believe we can do formerly desktop-bound activity X better, and we are betting you will think so too. All sorts of companies with products big and small are coming on to the map with online replacements for everything from IM to spreadsheets, and users are signing up. So in that sense, just having something out there in the field is a good idea even if the offering is not fully baked.

The second advantage of taking this approach is that the best hackers are always itching to work on the up-and-coming platform and right now the biggest nucleus of this activity is at Google. We engineers are just notorious about loving the conceptualization phase, the architecture phase, and that initial burst of hacking to get features done, and in that sense a company where you can be constantly launching new products that have in-built audiences in the millions is just like crack for the Google hackers. What we're not so good at is putting the finishing touches on things: triaging bugs, collecting customer feedback, and getting iterations in that don't move the feature set forward but make the product easier/better/faster (which incidentally is why I am proud that we made it out of beta in 45 days at Tabblo) but this is where good product management and discipline can really help.

And herein lies the piece of the discussion that I did agree with: it seems like Google could really benefit from better product management. It's not glamorous– and it certainly won't get the press– but at some point people will/will not switch from Yahoo Mail or MSN Messenger based on the feel of the app, and no amount of good PR will do that for you. Given Google's late entrance into a bunch of these categories: mail, news, finance, etc., they have to keep in mind that they do need to play a game of share-shifting instead of new market growth when it comes to users.

The analogy I was going to make in disagreeing with this piece was between Google now and Microsoft in the late 80s/90s, and around how Microsoft also had poor product management around some of its products (Access, Word, Encarta, etc.), and managed to win just by staking claims and plodding forward, but I'm not as sure of it now, mostly because in the case of a lot of Microsoft products, the game was not about share-shifting so much as giving users who had not been exposed a chance to play with new functionality (by contrast, I'm fairly sure that anyone on the Internet who wants web-based email has already tried at least one of the services).

Product management can be learned however, so it seems to me that this will just be a matter of time for Google. After all, they could raid one of their dinosaur neighbors (say Intuit) who has limited prospects but plenty of grade-A product managers. And when they get that under control, shareholders and pundits alike will be happy that Google staked all of these claims in categories where it did not seem like the clear and early winner.

In the meanwhile, just give them a little time to discover just where the boundaries to this new exciting platform really are.

Comments Permalink

Pete blogs some interesting HitWise stats released into the blogosphere today by LeeAnn Prescott about how Photobucket is the #1 photo site by traffic, and poor "little" Flickr is only #6.

Comparing Photobucket to Flickr is like comparing one of those cheesy $5.95/month hosting packages you can buy from a zillion different hosting companies to MySpace. In both places you can create a profile and post it, and you can even use all the same funky styles. But no one would ever look at your page on XYZ-Cheaphost and confuse it with MySpace even though they both contain just about the same content.

On the web, there are two things that make up an "application:" a relatively robust set of tools that are provided for the user to "do something" (socializing, photo-sharing, etc.), and the community that grows up around these tools. In the desktop days you just needed the former, but in the web days it seems to me that if you don't have the latter, you're just a piece of infrastructure that can get sucked into some other webapp. In this case, Photobucket seems like a piece of infrastructure that is used by MySpace users to plug a clear hole in functionality.

Not that I have anything against Photobucket– after all they are the clear leader in their infrastructure category. They've managed to turn the crappy business of webhosting into something that seems to make money with just a teeny functionality twist and a new business model. But when Om writes that they won because of "simplicity" or giving the users what they want, I'm left wondering what it is exactly that they've won. MySpace (or CNET for that matter with their new All you can upload) could probably seriously put a dent in their growth curve by simply implementing that little bit of functionality. And if they get too intrusive with their collection of demographic data or their ads, some new entrant may decide that there is just room for the free-and-anonymous version of Photobucket.

It's interesting to think back to when Flickr first launched. I remember thinking: well this is ok, but I'm missing albums and photo effects, and invites, just for starters– there is no way I'm going to use this given how many other places I can go post a photo. But since then they've grown tags, a community, and a whole bunch of new stuff to entice, encourage, and otherwise entertain their loyal users. Will Photobucket have the same opportunity the grow functionality with its community the way Flickr did? Maybe. A look at their frontpage seems to show that they are moving in that direction. The challenge though is any app work they now do they have to undertake with a datacenter full of servers that is being pounded with request for photos on MySpace, and sometimes the weight of this makes you slow. It's why we don't worry too much about places like Kodak gallery coming after us at Tabblo– even with hundreds of engineers, they've got to deal with 3 billion photos and over 10 million users while we deal with... a whole lot less.

In the meantime, this whole Photobucket vs. Flickr discussion seems to me to be a good place to drop the old adage about how comparisons are odious.

Comments Permalink