Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.
X

The Gravest Pain of an iPhone Developer

It’s a chattery time for App Store problems. Apple rejected Google Voice, then neutered Ninjawords and still presents an utterly opaque face to developers.

There are a laundry list of problems facing the growth of the App Store. I won’t bother to rehash them here. Let’s focus on the one that most thoroughly jeopardizes the future of developer businesses: Customer Service. Every other problem can be overcome or worked around but without the power of caring for your customers, your business has no reason to exist.

In an aside to a link last month, John Gruber muses:

I’m wondering how much of the problem is that the App Store is built on the foundation and framework of the iTunes Music Store, which was designed from the outset specifically as a venue for selling 99-cent downloads.

This is the most crucially important point: the iTunes Store was never designed to sell software. Among other things, Craig Hockenberry enumerates all the ways in which the App Store is hobbled by this historical truth. It’s a good, important post that you should read if you care about this kind of stuff. But it doesn’t address long-term outcomes related to customer service that will doom the developer community.

As an iPhone developer, I have no control over my storefront – Apple manages it for me, with basic data I provide. On the one hand, this is incredible news: access to a huge pool of customers, a complete distribution infrastructure and – best of all – I never have to worry about payment processing.

There’s just one issue: Apple doesn’t give a damn about my relationship with my customers.

Generous, attentive, impassioned customer service is an important piece of any successful business. My customers mean the world to me. Unfortunately, iTunes does not provide a clear, encouraging feedback channel.

User Reviews

When you’re selling music, user reviews are a simple tool. Much is subjective, but overall quality will be reflected in the reviews.

With software, the reviews have become more complicated. The most tantalizing way for a customer to speak out about software that is giving them problems is to write a review. And that’s what they do. Bug reports, feature requests and anything else that comes into their minds gets dumped into the reviews. And why not? The ability to write a review is prominently featured and uses a built-in, official form. It’s infinitely more seductive than leaving iTunes to write an email to the support contact. It’s also a venue provided by the same service that is taking the customer’s money, so it feels more intimately linked to their purchase than anything they can do on an external website or in their email client.

This is infuriating since the communication is strictly one-sided. There’s no way for the developer to follow up on these reviews to ask for more information. Without that information, acting on a bug report is often impossible. The worst part is that without dialogue, it’s impossible for the customer to learn more about their problem, discover workarounds and discover that there’s a living, breathing person who truly cares about the quality of the software they’ve just purchased.

Like it or not, the iTunes user review becomes the support form of last resort.

The Consequence

There are ways around this. Tap4Help is an interesting example, providing a built-in feedback and support request system. Developers, like Lucius Kwok, report some success explicitly declaring their email right in their application description with a call to action encouraging its use. I do this, too, but it doesn’t catch them all.

Why not? Nothing will ever come close to the power and authority of iTunes itself. I theorize that part of the reason so many customers prefer the review form to using a support email or link is that they know that iTunes will provide them satisfaction. No matter what, iTunes will show their review. They will be heard.

By keeping these customers so thoroughly at arm’s length, Apple retards the formation of relationships that will build developers’ business. I’ve turned angry emails into loyal customers through the power of honesty and genuine interest in customer issues. I’d desperately love to provide that dialogue for every customer, ever, but iTunes, under the current system, will continue to siphon off some portion of those opportunities into its black hole of customer reviews.

Having good conversations with your customers is as essential and non-negotiable as having an engine in your car. When Zappos tweets at me in thanks for my praise, I feel as though my relationship with the company has been further validated. When Netflix gives me complete and generous support when I have trouble with their service, I feel respect for them, since their conduct conveys respect for my business.

It’s all about how the customer feels. If you never get to talk with them, you’ll never get to impact that feeling.

Let’s Do It Better

This is not a hard problem to solve. If you happen to work on the iTunes Store infrastructure team, you may feel differently, but the company you work for is in the business of accomplishing the impossible on a fairly regular basis. My sympathy is limited.

Developer Review Replies

This is the easiest part. Let the developer reply to user reviews. This isn’t groundbreaking and I’m the eight thousandth developer to suggest it. So make it happen. The developer can join the conversation and solicit additional information so that bug reports that go into the reviews can actually be productive. Notify whomever left the review that they have a response via email. For bonus points, let the customer reply directly to that notification to reach the developer.

