Tuesday, August 17, 2010

The "Verizon" iPhone - If I were Apple

There have been rumors about a Verizon iPhone since the first day it went on sale as an exclusive AT&T phone in the United States 4 and half years ago. Recently, however, even major publications are buzzing with speculation. In common among pretty much all the rumors is that Apple is developing a special version of the iPhone just for Verizon in a bid to increase market share in the US.

I, however, have a different idea.
Apple has been making gangbuster profits on the iPhone. One of the main reasons that this has been possible (at least in the US) is due to the very lucrative exclusivity contract with AT&T -- Apple doesn't sell the iPhone for other networks and gets a kickback in return.

At the same time, the iPhone has grown to be number one in mindshare when it comes to smartphones. Everyone, and I mean everyone, has heard of the iPhone. Android, meanwhile, has enjoyed little brand recognition in the way of the mass public. Standing in the way of mass adoption, however, has been the exclusivity contract.

Most people, including John Gruber of Daring Fireball, posit that Apple is in no hurry to embrace Verizon and Verizon, with Android's recent successes, is in no hurry to embrace the iPhone -- at least not to the point of either side making concessions in their agreements.

Astute as Gruber's arguments may be, I think Apple has a winning hand. They don't need to go with only Verizon. If I were Apple, I'd make a CDMA version of the iPhone and put it on sale carrier free.

Now freed from the binds of specific carriers, customers will be abusing every wireless carrier support center in the US to get one. Armed with this new leverage, Apple can create a standard contract for all interested carriers tilted very much in their favor. Rather than face the support and PR nightmare of being the only carrier without the iPhone, every one of them will fall right into line.

Apple gets the market share and deals just as they want them. Everyone else gets the iPhones they've been waiting for.

For further reading on Verizon iPhone rumors, I highly suggest John Gruber's recent posts on the matter:

Monday, November 23, 2009

Trash

I've learned a lot from Steve Jobs, but the number one rule is this:
Everything you've ever built is trash.

Sit and think about that for a moment. Every project you've ever worked on, every piece of code you've ever written, every design you've ever made is complete and utter garbage. If it wasn't, you'd be done. And let's face it; we're never done.

If you take the statement above as implicit truth, the next question is "Why? What makes it trash?". This is an extremely important next step. If you stop at the first statement, you can never make something better. Critical thinking isn't just about complaining; it's about contributing. It's about figuring out exactly what makes something good and how you can make it better.

Don't sit in a tower thinking everything you've done is amazing, but also don't grovel in a trench thinking you'll never amount to anything.


Expand It

Now expand beyond the rule - if everything you've ever made is trash, and we accept this as a truism for everyone, everything ever made is trash. While this may be an initially depressing thought, think of it as limitless opportunity. Everything that exists in the room you sit in and beyond can be improved and we have the innate ability to improve it.

Try this for an exercise - find something each day and pick it apart. Figure out what's good about it and what isn't. Even if you can't execute on the changes you envision, it's worth thinking about. It'll help develop the skills you need to examine your own work critically.

Tuesday, April 28, 2009

What Before Where

Jott

In September of 2006, the world was introduced to Jott, a web service that transcribes your voice notes into text and sends them to different places like Twitter, Facebook, or your calendar or blog. It’s a really neat service.

Here’s how it works. When you sign up for your Jott account, you’re given a phone number that you can call to leave your notes. The service answers the line and says one simple question - “Who do you want to Jott?” After you speak a keyword indicating the service you’d like to send the note to such as “email” or “Sarah” you are asked to speak out the note and they take care of the rest.

Shortly after joining Jott, back when there were free accounts, I noticed a problem. As soon as I dialed the number and Jott answered, that question always threw me. “Who do you want to Jott?”. It isn’t that it’s a particularly confusing question. In fact, I bet the team over there spent a lot of time deciding exactly what the question would be and how quickly it would need to be said in order to get to the point as quickly as possible. But every time I’d call and they’d ask, I’d stumble.

There were 2 reasons.

The first has to do with knowing exactly what to say - while there are plenty of great examples throughout the Jott site, when I’m on the move I have trouble remembering exactly what voice commands it can take. So, I pause for a second. If it were a human on the other end of the line, I could say something like - “Oh crap, I can never remember that.” But, a computer is much more touchy. No matter what I say, Jott thinks it’s a command. So I freeze.

The second reason I’d screw up had to do with the context of the situation. You see, although the transcription service was sometimes human-aided, it was far from perfect. And I knew, from reading around, that some of the people doing the transcription were not native English speakers. So, whenever I’d call Jott, I’d be thinking 2 things - “get soup at the grocery” and “enunciate.” Unfortunately for me, 2 things is about all I can keep in my head at once, so when the question came up asking me where I wanted to put this particular note, I’d mess up.

What to do?

Other than fixing my brain to deal with more things at once, I see 2 simple answers to this issue - a) better recognition software so I don’t have to worry or b) ask what before where. I think the latter is a bit more interesting.

All the time we deal with interfaces that ask you for detailed info before you get to the meat. For example, in almost every mail client, we’re asked who the email is to and what the subject is before we get to the actual message. But the real world doesn’t work like that. How many times have you started a letter by filling out the envelope? Not many? Of course not. Given the unconscious choice, you’d rather get straight to the message, then deal with the details.

Or what about when you start a new document. One of the first things we’ve been trained to do is save it so that if the program or computer fails, we’ll at least have something. But in order to do that, we have to give it a name and put it somewhere. Yet, with a pencil and paper, I can just start writing and worry about where to put it later.

Look around, I’m sure you’ll notice more.

I think as software designers, it might be an interesting idea to look at where we can flip this around. While it may defy convention to have an email client with “To:” and “Subject:” fields at the bottom, I’d be interested to see the user reaction once they got used to it. It might just be something bothering us that we haven’t noticed yet.