EGOPOLY

A nice summary of latency, what it means to your web business and how to attack it. Thanks Derek for the link.

http://highscalability.com/latency-everywhere-and-it-costs-you-sales-how-crush-it

I don’t know why I read this blog, but I alway feel
[Ed. - nice grammar, dumbass] about 20% dumber when I do.

I wrote earlier about the iPhone’s poor SMS alert features, and how that made it unsuitable for my wife who is a doctor. I’m now 90% certain that a blackberry is the right choice for her.

The SMS thing is huge. I probably could hack something together, like have a web site that would keep sending SMS alerts every 5 minutes until she acknowledged it. But that could get very expensive/annoying in failure cases. Such as: the phone is in SMS coverage but not data, so you can’t stop the server from paging you.

Blackberry SMS alerts are fully customizable, and there is an alert LED as well. I don’t know if there is a persistent audible beep, but a long and loud alert plus the blinking red LED is good enough.

The other thing gets into the classic blackberry vs. iPhone debate. I won’t get into that too much, but mostly people talk about the touch screen keyboard vs. the physical keyboard; or screen resolution; or 3G quality; or integration with enterprise systems.

But all that is irrelevant to my choice.

First, the keyboard thing is a bullshit argument. Some people have a hard time with the touch screen keyboard, and they are aces with two thumbs. Some people are touch screen wizards. And others, such as me, are completely hopeless with both. The keyboard thing is largely a question of personal taste, and one is not better than the other, objectively. A touch keyboard gives you more screen to play with, a physical keyboard gives you different UI benefits (such as dozens of physical shortcut navigation possibilities.) It’s trade-off city.

When I really started thinking about what my wife needs for a smartphone, instead of thinking of an excuse to buy a shiny, pretty iPhone, I got into the real use cases. The primary one is this: it’s 3am, or she has 3 minutes between patients, and she gets a page/SMS. She needs to get to the email message that contains the voicemail quickly. If you imagine this use case on an iPhone, and really time it out, it would be something like this:

0. Pretend, just for argument that the incredibly quiet SMS alert on the iPhone actually gets noticed. In reality, it won’t much of the time, and then the entire work flow below gets delayed by 10 minutes to an hour.

1. Wake iphone (instant)

2. Slider unlock swipe (if you are sleepy because it’s 3am, you might have to do this twice); 1 second

3. Type unlock code. Oops, touched the emergency call button. OK, finally got it right. 5 seconds.

5. Open SMS. Find message. (2 seconds)

6. Touch Mail icon. Mail launches. (1 second)

7. Wait while Mail polls for new messages. (5 seconds)

8. Wait some more while Mail polls, because it just noticed the Wifi and reset it’s TCP connection. (15 seconds)

9. Or wait even more because EDGE/3G coverage is weak at the moment. (20 more seconds.)

10. OK see message that has the voicemail attachment and callback number. Listen to the attachment. Wait while it downloads (5-30 seconds.)

11. Listen to message, call patient. Call patient is instant because you can just click on the phone number in the either the mail message or the SMS.

I’ve been living with my iPhone for a year. I love it, it’s the best consumer electronic device I’ve ever owned. But this is the way it really is. I’m a computer programmer, I have zero stress in my job. I don’t really care much if reading email takes 30 seconds. If I’m checking email on my phone, it’s because I’m bored in the waiting room of the dentist and I have 30 seconds to waste. People aren’t throwing up blood while I’m waiting for an email to pop up on my screen. (Oh yes, I went there.)

You might think I’m being picky here, with these 1 and 2 second things. But put yourself in the situation. It’s night, you are tired, you are stressed. You probably haven’t slept much because you’ve got a lot of pages. Every stutter in the work flow is like a slap in the face, and your blood pressure ticks up a notch. Speed matters, and if you think 1 second is fast, then Google is going to eat your lunch when they eventually get around to entering your business.

OK, now walk through the Blackberry scenario. If you haven’t actually used a Blackberry for a while, you’ll have to trust me. This is the way it really is.

1. Wake Blackberry. (instant)

2. Type unlock code. Getting the code wrong/hitting the emergency call key is a lot less likely; one of the UI benefits of physical keys. (2 seconds)

3. Read SMS message (1 second)

4. Launch email (instant)

5. Oh look the message is already there, thanks to the insanely fast and reliable push infrastructure that RIM has perfected. Read message (instant)

6. Download voice mail attachment (5-30 seconds.) I’m going to guess this is about the same on the blackberry as the iPhone, but I don’t know that for sure, because I haven’t tested it yet. Based on current rumors, it’s possible that the iPhone has some weakness in the 3G stack, so it might be that the Blackberry actually is faster.