Feedback/Support Form

Let the user provide feedback or support requests through an official, iTunes-embedded form. Send the feedback to the developer via email, with an anonymized reply-to address, like craigslist uses, so Apple can cover their ass on privacy concerns. For bonus points, provide a rating for each application that states how responsive each developer is to requests sent via this form.

There is no step three. With those two provisions, an open dialogue has been created for anyone who bothers to seek one. Software, even for the iPhone, is not music. The one-sided echo-chamber conversation of the iTunes Music Store does not work in the App Store. With the two modest tools I’ve described, developers will have an infinitely easier time creating the relationships they need to build their business.

I’m not going to hold my breath. Hopefully Apple is working on this stuff, but in the meantime, I need to figure out better ways to put myself in easy reach of my customers.

Bad Products: Help A Reporter Out

Publicists are expensive. I do everything I can to keep my costs non-existent, so I don’t have one. But I still want press. One option I once read about that seemed promising is a mailing list called Help A Reporter Out.

Unfortunately, HARO, as it is called, is an awful product. It makes the fatal mistake that many fast-scaling services make: screwing the most important customer.

Three Customers

HARO has three customers: journalists, who need leads, sponsors, who pay for placement, and subscribers, who consume sponsored content and respond to journalist queries.

Subscribers are the most important customer as they are required for both sponsors and journalists to even bother with the product. Without subscribers, there’s no one for sponsors to influence. Without subscribers, the journalists get no responses.

A typical HARO email goes something like this:

  1. Lengthy sponsored message
  2. Cutesy personal update from the mailing list administrator, Peter Shankman
  3. An absurdly long list of journalist queries

The practical result of this is that a subscriber will have to scroll an entire page before they even get to what they care about. Even better, HARO is sent out as often as three times a day.

Now, I disclaimed that as typical. What’s more interesting to my point are atypical HARO messages. These don’t happen often, but happened often enough to piss me off. HARO has particular rules about how subscribers should interact with journalists. It’s pretty obvious stuff, if you’re not five years old, but boils down to please don’t spam the reporters. Sometimes a HARO subscriber would go off the reservation, do something naughty, piss off a reporter and end up in Shankman’s bad graces.

It’s a closed system – a mailing list, after all. The solution seems pretty simple. When applicable, speak to the individual’s boss, if their wrongdoing was in the service of a larger organization. Then, kick the person off the list.

That’s it. Problem solved.

In Shankman’s defense, it seems he does do this. Then he takes it a step further, by venting his frustration into the next HARO email and scolding the entire subscriber base at large. Here’s a sample:

READ THIS: This morning, while being given a behind the scenes tour
at Busch Gardens, I had to spend a portion of the tour on my mobile
phone, calming a reporter from a major publication. Seems someone
at a major agency took it upon themselves to form an opinion on
what kind of story the reporter was writing, simply from the query
alone.  Long story short, this was a situation that should not have happened.

This isn’t brain surgery here, guys: If you can answer a query, do
it. If you know someone who can answer a query, send it to them. Do
not post them on the web, in blogs, or on message boards, and do
not email the reporter saying “You should do it this way.” Had I
not gotten an EXTREMELY sincere apology from a top-level person at
the agency, I’d be outing the person who caused the mess in the
first place, as well as outing the agency. Instead, he’s just banned
from HARO.

Five rules of HARO here: READ THEM.
http://shankman.com/the-five-rules-of-haro/

I can only speak for myself, but as a former subscriber, it’s worth listing all the things in this message I don’t give even a tiny fraction of a fuck about:

  • Shankman’s very special behind the scenes tour
  • The frustration of said tour’s interruption
  • The existence of an over-sensitive, irate reporter who doesn’t know how to use the delete button on her keyboard
  • A rehash of common sense HARO rules I already know
  • Shankman’s super-duper ballbusting phone call to top-level Tommy
  • The ban of another subscriber
  • The power of passive aggressive ALL-CAPS text

The Precious Commodity

HARO exists thanks to a simple reality: time is a precious, ever-dwindling commodity. If reporters weren’t in a hurry, they’d spend weeks on just one story, finding the perfect source for their piece. They don’t have that luxury. HARO to the rescue. Similarly, subscribers don’t have time to build a publicity campaign, research publications or spend weeks pitching themselves. They often don’t even have time to learn how. Again, HARO to the rescue.

