Interview with Watson's Dan Woodby Derrick Story
Author's note: This interview with Dan Wood, chief architect of Watson, is the first in a new collection of articles we're branding as "Developing for Mac OS X." In this ongoing series we'll cover the ins and outs of how to successfully bring your ideas to the marketplace, from both a technical and business perspective.
It's appropriate to launch this endeavor by publishing a conversation with Dan Wood, who has achieved great respect among Mac users and developers alike for bringing Watson to our computers, then continuing to innovate as competition increased.
Derrick Story: Hello Dan. Thanks for taking time to visit with me and our audience here at the Mac DevCenter. I've noticed from the Karelia site that Watson 1.5.5 is available for download, and it has some impressive new features. But before we get to Watson itself, I'd like a little more information about Karelia and your role in the company.
Let's start with Karelia. The home page says that it's a region in Finland and Russia, and that the company name is inspired by the Karelia Suite, a classical composition by Jean Sibelius. Could you tell us the story about how this became the name of a Mac software company?
Dan Wood: Well, we hired a very expensive naming consultant, who convinced us that the new trend in software company naming is the classical music motif. Seriously, it was a domain name I had picked out for my own personal use several years ago. When I was looking for a company name, I decided to turn that into a company name, rather than having to hunt for a reasonable domain name in today's crowded namespace.
DS: And what's your role in the company these days?
DW: I'm still the chief architect of Watson, and I still do programming on it, although I've brought in another talented Cocoa programmer to work on our latest plug-ins. I hire others who do the other pieces like icon design and marketing on our Web site. I'm designing a new product that I hope to have ready early next year. Lately I've been spending a bit of time talking with other companies about partnerships that will help us move Watson to new levels. Oh, and I also find time to write some technical articles for MacTech magazine.
DS: So tell us a little bit about the inspiration for Watson, and how you continue to muster the energy to go toe to toe with Sherlock?
DW: Late last year I was looking for ideas for a program to build in Cocoa. I was inspired by one of the keynotes at Apple's developer conference that talked about "Deep Internet Integration." I had run across some small utilities that did web "scraping" (extracting and reformatting useful data from HTML pages) such as monitoring eBay auctions and collecting headlines of SlashDot.org. I decided that the world needed a handy container application for these kinds of utilities, and from there the individual tool ideas started coming left and right. Somewhere along the lines I recognized that this kind of program was to services what Sherlock was to searching. So I came up with the name Watson to complement Sherlock and to help people understand what the program was all about.
DS: Elementary...and brilliant!
DW: As far as having to compete with Sherlock 3, well, originally it looked like I was just going to have to put Watson into maintenance mode and accelerate the next project. But a few weeks before Jaguar shipped, when Apple developers were able to first experience Sherlock 3 for themselves, we started getting countless emails from users asking us not to give up on Watson because it's so much faster than Sherlock and has so much more functionality. So I decided to breathe some new life into Watson. I figured that since Sherlock had moved into the services game, not just in general, but pretty much all of the specific services that Watson has provided, that it made sense to add general Internet search capabilities to Watson as well. Hence the new Google searching tool. So it's really our user community that has given me the energy!
DS: What are the features about Watson that excite you most?
DW: Well, I've been a fan of good user interfaces, which is why I've stuck with the Mac through the dark times. And I love what the Web has done to affect people's lives, but I hate its non-standardized, minimalist user interface. In a sense, the Web is a great big "dumb terminal" with fonts and graphics. Using the Web, I yearn for the subtle user interface behaviors and consistent controls you get in a real desktop application,like buttons enabling and disabling when it's appropriate to use them, scrollable lists, dynamically adjusting displays, things like that. To me, Watson is a way of taking back the great user experience that the Mac perfected. I still get a kick out of zipping through a site using Watson's columns browser that would otherwise require page after page after page on my browser.
DS: Well, not to pile on here, but I've heard lots of developers complain about the Web experience, but I have to say, the Watson interface really leaves the browser in the dust for certain online activities. In large part, I think many people will agree with me that you've set a new standard.
DS: That being said, I'd like to shift gears here for a second. We all know about the stir caused when Sherlock 3 was released right after Apple awarded Watson the "Most Innovative Mac OS X Product" for 2002. Many people felt, myself included, that Apple should have handled the situation better. But they didn't, and Sherlock 3 sure looks like it borrowed much from Watson without any formal acknowledgment.
DS: My question to you is, based on your experiences, what suggestions do you have for Apple in terms of developer relations?
DW: Good question. I think Apple has a long way to go in terms of developer relations. Apple has helped some companies build themselves up, but others they have harmed greatly. From stories I've heard from other developers, the Sherlock/Watson issue is just the tip of the iceberg. I respect Steve Jobs's desire to make the Mac the most useful tool it can possibly be, to win over converts from the Windows side, but instead, Apple seems to be nibbling at their own developer community. Perhaps there needs to be a better agreement that both parties enter to avoid these situations. Apple should be thinking win-win in terms of developer relations--helping companies build great software so that both Apple and those companies will succeed--but the reality seems to be "We'll provide you some help to make a product, but we might just bundle your ideas into our OS or our next iApp."
Pages: 1, 2