Skip to main content

Attention to Detail

Apple has set an extremely high bar with respect to attention to detail in every aspect of the interface between the company and the customer. Yesterday I purchased an iPod for one of our beta testers, who was also a substantial contributors to iFlinger (an iPhone application that would let you toss a virtual cartoon shoe at a cartoon caricature of former U.S. President George W. Bush, if Apple had approved the application, which they did not.)

Today I was greeted in my email in-basket with a request to fill out a survey. The survey form was efficient and responsive, clear, concise, and contained places for me to elaborate or describe responses which varied from the options on the form. When I finished filling it out, I was greeted with this plain, simple, competently styled web page, which included a minimal set of links to places I might want to go, and a roughly standard footer with other such links, and a thank you.

200903270827.jpg The pleasant experience with Apple's feedback survey stands in marked contrast with other forms that I've filled out for other companies. Feedback forms always seem to receive the least attention in big companies. Very often they are not well organized, and contain exactly no way to deliver the kind of feedback the company needs to hear.

In these other companies, it's as if the committee in charge of the feedback form is somehow shackled, or has an incentive to gather only positive results, or more likely just doesn't have any experience with conducting surveys, doesn't know much about the company, or just doesn't care. Most of the other online feedback forms I've seen dump you to an oddly unstyled web page, which sometimes says "Thank You" but other times doesn't say anything meaningful at all. Usually they don't include a simple link back to vendor's main web site. I've even seen things like PHP core dumps which left me in no doubt that the vendor really didn't care one iota about my "feedback". Thank you for your feedback! We are promptly tossing it into the bit bucket! Have a nice day!   

This almost obsessive attention to detail at Apple, which results in seemingly minor things like the thank you page of the feedback form being considered as an important customer interface, is applied to every possible interaction between Apple and its customers.

Unfortunately, this corporate obsession is not applied to every interaction between Apple and its third party developers. As with similar stories from other vendors, when our iFlinger application was rejected, the reasons offered didn't really make much sense. There was no avenue to provide feedback or make an appeal, or engage in a discussion which might result in the application being modified in such a way as to get approved.

Despite Apple's recent declaration (in the iPhone OS 3.0 presentation) that everything is fine because most apps get approved within a week, now, the iPhone App Store process is hopelessly broken. Developers must guess at what might get approved or rejected, based on a lengthy document full of vague legalize which translates quite literally down to this phrase:

"Apple can reject your application for any reason, for reasons other than stated, to provide them with a fig leaf, or for no reason at all. If a summer intern at Apple rejects your application, tough luck."

To some extent, relations between Apple and their development community have always been rocky. Some tension between them is a natural and unavoidable outcome which arises from Apple's need to keep research and product plans secret. However, the iPhone App Store policies have been upside-down (build it first, we'll tell you later if you will be permitted to sell it) for too long. If it's too difficult to put a concept-approval process in place, then an appeals process needs to be created, and guidance on how to overcome app rejections should be available.

One might be tempted to suggest that Apple's rocky developer relations are their "perfect flaw" but somehow I don't think so. Perfectly flawed pottery doesn't leak water all over the floor.

No, a perfect flaw is more subtle. A perfect flaw is holding your iPhone upside-down, on your otherwise very stylin' iPhone consulting web site.

Comments

Popular posts from this blog

Blogs: Not dead, yet!

If you're a blogger, you might find this essay, recently shared to YCombinator's Hacker News  from a blog, to be of interest. It's perhaps a little pessimistic, but has some fair observations about the state of affairs in the #blogosphere.  If I could bring one thing back to the internet it would be blogs It's almost impossible now to find a blog that's not on a focused theme because that's what search engines focus on and how websites profit. But you want the opposite, a blog that never tried to focus or even thought about it.  The observations about the role of the only search engine that presently matters, Google, in the state of the blogosphere are worthy of consideration. In the discussion at Hacker News, the author was criticized a bit for saying that Google Blogger was "dead" —which itself seems a pretty fair criticism if not strictly accurate in a pedantic sense. Google basically abandoned Blogger in place years ago. Sure, our own ill

Black Monday was the Big Bang

On February 11, 1993 NeXT announced they would no longer make and sell their sleek black computers the NeXTcube and related family of "pizza box" workstations known as NeXTstation . Three hundred people were fired and the company reformed around a software strategy based on pitching their operating system and object-oriented software developer tools known collectively as NeXTSTEP, for various  hardware platforms including PA-RISC, SPARC, and Intel x86.  In addition to providing their OS on other hardware platforms, the company worked with partners including Sun and Microsoft to layer their developer tools on other platforms including OpenStep for Solaris and OpenStep for Windows (sometimes known as "Yellow Box"). Known by the community of NeXT enthusiasts wryly as "Black Monday" this transition led to some amusing footnotes in the history of computing. One Wall Street firm, AIG Trading, didn't pick up the advanced (but probably very subtle) hints

ectoize - bookmarklet for ecto

We received an interesting email from an ecto customer recently. Here's what they asked us about: "Hello, Any text that I publish using the "ectoize" bookmarklet appears on my blog entirely in italics, indented, with a vertical line on the left side of the text. I've searched high-and-low but can't find any reference to this problem on your website or in the documentation. Can you help? Thanks." Of course, since we didn't have the full context, we had to chat back and forth a bit to figure out what they were really trying to do. They had been advised by a WordPress consultant to use ectoize, the ecto bookmarklet, as a tool to help them migrate content from a static web site (which had been created in GoLive) to a new site, managed in WordPress. ectoize, the bookmarklet, grabs a chunk of highlighted text from a web browser window, launches ecto, and pastes the text into a nice little block quote. The italics and vertical line were coming from th