A touchscreen does not an iPhone make

December 2nd, 2008 . by mikepk

Gadget geeks love spec sheets. When the iphone was first released, many gadgeteers sneered at the device, no GPS? Insanse! No video? Crippled! No removable battery? Scandalous! 2MP camera? What a piece of crap!

When I first got the iPhone, and being of a technological bent, friends and acquaintances would ask me about the iPhone’s ‘revolutionary innovations’. Surprising many, I would say that there was little technically new or innovative with the iPhone. There were devices with touchscreens, browsers, email, etc… long before the iPhone. Even interface gestures were a very old area of research.

What Apple did that was innovative was approaching the mobile device from a completely different perspective. Instead of a phone that happened to be able to do some computing-like tasks, they came at it from the approach of a pocket computer that also happened to make phone calls. This sounds like a trivial distinction but it makes a big difference.

The touchscreen is not a bullet on a spec sheet. The touchscreen is a an expression of this philosophical approach to the mobile experience. It allows you to ‘paint’ any interface you want onto the device and allows you to iterate that design over time. This is exactly analogous to the development of the GUI, software based buttons and interfaces allows much greater flexibility than anything hardware based.

nokia_n97_group_05_lowres.jpgI’ve seen some of the coverage by tech bloggers, including Scoble, about the Nokia N97 device and I hold to my position that this marks a failure for Nokia. To be fair, the specs and the design of the device are actually quite impressive. I think Nokia has done an excellent engineering job with this device. Looking at videos and its capabilities, it’s quite sexy. The problem is that it reflects the same philosophical approach to product development that the mobile industry has had for years. The touchscreen feels like a tick-mark on a spec sheet and not an embodiment of a different approach.

Both the blackberry storm, and this new Nokia seem to have this same problem. If they can somehow just bolt on a touchscreen onto their existing OS/device, they’ll not only have feature parity with an iPhone but exceed it on every count. Unfortunately, that’s not why the iPhone is great, a touchscreen does not an iPhone make.


Cool MacBook X-Ray

November 20th, 2008 . by mikepk

Apple: Aluminum MacBook X-Ray Makes Perfect Desktop Background: “”

macbook-xray_01.jpg

Technology in x-ray always looks cool to me.

(Via Gizmodo.)


Google is not a technology company

September 2nd, 2008 . by mikepk

I know we’re used to thinking of it that way, but I think that image belies the nature of the company or what it’s rapidly evolving into. Google has created some pretty cool technology, have some of the best and brightest working away in the Googleplex, but are they a technology company?

I’ve been seeing a lot of posts about Chrome, Google’s really interesting new browser, but why are they releasing a browser? I’ve been contemplating Google’s unique position in the tech space, and the fact that they make almost none of their money in that space.

If you take the perspective that they are not a technology company, why would they want to do this? If they’re not a technology company, then what? Google is in the business of advertising. Granted, their approach is very hight tech, but at it’s core, the vast majority of their revenue comes from ads.

Taking that view one possible motivation for creating their own browser comes into focus. What are the most popular browser plugins for Firefox? Ad blockers. If you control the browser, and you’re an advertising company, you can keep people from ignoring your ads.

I’m sure creating the “browser as OS” or possibly just improving the browser experience as a more stable platform for google apps, or possibly a development platform for Android were part of their reasoning for releasing Chrome, but at the moment they make almost no money from those types of efforts. The one thing I haven’t heard anyone talk about, and that I wouldn’t totally discount is the control of the ‘advertising channel’. I wouldn’t be surprised if Chrome either will intentionally lack a plugin architecture, or, at a minimum, will involve a vetting process that “for your safety” conveniently also disallows ad blockers.

It’s interesting to look at their actions in this way. Google is an advertising company and becoming more so each day.


VibeMetrix - Our newest site

August 19th, 2008 . by mikepk

The blog has been a sparse lately because we’ve been working, heads-down, on VibeMetrix. What is it? VibeMetrix, is a tool for engaging with social media. We hope it will evolve to become the best tool for engaging with bloggers, building relationships and filtering and tracking conversations on the internet.

I’ve had a series of posts I’ve wanted to write about the road that’s led us to this from our usual set of Grazr offerings. As usual, when working in a startup, inspiration comes from interesting and unlikely places.


The Awesome Bar

June 18th, 2008 . by mikepk

Sounds like the name of some trying-really-hard-to-be-hip new nightspot. After playing with FireFox 3 for a couple of days, I’m surprised to find it’s my favorite feature of the new browser. I upgraded mainly because, for some unknown reason, FF2 was highly unstable on my Mac (crashing at least once a day, and yes that was after ruling out extensions). In search of stability I updated to FF3, but didn’t think much of it’s new features.

I just typed a single letter into the url field and the first item in the awesome bar’s results drop-down was exactly where I wanted to go. Freaky. If it gets any better maybe I’ll be able to navigate via thought :). A very nice addition, kudos to the Moz team.


Innovation in a big corporation

June 5th, 2008 . by mikepk

