Archive for February, 2009

Ubiquity Photo Editor: A Sketch

Tuesday, February 3rd, 2009

The open Web has no good way to edit images. There are tools like Picnic, Sumo, and Aviary, but they all revolve around proprietary tools and destination sites. Making graphical edits is a fundamental action that should be available anywhere you see an image on the web.

Using Ubiquity as a platform for innovation, here is what an browser-based image editor might look like:

How You Use It

(1) Place your mouse over an image, or select it.

(2) Bring up Ubiquity and use the “edit” command. Alternatively, right-click to get a context menu or use the to-be-implemented mouse-based version of Ubiquity. This brings up the full-screen editor.

(3) The full-screen editor has four major areas arranged along the top: reshape, develop, effects, and done. Reshape gives you the basics of resizing, cropping, and rotating the image.

Develop let’s you fiddle with the contrast, hue, saturation, color curves, etc. Effects are for turning a photo into a reprise of the end of 2001: A Space Odyssey. The sub-actions take place down the right-side of the screen in a non-modal way, and are dependent on which of the four top actions has been selected. The interface takes some inspiration from Adobe Lightroom.

(4) When you are done editing a photo the tricky part begins. Most pages aren’t read-write (although, in the original web browsers of yesteryear they were). To “save” we are going to have to do something clever.

We can put the image back into the page, by replacing the image with the new one as encoded by a data URL. From there, you can right-click to save it or, if it is in an email, just send it off. The browser can even annotate the page locally so that when you browse back to the same page, you see your modifications, just like the “edit-page” command does in Ubiquity now. Of course, those changes won’t be shown to the rest of the world.

The other options, besides simply downloading it to your computer, is to save it by sharing it via social networking sites like Facebook, FriendFeed, or Flickr. Flickr currently accepts POST requests for uploading modified images. Hopefully, as time goes on and image manipulations becomes a more integrated part of the web, more and more sites will think of their content as user-mutable.

Using Open Web Technology

As the prolific Jacob Seidelin has shown, canvas is able to support a full range of photo-editing capabilities. You can see some of those capabilities in action with his canvas-based library Pixastic.

Jacob will begin leading work on a Ubiquity-based editor in around a month. I’m super excited to see where it goes. We’ll keep you posted.

If anyone else wants to get involved, join us.

Open Design: Five Lessons

Tuesday, February 3rd, 2009

The virtual Ubiquity team recently did an open redesign of the Ubiquity logo. The penultimate result (one more round of polish needed) was spectacular, as was the journey. The process even got some press.

Open design is hard. There are many opportunities for arguments to become entrenched and for a stop-energy to become insurmountable. For the Ubiquity logo redesign, none of these things happened. That’s mostly due to the passion and creativity of everyone that participated.

Along the way, five observations/lessons emerged:

(1) The process takes time. The freedom to do a couple iterations is key — giving enough to to absorb feedback and channel it into a better result. If there was one thing we could change about our redesign process, it would have been to budget more time for another iteration or two.

(2) Open-ended questions are answered in open-ended ways. If you want concretes answers, give concrete questions. The further in the design process you get, the more focused your questions should get.

(3) When making decisions, it helps to create a highly visible framework/rubric by which those decisions are being made/entries judged. This shapes and focuses the discussion and staves-off bike shedding.

(4) Have a focused point-of-contact to take feedback, incorporate it, and iterate on it. Although the Ubiquity logo design process was open, we had a single designer incorporating the feedback of many. This yielded a funneling process with a consensus conclusion, rather than a diverging process without a conclusion (a major danger with open design). In our case Sebastiaan de With was our gifted designer and point-of-contact.

(5) Constant communication is key. Use Twitter, blogs, news groups, etc. to keep the dialogue going among everyone in the community. Open design isn’t a one-way street, but it feels that way if there’s a dearth of communication. And when that happens it becomes a monologue, not a dialouge. (Thanks to John Slater for this observation).

Did anyone else have observations or lessons they learned from the Ubiquity logo redesign? Does anyone have wisdom gained from other open design projects?