The issue is that HARO does not give any reverence to the time of its subscribers. Quite the opposite: not only do we have paragraphs of crap no one cares about at the top of each message, there’s this occasional business of Shankman feeling empowered to command the entire list to spend time reading a rant about the misbehaviors of a single participant.

This doesn’t even begin to take into account the amount of time it takes to scour the actual list of queries. Taken in aggregate, it’s shocking. Let’s not forget, it’s a thrice-daily proposition.

The reason it happens is that while subscribers are the most crucial part of Shankman’s business, they’re also the most plentiful – the most easy to replace. Sponsors are magic unicorns, treasured and protected. Journalists are golden geese, continually laying the eggs that make each HARO message. Subscribers? There are tens of thousands of those.

So HARO gets away with it. For now.

Complacency Breeds Contempt

I just checked my calendar. It’s 2009. A mailing list? Hell, let’s move the whole thing over to Usenet. Infinitely more retro chic and you don’t need to bottleneck the queries through a single guy.

The problem with HARO not caring about its subscribers’ time is that it completely erodes loyalty, trading every ounce of goodwill for an ounce of contempt with each message. When something better comes along, they’ll have no problem switching. Ask Blockbuster how that works.

Fine, so you’re saying if I’m going to be a douche and trash this guy’s hard work, I should have a better idea, right? Glad you asked.

Let’s Do It Better

Build a website.

That’s it. A problem actually solvable with a website. Could have been huge during the dot-com bubble, but I bet it’s enough to at least keep Shankman fed. Here’s what you do:

  1. Persistent accounts that store basic bios and feedback ratings. Elevate the stars, demote those who don’t play by the rules, make it clear who’s making the best contributions
  2. Categorized, post-moderated, RSS-enabled members-only query threads that let reporters post their queries whenever they want or need. Only postable by verified reporter accounts to keep the bozos at bay
  3. Tagged queries: instead of having to parse a tedious headline that’s different for each query, provide the option for easy-to-scan tags
  4. User-configured search agents to send email alerts any time a query seems of interest
  5. Daily sponsorship opportunities, to keep Shankman in Busch Gardens tickets

That’s it. I bet you could accomplish most of it with Ning, without having to spend a dime. If you wanted to take it to the next level, you could impose a monetary bozo filter for new accounts.

Will it happen? Eventually, I’m sure it has to. Linking journalists with sources is an important job. Just because HARO’s implementation is completely hamfisted doesn’t mean someone else’s won’t eventually hit the mark. Will Shankman do it?

“It is difficult to get a man to understand something when his salary depends upon his not understanding it.”

Upton Sinclair, via Daring Fireball

So who knows. In the meantime, I’m off to half-heartedly find some other way to get journalists to talk about me.

No boss, No paycheck, No worries

I’ve been collecting a paycheck since I was 15. It began at Publix, the best damned supermarket you’ll ever visit. I was a shy kid, reluctant to be employed and encouraged by a dramatically unstable home life to stay as hidden from the world as possible. But I went. I interviewed.  I didn’t know much about interviewing at that point. The myriad job hunting bullet points had yet to be delivered to my brain. I don’t remember what I said or even what I was asked. It wasn’t an impressive performance, surely.

But they called me. I had a job.

And I loved it. I’d never had more fun in my life. Thanks to a handful of adult mentors, I went from being shy and insecure in front of strangers to being outgoing, helpful and outrageously courteous, as befitted Publix’s customer service mission.  I got to meet people, learn about their lives and help make their day better, all in the time it took to bag up an order and pack in a car. Publix has a firm “no tipping!” policy and this was spelled out on a button affixed to my apron at all times. Despite this, not a week went by where a kindly retiree or harried but grateful parent didn’t stuff a couple bucks into my hand or pocket, buying me a sandwich or drink to end my shift. With a home life that was terrifyingly unpredictable and school that was tedious and unsatisfying, Publix, the people and the tangible benefits of my work there, became an escape that I craved.

