(this is page 101 of 121)





Latest

Get that API on a diet

Having spent a bit of time thinking about developing APIs since the HP acquisition took place a few weeks ago, I was very amused by an ACM Queue piece, "APIs with an Appetite," which considers how APIs can get too fat too quickly.

In essence the piece argues that a well thought-out API will have just enough method calls to provide the intended functionality plus an "escape hatch" call which may be ugly but which plays a critical role. The example given is the UNIX file-access API with its 5 basic types of calls: open, close, write, read, and ioctl, the last being the escape hatch call which lets one pass almost any data structure down in the guts of the operating system and get almost anything back.

I've always thought of ioctl as the ugly stepchild which somehow broke with the elegance of the "stream of bites" abstraction of its four siblings. And yet, as the article argues, it is precisely ioctl's ugliness that allowed the rest of the API to remain so pure while still actually being useful.

It's interesting to consider this design approach in the newly emerging set of web service APIs. The Flickr API is the posterchild for the new web and yet, while the API is quite useful, the author of the ACM piece may consider it "fat." After all, there are a bunch of repeated methods for dealing with collections of things: photos, people, sets, etc. And yet, each of the method families belongs to a different namespace and returns slightly different data structures.

This short piece is definitely worth reading for anyone working on web service APIs. The final point about monitoring the use of the escape hatch call and learning from it how to evolve the API is perhaps most applicable in the web environment (where everything is centrally logged for later study). As the coolness of just having an API fades and is replaced with an explosion of services and APIs, we'd be well served to take this piece to heart.

(via Phil Windley)

Comments Permalink

Dilemmas and innovation

There was a great article about our new owners in today's New York Times which is a great read if you are interested in the internals of HP and the future of printing. Of course it elicited a bunch of emails from my joker friends wishing me well in what seems to be an epic battle as people consume less paper and more screen.

What is most interesting to me is a point which VJ makes in the piece about how most companies don't innovate when they are on top, but rather when they are struggling at the bottom of the heap. One of the most exciting things about Tabblo being part of the new strategy is that we get to take part in the strategy from this rather unique vantage point.

Today Apple shipped its 100 millionth iPod. This is a wild and crazy success and yet it's interesting to think that HP's installed base of home printers is significantly larger than this. Is Apple thinking about what comes after the iPod and are they willing to swing hard to get there?(1) Is Google making acquisitions around what might come after AdWords? Does Microsoft really want to make a product bet on web-based software?

Christensen's Innovator's Dilemma is supposed to be business-101 for anyone working in technology. It's good to see that my new bosses have actually read it.

(1) iPhone? Maybe, not clear yet.

Comments Permalink

In what is a great example of how Digg/Reddit have made blog post titles irrelevant, Paul Graham has a piece called "Microsoft is dead" which is really much more about how they are now irrelevant. The thrust of his argument is that Google and AJAX make their platform irrelevant for new hackers.

Fun stuff, appropriately lambasted by wizened veterans like Dave Winer and Don Dodge and put properly in the context of "Rich Internet Applications" by Ryan Stewart. So rather than plumb the depths of the argument, I wanted to keep the plane at 30,000 feet:

For a platform strategy to be displaced (and this is what Microsoft has done brilliantly up until now), you need to have a new platform strategy and a viable economic model.

Are AJAX-enabled web applications enough? Not by themselves. It's cool to have a much richer experience in the browser but I doubt that this alone is discontinuous enough. Outlook web access was after all, the first AJAX-enabled web application, made by the very folks at Microsoft who this new platform is supposed to make irrelevant. Despite the portability advantages of data-in-the-cloud, turning the world of PCs into dumb terminals doesn't even necessarily feel like it is altogether a step forward in the evolution of personal computing.

However, there is something else that makes Web 2.0 a much better candidate as a full on platform: people. Tim O'Reilly has been writing about it for years, and plenty of others have jumped in; collective intelligence, smart mobs, folksonomies— however you label it, the idea that people can come together and trade, write encyclopedias, etc. is really powerful. I don't think we even know how to understand what this new people platform is really defined by, but we can see its outlines in examples emerging from the wild. For instance, Twittervision is a great example of an app built on the people platform.

That said, we still need the economic model to give the platform enough time to grow its ecosystem. Microsoft has had wonderful one here in software licensing. Open source has a pretty good one in the gift economy and ego/reputation (albeit not as good as Microsoft). Web 2.0 most definitely does not have a good economic model in "selling the feature to Google/Yahoo." Furthermore, it's not clear that the ad thing is going to work, especially as we see increasing returns to scale in the online ad networks, and try as we might, no non-content provider has yet to crack the subscription model on the consumer side.