I was reading a post by Zoli Erdos about how Microsoft could have been first out of the gate with a web based office alternative but then canceled it. Then I saw Matthew Ingram followed up with a common interpretation of this kind of big company behavior, that they can never win (ostensibly because they fail to grok new waves of innovation). This reminded me of a post I wrote some time ago regarding this odd big company behavior so I thought I’d repost it here (with some edits). Sorry for the length, I’ve never been good at being succinct.

We’ve heard the corporate battle cry, “innovate or die!” Countless books tell us that innovation is at the heart of our economy. Those companies that innovate prosper, while those that don’t are doomed. We accept that to be innovative, especially in a corporate sense, is akin to pure virtue. So why are large companies so awful at new and sweeping innovation?

Big companies aren’t nimble. They don’t react to changing market conditions. They become buried in bureaucracy, stuck in their ways, sluggish, inefficient. Phrases like these reflect around the media echo chamber all the time. This imagery appeals to our love of the underdog especially when considering startups versus large companies, David versus Goliath, virtue versus brute strength. While this imagery is appealing I don’t think its true.

It’s important to understand the dynamics of innovation in large companies if, when creating a startup, we hope to harness the shortcomings of large companies to become successful. Too many startups believe they can succeed by virtue of being a startup, relying on the ‘fact’ that large companies are incapable of being nimble or innovative. I think this is fundamentally untrue, although clearly there is something at work that allows startups to succeed an topple more powerful incumbents. Bureaucracy and inefficiency are serious problems inside large institutions but I don’t believe this fully explains the lack of innovation.

Looking at the case for innovation in big companies, I have a unique perspective. I worked for, Data General, one of the big, old minicomputer companies that are part of the accepted technology industry narrative. DG, DEC, Wang, Prime, the mini computer companies that, as the story goes, went to their grave oblivious to the changing world around them. The fate of the minicomputer company is often used as a warning story to those that don’t worship at the altar of innovation.

There were lots of interesting historical footnotes to this ex-minicomputer company that I worked for. By the time I started there, in the late 90’s, they had long ago abandoned the minicomputer and were developing some pretty cool and cutting edge computing systems (why I had chosen to work for them). The longer I was there the more I learned about the innovations that had been pioneered but never commercialized. I learned that at one point they’d developed one of the first true laptops, with battery power, dual 3.5 inch disks, LCD screen, all in 1984. Their implementation of the Unix operating system was frequently hailed as one of the most stable and innovative. They created a new disk storage subsystem (which eventually led to their being purchased by another company). One of the business units at DG, when I started, was developing stackable, lego-block-like internet appliances for ISPs.

One day I was wandering the halls and stumbled on a strange wireless, handheld, WindowsCE based, touch-screen LCD, “clipboard” called the “wiinpad” that was sitting in a garbage palate. Apparently this “clipboard” had been developed somewhere between ‘97-’99 and then canceled. In short, there were lots of really neat and innovative things happening in the company, yet it was still considered a minicomputer company incapable of innovation.

There’s a famous quote attributed to Ken Olson who was CEO of DEC, “There is no reason for any individual to have a computer in their home”. This quote is cited frequently in support of the innovation myopia afflicting large corporations. Again I think the soundbite and the imagery it evokes are more appealing than the truth, Ken Olson himself had a computer in his home.

[That interpretation of my comment] is, of course, ridiculous because the business we were in was making PCs, and almost from the start I had them at home and my wife played Scrabble with time-sharing machines, and my sixth-grade son was networking the MIT computers and the DEC computers together, hopefully without doing mischief, using the computers I had at home. Home computers were a natural continuum of the “personal computers” that people had at work, in the laboratory, in the military.

The original quote was aparently taken out of context where he was discussing home automation (whether a computer would *control* your home, turn your lights on and off, fix your meals, etc…). Mr. Olsen defended himself on numerous occasions saying he fully understood the importance of the PC. It could be argued that he was just back peddling, but I don’t believe it.

Minicomputer companies died, it is said, because they failed to see the “strategic inflection point”, “paradigm shift” (or pick whatever sweeping term you want) of the personal computer revolution. I don’t think the innovations occurring in the company I worked for were isolated and probably occurred in all the old minicomputer companies. These companies are filled with exactly the engineers and innovators who see these trends. So they were indeed innovating. That, however, leads to the more interesting question of why weren’t any of these innovations successful?

The foundation for my understanding of innovation in a startup versus a corporate behemoth lies mostly in an excellent business book on innovation, “The Innovator’s Dilemma” by Clayton Christenson. It is a book I highly recommend all technology entrepreneurs should read. Its the closest thing I’ve found to an engineering approach to understanding the force of innovation and how it relates to big entrenched companies versus startups.

Christenson divides innovation into two broad categories, sustaining and disruptive. His theory is that big companies are amazing at the former and terrible at the latter. Sustaining involves improving on current technology such as increasing data density on a hard drive platter. Disruptive technologies are “fringe” technologies that are usually “low end” (or at least initially so) the PC versus the minicomputer.

