In a pair of recent posts, Andre Torrez outlined an idea for solving the “how do I get photos from my iPhone onto a website” problem. I like this idea, and I’d happily install this hypothetical Community Camera app if anyone ends up developing it.
The central mechanism for Andre’s idea is a new URL protocol
camera: (similar to
ftp:) that a simple camera application could claim control over. One such built-in protocol on the iPhone is
sms:, which lets you easily direct users to send an SMS message. For example, clicking on this link (with URL
sms:+12125551212) would switch you over to the SMS application with the phone number already filled in. Here is a handy list of other iPhone-supported protocols. But if you’re not reading this on an iPhone, pressing that link will probably give you an error message.
sms: links are supported, and make the process much more seamless for users. As far as I know (
correct me if I’m wrong), such a mechanism doesn’t exist yet. It exists! See update below.
The email workaround
One workaround solution, used by many web applications including Flickr, is to provide a special email address that allows you to upload photos as an attachment. The benefit is that every computer with a browser supports email links, smartphones and otherwise. The downside is the unwieldy sequence of steps you have to follow. In the best case scenario, a user has already saved the web app’s special email address to her contacts:
- Switch to the Camera app, take a photo or find the one you want from your library
- Press the “utility button” and choose “Email Photo”
- Fill in the email address from contacts and press send
- Switch back to the browser and wait for the attachment to be received by the web app
A number of factors complicate this process, starting with the initial messaging. The natural thing to say is “Email a photo to upload,” linked with a
mailto: URL protocol. But on the iPhone you can’t attach photos from the Mail app, it only works from the Camera side of things. So that “Email a photo” link should probably go to a page that explains the process outlined above, including the important step zero “add our special email address to your contacts.”
Email uploading requires that you’re willing to read a bunch of steps, understand them, and follow them. Additionally, the web application is left with no button that initiates the process and no way of giving feedback about whether it worked or not. If you reload the web app and you see your photo, then it worked. If not, maybe you’ll get a email bounce message. It’s a process that works okay for experienced users, poorly for novices, and that fails ungracefully.
Plus there is the implementation challenge of receiving and parsing email, which is kind of a pain in the ass. As an alternative to Andre’s plan, if somebody wants to write a general purpose email-to-upload service, I would find that pretty useful. Or does this exist already? I haven’t looked very hard.
Compare those steps above to the
camera: method (including step zero, “install the Community Camera application”):
- Press the “upload photo” link, with its “camera:” URL protocol
- Using the native app that appears, take a photo or choose one from your library
- When finished, the app switches you back to a page that has useful feedback
This is a better user experience, but it does require that someone go and write that native camera app (and that I install it). And unless there’s some way of checking for
camera: support, even this will require some additional explanation.
Yet another solution can be found in SMS, or its more advanced permutation MMS (Multimedia Messaging Service). Using the
sms: protocol mentioned above, I could create a link to
sms:email@example.com that behaves almost exactly like the email upload method, while avoiding some of its complexity. On the iPhone, you can attach photos from the Messages app, and you can send MMS messages to an email address. And since there’s a link that initiates the process, it allows web apps to give some feedback on the page in response to a
The downside to this method is that it requires the user to have a mobile plan with reasonable rates for sending MMS messages, and could fail ungracefully for users who aren’t fully informed about their mobile plan.
In any case, writing all this up has made me realize web browsers should let you detect whether a given URL protocol is supported. Browser makers, please build that into your next release!
Update: Andre tweeted a clever trick for detecting URL protocol support! Here’s how it might work in PHP:
// This will only work if the sms: protocol is supported
// If not, fall back on this other page
echo '<html><head><meta http-equiv="refresh" content="0; url=sms-not-supported.html" /></head></html>';