Without a viable economic model, it will only be a matter of time before Microsoft and Google incorporate the features that make the people platform into their respective businesses and leave a vast wasteland of cynical folks capable of using pastels and rounding corners on rectangles. This stuff is really hard to get right; you need the platform shift (timing), the economic model (business), and the emergent ecosystem (developers) to work together for a long stretch of years. And no matter what the cool kids at Y-Combinator are worrying about these days, I'm not sure we've got all of the key ingredients in place.

As an aside, if you want to see a great example of someone who got this right on the money the last time around, go and listen to this long-ish talk by Bill Gates from 1989 when he talks about the PC ecosystem. He must have been in his mid-thirties at the time, and it is just amazing to hear how well he can navigate the level of detail up and down to paint a really cohesive vision of where personal computing was going back then.

Comments Permalink

A rocket for the plan

The Acela, Amtrak's high-speed train that runs the length of the eastern seaboard (and my favorite train ride in the world), makes an interesting stop in New Haven Connecticut. As you are heading north on the train, you will spend about 5 minutes stopped there during which the train will jiggle this way and that while something is being done to it. And then, zoom! the rest of the way to Boston, the train speeds at what feels like 150% of the speed that you had coming up to New Haven.

I've never know exactly what happens at that stop but in my cartoon imagination, I've always thought that the Amtrak guys must strap some sort of rockets to the top of the train.

Today is that day for Tabblo.

Five minutes ago, a press release went out that said that the Hewlett-Packard company is acquiring us to execute on their web-to-print strategy. Details of the deal were not disclosed, and I am not going to elaborate here, save for three facts:

  1. We (Tabblo and our investors) are very happy with the outcome
  2. We (Tabblo and the Tabblo community) are going to stay on board at HP executing on our combined strategy and building great products
  3. We (Tabblo and HP) are incredibly excited because it feels like someone is strapping that rocket to the top of the car

I think #3 is the reason why I am not simply feeling the "pheew, we're done" emotion that entrepreneurs talk about when they sell their companies. On the contrary, I'm itching to see just how fast we can make this train go now that we've got a rocket to boost the "print engine of the web" strategy. So stay tuned there.

On a more personal note, I could not be prouder to be joining HP. Growing up in Venezuela, HP and Apple were the two companies that represented everything that was great about the American entrepreneurial ethic both in terms of ingenuity and hard work. I still have the HP-29C my father gave me when we first got to the US (its programability got me into college), and have very fond memories of my struggles at Terman (the engineering building at Stanford that Hewlett and Packard gave in name of their mentor).

In short, I am really happy to be merging Tabblo's future plans with such an incredibly rich and long-lasting institution, and I'm really looking forward to what the future holds for us.

On that note, if you are from HP, please don't hesitate to drop me a note to introduce yourself at antonio -at- tabblo -dot- com.

Comments Permalink

Beam me up Scotty

Neil Gershenfeld has this really neat book called Fab about the coming era of "personal fabricators" which are sort of like printers for 3-dimensional objects. In it he argues that soon we will be using simplified CAD programs to design our own objects which we will then just print at home for use.

I think a big part of me loves the idea at the "Star Trek gut level" much in the same way that people loved the original Motorola Startac because it subconsciously reminded them of Captain Kirk's communicator. In the case of the personal fabricators, we're bringing to life the replicator— Gene Roddenberry's utopian answer to renewable resources poverty.

In the meantime, we've got the Tabblo PhotoCube :), the latest product in the Tabblo family. It's a personal favorite for two reasons:

First, it's the first product we are asking folks to build (print, cut, assemble) at home. Despite being outside to our original business model, I think that the PhotoCube captures a lot of the immediacy of the web in a much nicer way (see pictures I like, make them instantly into a 3-D physical world object). It does have that "some assembly required" quality, but in the world of makers, this is a feature and not a bug.

Second, the PhotoCube is great because in being 3-D, it does give one the illusion of being a sort of "matter transporter" where you can literally recreate the thing you've photographed as an object that sits on a desk. Obviously it's not the same dog/car/beach that was photographed, but it is fun to see 2-d facsimiles built back into three dimensions.

What are you waiting for? Go make a cube...

Comments Permalink