We’re working on a new site at work, and it utilizes WordPress in a big way. (yay!)  Worlds are colliding… Just in time for WordCamp. However, there is also a community photo component that the client would really like to do with Flickr, largely due to “all the content which already exists” for their set of keywords. So we’ve been fooling with Flickr, and exploring the API, and trying to get approved for a commercial use, etc.

I do not like Flickr, and my lead developer agrees. The interface is not intuitive. Oh, it’s easy to upload photos and all, but if you want to do something other than basic upload, keyword and view - it could be a LOT easier to find the options, and figure out how to structure things properly. Number one rule of interface design - if a person has to do a bunch of Google-drive blog reading to figure out how to configure your service - your interface needs some clarity. Personally, I prefer Google photos, but I don’t do a lot of online photo hosting and sharing. This may be because I don’t have many friends, or the sort of friends that I would share pictures with, but mainly because I’ve just always used markalope.com to host any images I wanted to share, and leveraged any of the many free gallery generators to create my photo viewers. And another thing, the purchase (of Flickr) by Yahoo kind of scares me when it comes to utilizing Flickr as part of a site - there’s too much than can change in their TOS post-purchase. Still, the client want the “cachet” (which they persist in spelling “cache”) of the Flickr logo, and of course all the content they are convinced is already there.

So I guess maybe “cache” is the proper word after all….