Brad Frost

A tel Tale Sign

In this responsive age, it's worth pointing out that mobile phones can make things called "telephone calls." Once upon a time, in an era before web forms and e-mail, the best way to make a dinner reservation, place an order, or get help from customer service was to pick up the phone, dial a number, listen for a few rings and (hopefully) talk to a human on the other end of the line. As it turns out, phone calls are still an amazingly effective (and human!) way to communicate. Yelp mobile users call a local business every other second thanks to prominently-placed phone numbers in their plethora of mobile apps. So yes, these mobile phones we're all carrying around are well-equipped to facilitate some phone call goodness. Here's some other mobile web phone call use cases:

Making Phone Numbers Linkable Max Firtman gives an in-depth look at how to make phone numbers clickable for mobile browsers. The most "standard" way is by using the tel: URI scheme, which looks like this:

Call Customer Service at 1-800-555-0199

This is a great way to bulletproof a phone number, even though most mobile browsers do a decent job auto-detecting phone numbers and converting them into links. iOS, Android, Opera Mini, Opera Mobile, Blackberry (even pre-6.0) all do a good job auto-detecting phone numbers in text and making them clickable. However, most mobile browsers don't stylize these links by default (iOS and Blackberry add an underline to the generated phone links), so it's a good idea to style tel links so they're nice and actionable. [caption id="attachment_2473" align="alignnone" width="650" caption="Chunky, actionable phone number links on Yelp and Google Local"]Yelp and Google Local tel links[/caption] Phone Numbers in Responsive Designs Tel links work great in mobile browsers, but unfortunately seem to fall apart when you get to desktop browsers (iPads and other tablets cleverly ask if you want to add the number to your contact list). [caption id="attachment_2491" align="alignnone" width="650" caption="Safari and other desktop browsers unfortunately don't comprehend the tel URI schema"]Desktop Safari doesn't like tel links[/caption] In their excellent book Head First Mobile Web, Lyza and Jason give a server-side detection example where the user experience is enhanced based on the device's ability to make a phone call. I concur for the most part, although I really just want desktops to do a better job launching communication apps (Skype, iChat, etc) and/or contact manager apps (I've done some testing on this and it works in some environments, but not in others). The tel URI-scheme is semantic in my eyes and think it should be encouraged. I don't want to style a and hope that all browsers will automatically detect a phone number. I suppose you could disable tel links and remove actionable styles for desktop browsers using Javascript, but again I like the idea of launching desktop VoIP software (used by millions and millions of people I might add). Yes, I know there are custom URI schemes for Skype and other apps, but the point is that any app should be able to leverage the app-agnostic tel URI scheme. And tel links make sense in other emerging contexts (TVs, car dashboards, tablets, etc). Obama's Missed Opportunities The reason I'm writing this post is because I had the opportunity to check out the newly-responsive Obama campaign site. I came across a giant red "Call" button while browsing the site on my phone, and naturally thought that I could make a call. Instead, it dumped me off to a non-responsive section of the site where the login screen got buried behind the virtual keyboard, rendering the section useless. [caption id="attachment_2520" align="alignnone" width="650" caption="Obama's site unfortunately doesn't let users make phone calls from their mobile phones"]Obama responsive site broken call button [/caption] This can be written off as a technical flaw, but I was also surprised to not see any promotion of Obama's historically very successful text messaging campaign. Again, mobile phones are capable of sending text messages and it would make a whole lot of sense to get people opting in to the program on the devices that can actually send and receive SMS. I'm not trying to nitpick on a single site or discredit a very nice responsive design, I'm just trying to use this as a reminder that the mobile context is much more than screen size. Mobile is a unique medium with it's own powerful communication channels built in. We should think about how we can take advantage of the capabilities of these devices to create better experiences. Phone Link Best Practices [caption id="attachment_2517" align="alignnone" width="650" caption="Sparkbox does a great job with their contact info: omnipresent, accessible, redundant and tappable"][/caption]

This post at surface level is quite simple: be mindful of telephone numbers on web pages. But it's really meant to keep up thinking about the mobile context as much more than just a small screen. When we create mobile sites: whether they be dedicated, responsive or other, we should be extremely considerate of all the opportunities and constraints the mobile medium provides.