7. Call patient. The Blackberry can make a phone call from the selected phone number in the email, just like all smart phones. (instant)

With the Blackberry, there’s no stutter in work flow at all, except waiting for the download of what could be a long, rambling voice mail from a sick and occasionally demented patient. That’s pretty much unavoidable until networks get faster/better coverage.

A much better solution to all of this would be to forward the voice mail left on the office phone system to iPhone visual voice mail, or to the voice mail box of the Blackberry carrier, with caller ID intact. I don’t know of a way to do this with a self-hosted PBX (we’re using an Asterisk-based one now.)

Finally, there’s an obvious question here. Why doesn’t she just call her office voice mail and listen to the messages, once she gets the SMS? This is, in fact, what we do today. It’s not really satisfactory because of a problem with the office PBX: for some reason, incoming calls are very quiet. If you listen to them on the phone, it can be hard to understand what a sick/elderly patient is saying, because they talk quietly or mumble. For whatever reason, if you just play the audio file in email, it’s much clearer and louder. We’re working with our PBX vendor to fix this, but honestly, I’m about to put the thing back in the box and send it back. So the whole adventure of getting a smartphone to listen to voice mail is a pragmatic solution to vendor intransigence.

Why didn’t I know this? Thanks to Tim for clueing me in. How do you spelling clue-ing? cluing? Gah.

Nerf Herder IV

I’d like to buy an iPhone for my wife. She has a RAZR, and it’s such junk. She doesn’t get very much email, so the simple iPhone email app would be great for her to get her email and check her voice mail. (The phone system at her office sends voicemail as attachments.)

But there is one huge hurdle that’s blocking me. It’s a big problem, and it’s extremely frustrating because it could be solved so simply. It’s really just a tiny little thing, and it sucks that stopping me from buying that shiny, shiny new phone.

My wife is a physician, and part of that means being on-call. What happens is this: patients call the office at 2 in the morning, they leave a message, and the phone system sends an SMS message to her phone. Currently it’s her RAZR. So I set up her RAZR to have the longest, loudest possible SMS alert sound. It’s important, because if she happens to be at home, and her phone is in the kitchen, and she is in the other room, you want her to hear it. So she can call you back and prescribe your meds. But if she does happen to be WAY down the other end of the house, and the kids are yelling, and she doesn’t hear the loud, long alert, the RAZR has a persisent page. So 5 minutes later when she is back near the phone she’ll hear a little “beep.” Then she’ll know she has a page and she can return it.

The iPhone fails this use case in two ways. First the selection of tones is pathetic. Apple has decided that there are only 10 or so sounds that are suitable for an SMS alert. And they are all quiet and short little dings and beeps. Second, there is no persistence. The iPhone won’t beep every 5 minutes until you at least look at the screen and see the message indicator.

I even bought a custom ringtone in the hope that it would be selectable as an SMS alert. No dice. Wasted $0.99.

I don’t see how any physician can use an iPhone as their sole device. Apple has basically forced all of them to also carry a pager, or RAZR, or Blackberry. Why? I don’t get it. Most UI limitations Apple chooses really contribute to overall cleanliness and simplicity of the interface. But the SMS sound selection ALREADY has a choice of sounds. Why not let somebody choose annoying, long sounds for SMS? On the surface, it might seem like a tasteless, annoying thing to do. But in some use cases, it could save somebody’s life. Think about it.

I’m hoping some clever developer creates an iPhone app that will solve this.

[I know I could buy her an iPhone, and she could carry both the iPhone AND the RAZR. But... yuck, and you know, it costs money to have two devices.]

Update: I was hoping the iToner app from Ambrosia would work, but, alas, it only customize the phone tones.

Update: there is a lot of info out there on how to hack your iPhone to do this, but it requires Jailbreaking, which won’t work at the moment on 2.0.1. But that might be an option for us.

Create the file /etc/launchd.conf

Add this line:

umask 000

reboot.

This is very handy if you want a network-wide shared read/write NFS partition to actually, you know, work.

Where I was, August 8, 1985. My freshman dorm room. Golly, it looks exactly the same today.

It’s now possible to have bi-directional (read/write) access to you Google calendar via Apple’s fat iCal application. This seems to work even for Google hosted domain apps (which is what I’ve moved all my google accounts to, for home and work.)

http://www.google.com/support/calendar/bin/answer.py?answer=99358

Should be cool if it really works.