Read posts about flickup

August 20

Best way to upload photos from an iPhone, and preserve location information (or: review of Flickup for iPhone) (Tiny Screenfuls (JoshB)) by Josh Bancroft

I use Flickr to store my photos online. You can “geotag” your photos on Flickr, to show where, exactly, they were taken (on a map). I’ve geotagged most of the 4000+ photos I have on Flickr. By hand, dragging them to the correct location on the map. What a pain.

The iPhone, with the new 2.0 software, can take pictures and tag them with your current location (if you have an iPhone 3G with real GPS, this location information is usually MUCH more precise). Suddenly, the dream of being able to get photos from the iPhone to Flickr, WITHOUT having to manually geotag or othewise manipulate them, seemed to be within reach.

So close, yet so far away.

Right now, there are a few ways to get photos from an iPhone to Flickr. The easiest, I think, is to setup the “upload by email” feature on Flickr. This gives you a secret email address that, when sent a photo as an attachment, uploads the photo to Flickr for you. This is how I get iPhone photos onto Flickr 99% of the time. The downside is, the photos get sent at a much smaller size (640×480) than they were taken at (1600×1200). On top of that, all of the “EXIF” metadata (what make and model camera took the picture, what exposure settings were used, etc.) gets stripped off of the photo when it’s emailed. This includes the geotag/location information. So it arrives at Flickr shrunken and lobotomized and unaware of where it was taken. So sad.

Once the App Store launched, Flickr uploader apps started appearing in droves. AirMe seems to be a popular one, but I tested it, and it didn’t preserve the geodata, (and I think it shrunk the photos, too). So I deleted it.

I’ve been watching the development of an app called Flickup with interest. The author, Martin Gordon (@kodachrome22 on Twitter), is someone I kind of know from Ars Technica. But most importantly, the feature list of Flickup looked promising - it can upload photos and preserve the geotag/location information. It’s not free ($1.99), so I waited a little longer to try it than I would have otherwise, but try it I have, and I’m pleased (if not 100% ecstatic) with the results.

First of all, Flickup DOES preserve the geotag information of the photos it uploads (with a caveat):

Flickup Geo Test


This is a photo I took from within the Flickup app, and uploaded straight to Flickr. The app asked me for permission to use my location (like all location-aware iPhone apps do), which I granted, et viola! The photo appears on the map where it was taken (to the best of my iPhone’s knowledge). Click on the photo then click “map” to see it - I can’t figure out a way to direct link to a single photo on the map on Flickr.

Even better, for photos taken from within the Flickup app (as opposed to uploading saved pictures from the Photo Album), the photos go up to Flickr in their full 2 megapixel 1600×1200 glory.

If you’re looking for an app ONLY to take pictures, and send them directly to Flickr, you can stop reading here. Flickup is perfect, and does everything you’d expect it to (you can edit the title, description, and tags of the photos, etc., too).

So what are the caveats? They have to do with uploading saved pictures from the iPhone’s Photo Album.

First, when you upload a saved photo from the album, it goes as a shrunken 640×480 version. Martin says this has to do with some limitations in the iPhone’s APIs (which I believe). He also says that the API is the cause of all the other EXIF metadata being stripped from the photos (which is probably what makes this such a problem in the first place - fix your stupid APIs, Apple!) Don’t count this against Martin or Flickup.

Second, when you upload a saved picture from the album, Flickup WILL geotag it, but it appears to grab your CURRENT location (it asks), rather than use the location data stored in the photo. In other words, it will geotag the photo with the location of where it was UPLOADED, instead of where it was TAKEN. Martin acknowledges this is sub-optimal.

Flickup from Photo Album Test


(A photo uploaded from my Photo Album, but geotagged at the time of upload.)

If what Martin says about the Apple APIs stripping out EXIF metadata (and again, I have no reason not to believe this is true), then there’s probably no way for Flickup (or any other photo uploader app) to preserve a photo’s ORIGINAL location information. The best we can hope for is how Flickup works - tag it with the location at the time of upload. If you take photos and upload them immediately, then there’s really no difference. But it’s super annoying that Apple comes SO CLOSE to making this work the way it should, yet falls short in the home stretch.

So, is Flickup worth the $1.99 in the App Store? If you’re a Flickr user that cares about a) uploading pictures at full size instead of 640×480, and/or actually preserving all that fancy location data that your iPhone can tack onto your photos, then yes, absolutely. Flickup is the way to go for full size geotagged Flickr uploading goodness.

There’s still room in this field for perfection. But it seems that it will depend on Apple making changes to the photo and location APIs on the iPhone, or some really clever developers figuring out ways to get around those restrictions. Guess which one I’m betting on happening first? ;-)

Posted in: apps , blog , flickr , flickup , geotagging , iphone , photos , review , software , upload
August 4

