What the f*@# do you mean you don’t have an iPhone?

You can file this under rant.

One of the things that boggles my mind, is when someone in the mobile space says that they don’t own an iPhone.

Whoa!

Hold your horses.

Before you start prattling on about the whole Samsung/Apple debate (Winston), know that that’s not where I’m going with this.

Simmer down now.

iPhone is just a placeholder.

The title to this post might have been “What the f*@# do you mean you don’t have an <insert name of mobile device here>?”

But that didn’t quite roll off the tongue.

Feel me?

Honestly, I could care less about your mobile device preference.

Apple, Samsung, HTC, LG, Nokia, Motorola, I could give a rat’s ass what you like.

As long as you own a smart phone capable of approximating the intended feature or functionality you’re trying to vet, we’re cool.

But when you’re building a mobile site, developing an app, using QR codes, or integrating augmented reality…

ANYTHING that requires a proper smart phone to experience…

And don’t own a proper smart phone…

You. Sound. Crazy.

At least to me you do.

I can’t tell you how often I’ve talked to folks about how a feature works or is supposed to work.

And learned – in the midst of that discussion – that they’ve never actually tested the issue being discussed on a device.

Or, worse yet, that they don’t even own the friggin’ device to test on.

I mean really?

How do you form your lips to critique something you’ve never tested?

Why are we even having this discussion?

Trying to describe a function or feature to someone who doesn’t have the device in question is like trying to describe color to a blind person.

No. It’s actually worse.

Especially if that person is making decisions in the absence of valid information.

Sure, wireframes, mock ups and emulators can help you imagine what the finished product will be like.

And they’re great for what they’re for – modeling.

But there is nothing like experiencing a thing on the platform for which it was intended.

And there’s nothing more valuable than getting feedback from an actual user.

Now, truth be told, I used to be one of the people of whom I speak.

Back in the day, I blacked out on Android users, but never owned an Android device.

My opinions of Android’s inadequacies were wholly based on conjecture not fact.

I have since seen the error of my ways, copped a Samsung GS3 and tested countless other Android devices.

So the disdain I now feel for Android devices, is steeped in fact.

But I digress.

My point is, don’t be like the old ignorant Stephen, casting stones in a glass house.

Be like the new Stephen, who opens the window to cast his stones carefully and with precision.

Now class, what have we learned today?

1. Stephen has a low tolerance for BS.

2. If you’re developing for mobile, you’ve got to have a mobile device.

I’m done.

Rant over.