Apple at Expo: What went wrong?

17.12.2008

Now here's why I'm not surprised by Apple's announcement. Let's back up for a moment to the turn of the century. At that time, there were two Macworld Expos--one in January in San Francisco, and one in the summer on the east coast. (First Boston, then New York.) Apple pulled out of the New York show just as it was announced that it was returning to Boston. Which one of those facts came first depends on who you ask. But let me tell you this: those final few Apple keynotes at Macworld Expo New York were lame. Apple had very little in the way of new products to offer, so the high expectations that come with Apple keynotes led to major disappointment.

It was clear to me that Apple was tired of announcing products on someone else's schedule. The elimination of the east-coast Macworld Expo reduced that expectation down to one event: Macworld Expo in San Francisco.

At the same time, Apple was toning its product-announcement muscles in other areas. The keynote address at Apple's once-sleepy developer conference suddenly became a hot ticket. And Apple began making more and more major announcements at Apple-controlled media events, not only at the Apple campus, but at Moscone West in San Francisco, at the Yerba Buena Theater in San Francisco, and even at the California Theater in San Jose.

Those events were timed by Apple, controlled by Apple, and attended only by Apple's invited guests--VIPs, members of the media, analysts, and Apple employees. The public couldn't get in, and there was no intermediary like IDG World Expo to get in the way. But I think most important was the timing--Apple could announce products when it damn well wanted to, rather than being forced to adhere to a trade-show calendar that's usually set years in advance.

Apple Stores: They're like mini Expos!