Crazy Easy (Martin Gordon's Blog (cptncelchu)) by Martin

Merlin Mann on iPhone development (from the SF iPhone Dev Camp):

Think about having the courageousness to make an app that is crazy easy. Instead of making a circus that’s really fun to play in, just make something that’s easy to get in and out of quickly without hassle.

Yes! This is exactly what I'm going for with Flickup. I wanted it to be dead simple to post photos to Flickr and I think I've gotten pretty close. While I don't want to add frivolous features, there are some that are reasonable to consider - uploading to a set, security settings, etc. I struggled to fit the metadata view onto one screen and now I'm faced with the challenge of adding these new features without undermining the simplicity that I was going for in 1.0.

Technorati Tags: , , , , , ,

Posted in: apple , applications , development , flickr , flickup , iphone , simplicity , software , user interface
August 2

Flickup 1.0 Is Out! (Martin Gordon's Blog (cptncelchu)) by Martin

A few hours after my post about being rejected from the App Store, Flickup was approved. If that was all there was to the story then I would have posted about it immediately. Sadly, however, it took nine days from the time Flickup was approved until the time it was actually available for sale on the App Store.

In preparing the now-defunct demo version of Flickup, I stumbled across the contracts page on iTunes Connect and realized that my Paid Applications Contract wasn't complete. I completed it on July 17th and incessantly refreshed the contracts page to see if it had been approved yet. When Flickup was finally approved hours after my last blog post, I was met with the status of "Pending Contract" and frustration returned. I would have thought that three days would have been enough time for someone to review the contract, but apparently that wasn't the case. Having given Apple some breathing room, I finally sent them an email on the 24th asking how long the process would take. Their response? Nothing.

I didn't hear anything from Apple until the contract was approval last Monday, July 28th and the status changed to "Ready For Sale." When I finally got tired of searching the App Store every few minutes to see if Flickup was listed, I sent Apple another email. Again I received no response. It wasn't until I saw a tweet from Jon that I learned that Flickup had finally been posted and that the three week ordeal was finally over.

When I first started working on Flickup I set a lifetime sales goal ("If only X number of people ever buy the app, I would be satisfied"). I'm happy to say that I reached 10% of that target in the first full day alone. Since the app went live, I've been answering support emails (already!), pushed out (well, submitted to Apple anyway) a new version with some bug fixes, and already started working on some new features.

Now go out and buy it!

Technorati Tags: , , , , ,

Posted in: apple , applications , development , flickr , flickup , iphone , software
July 22

Rejected (Twice!) From the App Store (Martin Gordon's Blog (cptncelchu)) by Martin

I am now a proud member of the elite group of developers who have had applications rejected from the iPhone App Store.

The application I have been working on since a few weeks after the SDK came out is Flickup, a simple Flickr uploader. When Apple announced the July 7th deadline, I pulled an all-nighter that day to finish it up and submitted the app to Apple around 6am in order to meet the 3pm deadline for inclusion in the App Store at launch. When the App Store is launched on Thursday/Friday, my app is nowhere to be found and the status remains "In Review". I sent an email on Saturday to Apple asking why Flickup was still in review and I received a non-response three days later telling me that "In Review" means my application is being reviewed by Apple. I responded immediately clarifying my inquiry and I finally received this response yesterday:

At this time, Flickup cannot be posted to the App Store because it does not allow the user to logout or change the Flickr account that they are using.

In order for your application to be reconsidered for the App Store, please resolve this issue and upload your new binary to iTunes Connect.

This is a perfectly valid critique, and an oversight on my part, but did it really take them two weeks to tell me about it? Would they have even told me had I not emailed them about my app's status? In any case, the time it took to get a decision on Flickup gave me time to fix some bugs, and of course add the required logout functionality.

As an aside, the Flickr Authentication API's Implementation Guidelines merely states, "Users must be provided with 'logout' functionality." The API documentation does not provide any way to revoke tokens and log users out. I had to resort to directing users to their revoke permissions page instead.

In the mean time, the App Store turned one week old and gripes about the review functionality sprouted everywhere, particularly with regard to the ability for people to review an app without actually having used it. This "feature" of the App Store prompted the cheapskates out there to use reviews as a medium to complain about price. Taking this to heart, I spent some time last week preparing a demo version of Flickup that would allow people to sample the app before dropping two Washingtons on the full version. I submitted the demo version on Friday and received a decision today:

Flickup Demo cannot be posted to the App Store because it is a beta or feature-limited version. Any reference to demo or beta needs to be removed from the binary and metadata. Free or "Lite" versions are acceptable, however the application must be a fully functional app and cannot reference features that are not implemented or up-sell to the full version.

In spite of the lightning fast turnaround time, I am still just as angry about this rejection than the last one since there was no prior warning (in program agreements or otherwise) that demo versions would not be allowed. It's hard to believe that Apple isn't aware that people are crying out for demos and trials; going as far as explicitly prohibiting them (while letting all other sorts of crap through) is nothing short of infuriating.

Technorati Tags: , , , ,

Posted in: apple , applications , development , flickr , flickup , iphone , software