There was plenty of reward in the fun of the job, but I found that throwing myself into my work with such gusto had other perks. When all of the front service clerks got reviews, there was much kvetching in the break room. Nickels and dimes, my teenaged colleagues moaned. They barely gave them anything for a raise. When my turn came, my boss, Mr. Starkey, called me into his office. After rattling through his estimate of my performance, I was given a fifty cent raise. It was the largest, Starkey confided, that anyone in my group had gotten. In retrospect, too, I realize that I was rarely tapped to do cleaning chores, since my management seemed to prefer me in front of customers as much as possible.

It was all so perfectly Randian, in a way that satisfied my then-Randroid brain. I gave honest effort in exchange for honest reward and recognition. Love your work, I thought as I pushed a pile of carts back into the store, and nothing feels like work.

Of course, it wouldn’t last. Home, as was its wont, took another lolloping, staggering jolt. For the second time in less than a year, we were moving away. Mr. Starkey was crestfallen. He’d been eager to groom me into cashiering and beyond. These were remarks that were and remain deeply flattering – it didn’t seem like he especially enjoyed terribly many of the other kids who had my title. At my request, he eagerly typed up a letter of recommendation. My favorite line, then and now:

“I would rehire him immediately if he were to return to Sarasota.”

I enjoyed it both for the heartfelt endorsement and for the tiny, whimsical implication that I was somehow in control of my existence.

I went on to be a salesman, an intern, a marketing manager and a project manager. With each job, I hoped to find the feeling I knew at Publix. The feeling of throwing myself into my work, enjoying every minute, and always hungry for more.

To be sure, I had some amazing jobs in the years since. Tremendous opportunities that provoked growth and change. But none of it could ever recapture the lost innocence of that first, magical time I worked at the supermarket. This realization, each time I started a new gig, was always a tiny disappointment.

For almost a decade, I’ve drawn a paycheck from someone. Until now. Not having been to the office, or any office, feels vaguely like retirement. Except there’s a ton of work to do.

And it’s back: that magic Publix feeling.

I love my new job. I’ve spent the last week building a new iPhone app from scratch. My new boss, me, really likes how it turned out. This is the most incredibly rewarding productive activity I have ever chosen for myself. The app is about done; I’ll have more to say about it soon. The most tremendous and powerful discovery came through its creation: I love developing applications for the iPhone. I can do it all day and night until my fingers hurt and still want more. It’s the most satisfying thing I’ve ever invested my working time doing. All I want is to get better and keep building.

Like Publix ten years ago, it doesn’t feel like work. It’s fun. It’s… wonderful.

Time will tell if this feeling and the products it creates will be sufficient to feed and house me. For now, I’ve got enough to hold out for awhile and give it everything I’ve got.

It’s a scary prospect to abandon security and regular cashflow, move across the country, and go into business for yourself, all the while hoping to hell everything will work out okay. Like many projects, it’s one of those things where if you truly took the time to consider all the attendant difficulty, complication and risk, you’d never bother to do it all.

It’s the best decision I’ve ever made.

Love what you do, do it for you

As I begin this post, I am nine days, six hours and 31 minutes away from leaving a very comfortable, generously-paid job where my colleagues and leadership respect me and treat me well. In just over a week’s time, my girlfriend (and adventuring partner), Aubrey, and I will be driving off into the night, embarking on an incredible roadtrip to seek out a new home somewhere beyond the Rocky Mountains.

There are no words to convey my excitement.

For as long as I’ve existed, there has always been an obligation to someone else’s rules lurking just beyond the horizon. Even on vacations, where time is theoretically mine, there was the lingering, ever-present knowledge that before I knew it, I would go back to a world of obliging someone else’s whims. For the first time, I’ll escape those bonds. It’s a feeling of freedom I’ve never known.

It must be stressed that while Full Sail has been a great place to work and I’m grateful for the experience, I had a job there and I have a handful of problems with working any “job,” no matter who supplies it. When I say job in this context, I mean any paid activity wherein you provide 40+ weekly hours in exchange for a regular paycheck, benefits and perhaps a reasonable approximation of social interaction. I’m a difficult, demanding, even impossible person, so these problems loom larger for me than perhaps they do you.

More…

GlobeJot fixed, waiting on approval.

The App Store approval delay is easily the most painful and difficult part of developing for iPhone:

The good news is that nearly two weeks ago, GlobeJot’s major issues had been diagnosed and corrected. The bad news is that, until Apple gives the go-ahead, the fixed version is not available for your enjoyment.

Learn more at the main site.