The key to understanding this is that large companies ignore disruptive technologies because it is the right thing for them to do. All of the business structures, processes, culture, and institutions will have been rightly structured to maximize profit and growth for the company. Disruptive technologies, by their nature, will produce little initial profit and revenue (relative to the large company) and will only cater to the “worst” low end customers of the large company.

I mean “right thing to do” from a classic business standpoint. Its the driving requirements of profit and growth. Improving the current technology by adding features, power, or general “goodness” are what allows the company to satisfy its most important and high profit customers. Clearly catering to your best customers is a good thing. A disruptive technology, like PCs during the minicomputer era, would have been interesting to the visionaries in the company but would not have satisfied the requirements of the “good” highest profit customers. Even if the minicomputer company had tried to supply this new “low end” product, all of the internal structures of the company would have been aligned against it. Not because it didn’t have the potential for great future success, but because in the present it was diverting effort from the highest profit, highest margin business, and from a “bottom line” standpoint any profit and growth would have seemed trivial.

Startups have two primary advantages. The first advantage is that the profit and growth generated by a disruptive technology, while trivial to a large company, will be quite interesting to a startup. The second advantage is that startups are directly coupled to the market for their disruptive technology. Startups will do anything to make that disruptive technology “fly”, leading to the sense of nimbleness that is really mostly borne out of desperation. Where a large company will cancel a disruptive technology project after several quarters of “insignificant” revenues, most startups will see that same income as great success and carry on.

How are the “Goliaths” toppled? Over time the “sustaining” innovation factor continues to apply to the new “low end”, disruptive technology. This disruptive technology begins to become good enough for more and more of the market originally satisfied by the large incumbent. As the disruptive technology eats at the “low end” of the big companies market, this “squeeze” forces them to focus more and more on the highest profit/margin cstomers. Eventually, the large incumbent innovates itself right out of its own market via “sustaining” development, while the new technology now satisfies all the needs of the market at a lower cost. The key is something Christenson says a few times in his book, that good companies can fail by doing everything right.


Scoble Feedback

June 1st, 2008 . by mikepk

I wasn’t expecting this kind of a response from Robert Scoble to my comments on Mathew Ingram’s Blog regarding Twitter and their architectural issues. I really honestly appreciate the feedback on Grazr, even if it’s painful for me to hear as one if it’s creators.

First, I want to say, Grazr is still here. We have lots of users, just not as many as we’d like and not on the growth curve we’d been hoping for. We’ve been trying to evolve and iterate our service to find the elements of it that are compelling, what it “wants” to be. One of the truths of startups is that you rarely “hit it big” with your initial idea. Twitter had no idea what they were onto when they first launched the service. Flickr started as an online game for girls and it took them time to find their niche. The key is accepting feedback and looking for the aspects of your technology that people find interesting and moving emphasis. We are still very much in this process.

Robert, thanks for the feedback. What you’ve pointed out is pretty much an exact list of the issues we’ve identified as we’d planned for our next version of Grazr, one we intend to launch in a few months. The strength of our core team is the technology skill-base, which in a lot of ways gives us the opposite problem as Twitter. Our architecture, services and scaling are extremely solid, but at the same time we’ve brought in some new people to help us redesign, re-articulate and relaunch the service in ways we’re confident are going to be much more consumer-facing and understandable.

I’ll be very interested in your thoughts on the new version. I’ll let you know when we’re ready, I would love to get more (albeit brutal) honest feedback :)

(I cross posted this to our company blog Feedonomics as well)


Politics in Twitter via Summize

May 31st, 2008 . by mikepk

I know Twitter’s been having problems, but lately we’ve been hoping to build some twitter services. Unfortunately due to their issues, we’ve been denied access to the twitter jabber stream we were hoping to build on. In the interim I’ve been playing with Summize, it’s a pretty nice search engine for Twitter. They return data in a few formats, so I’m playing with their JSON return seeing what I can get out of it. Here’s showing a search for various political terms including the DNC, Obama, Hilary, McCain and a few others.

summize

Temporarily disabled.


Apple News

May 31st, 2008 . by mikepk

It’s nice to have a new blog where I can throw together little experiments. I just changed my stream integrator around a bit so I thought I’d test it again. One of my streams is “Apple News”, so this list should be an up to the hour river-of-news, updated from my favorite Apple news sources.

Powered by Grazr Streams


Thar she blows!

May 29th, 2008 . by mikepk

thar she blows I may have to eat my words about Twitter surviving its current troubles. I’ve been surprised how often I’ve seen this screen over the past couple of days. If a service is down more often than it’s up, I wonder if we’ll see the tipping point where a mass exodus from Twitter will occur?

We’ve been hoping to start a new project using Twitter data (through their Jabber API) but we’ve been denied access twice now (with a nice come back later mesg.). Hopefully Twitter will pull themselves together, we’d like to play in the Twitter ecosystem (besides just reading their feeds).


« Previous Entries