Last night at about midnight this idea popped into my head. It was so good (to me) that I decided to write it on my iPhone, while half-asleep, because it was keeping me from going to sleep. I posted it.

Now that I woke up and read it I realize there are a lot of gaps there. Also I don’t even explain the problem very well.

So here is a repost of the idea with URLs explaining what I meant.

As a web developer one thing that is very easy to do is file uploads. There are so many ways to get a file from your computer to my site that people will argue about the best way to do it (it’s Nginx Upload Module, btw).

The problem is when someone using an iOS device hits the “browse” button on their iOS device. There is no file system available and so the button does nothing. Here is where Apple could solve all of this by making the “browse” button open your camera roll and allow you to select an image from it. (Surprise: this is what Android does.)

Since Apple doesn’t allow this many people end up making iOS apps that do everything a mobile site could do plus image upload. If there were just a way to fire up the camera or camera roll from a web page and choose an image to upload, many web developers I know would be very happy (me).

The URL terminology://q=word (yes, that’s a valid URL) only works if you have the Terminology application installed, or some other iOS app has registered to handle that URL. So if someone puts it on a web page only people with the app can click the link.

Here is my idea: make an application called Community Camera.app. Community Camera.app registers to handle any URL like camera://url=[…] where […] is a URL that accepts an image upload.

Someone clicks the camera:// link and it opens the Community Camera app with a location to post an image file. The user then either takes a picture or selects an image using the standard controls and then Community Camera.app POSTs that image data to the URL that was passed in.