Wednesday, May 27, 2015

OpenSeadragon 2.0: Forest-to-Tree Zooming

Today we cross a major threshold!

OpenSeadragon turns 2.0 and brings with it full support for zooming multiple high-resolution images in the same scene. Imagine all the pages of an ancient manuscript laid out on your screen and being able to seamlessly zoom in to the smallest detail on any page.

Back in 2008 when OpenSeadragon (then called Seadragon Ajax) was first released — when IE 7 was Microsoft's top browser and woolly mammoths wandered the frozen steppes — smoothly zooming a single image in pure JavaScript was quite the feat! We could only dream about the sort of cool multi-image scenarios Blaise demoed using a native app with GPU-accelerated code in his famous TED talk.

OpenSeadragon doesn't yet do everything shown in that video, but multi-image opens up some exciting new possibilities! Check out these demos for some inspiration:



OpenSeadragon + Rdio: swim across a sea of high-resolution album artwork, discovering new music as you go.




OpenSeadragon + Flickr: hop from image to tag to image on Flickr's most interesting photos of the day.




Chris Jordan Infinite Zoom: kick back and fill your screen with Chris Jordan's giant photo montages.


If you're new to OpenSeadragon, you should also check out all the great work people have done with the single-image version, such as this gigantic panorama of Mont Blanc and this amazingly detailed story-map of Central America.

Now what are you waiting for? Make some cool multi-image OpenSeadragon things!

Labels: ,


Tuesday, August 28, 2012

Fathom Philosophy

Fathom is simple enough, but it's actually got a lot of my design philosophy packed into it. I'd like to go into detail on each of these points eventually, but for now I think it's worth just getting the broad brush strokes out here. So, in no particular order:

Rather than focusing on the recommendation algorithm, I'm focusing on the presentation/exploration interface. Recommendation algorithms have gotten lots of attention, so it's hard to move the needle there; interface not so much, so there's lots of potential in that area.

Make it fun, inviting, and safe to explore… eliminate click friction; make it easier to just try something than it is to think about whether you should.

Rather than completely passive (like Pandora) or completely active (like Amazon), you get to choose and fluidly slide between levels of involvement.

By using APIs, I can focus on my strength (user interface) without having to build up all of the required data ahead of time. Also, by being connected to those other sites, we become just a little entwined… no website is an island anymore. This approach has its challenges, of course, but I feel it's worth exploring.

The interface scales to fit your window, however big or small.

The content is the interface, as much as possible. Controls appear when needed and disappear when not.

Animation is used to explain what's going on… you see where things are going to and coming from.

Focus on albums, rather than tracks.

Promoting album cover art and reconnecting it with the music in people's minds.

Minimize unnecessary clicks; for instance, you don't have to click an extra “play” after selecting an album.

An album's “neighborhood” of related albums gives it context… you start to get a sense for the space.

Having new albums come in with every move keeps things fresh and gives a game-like exploration feel.

Music is right-brain; your interface shouldn't be left-brain classics like the spreadsheet (iTunes) or huge pages of text (Amazon).

Of course Fathom is just one possible expression of these ideas. I look forward to future explorations along these lines. What do you think? Did I miss any? Are there other good examples of these principles out there?

Labels: ,


Tuesday, July 10, 2012

Things You Don't Mind Breaking

As anyone who lives with kids well knows, they're a potent force of destruction. It's tempting to hide all the breakables and fill their lives with indestructible plastic objects. Of course this means you can't have nice things. Worse yet, your kid never learns how to treat things nicely.

Our strategy has been to fill Caitlyn's life with nice things, breakable and not, which are nonetheless relatively inexpensive and easy to replace. We don't want them broken, but it's not a big deal if they are, and it's a valuable learning experience for Caitlyn. If it's a plate, she helps clean it up, and we get another. If it's a toy, we try to fix it, and if we can't, that's how you lose your toys. These days she routinely handles heavy glass jars full of food, for instance, and rarely is there ever an incident.

It seems to me that this is a good principle in design as well. If you treat your users like idiots and constantly protect them from themselves, then they'll just keep getting dumber. If you give them nice things and help them learn when they break stuff, you're helping them grow, and they'll love you for it.

Labels: ,


Sunday, October 07, 2007

Traffic Calming

We're discussing speeding in my neighborhood these days. Traffic calming is an important piece of the pedestrian-friendly puzzle. Fortunately, there's been a lot of energy in this area around the world recently. In many cases, conventional wisdom is being turned on its ear.

Some keys to effective traffic calming:
  • Perceived Danger. People have a safety threshold, and they drive right at the edge of it. Children and toys in the street, parked cars on the side of narrow roads, exuberant foliage that limits visibility, all serve to raise people's perceived danger and slow them down. Of course, this perceived danger can be accompanied by actual danger; we certainly don't want any of these kids to get hit. With this in mind, the question becomes how do we increase perceived danger while simultaneously decreasing actual danger. Fortunately, studies have shown that streets that look dangerous are often quite safe, due to the change in people's behavior. The key is to make the dangers and uncertainties as obvious as possible.
  • Antagonism vs Cooperation. The trouble with traditional traffic calming techniques such as speed bumps and stop signs is that they only serve to increase the antagonistic relationship between cars and pedestrians. Drivers are resentful of these periodic impositions and so they gun it between devices, wrapped up in their own inconvenience, paying even less attention to the pedestrians. Instead, you want to encourage brotherhood and cooperation between drivers and pedestrians. They need to relate to each other as people. In fact, just making eye contact and a friendly gesture is enough to slow a driver down.
  • "Going Somewhere" vs "Being Somewhere". We all have two modes, whether on foot or in a car: "going somewhere" on the highway or down a hallway, and "being somewhere" on a quiet residential street or a living room. In the former, our mind isn't really on where we're at; we're already thinking about where we're trying to get to. In the latter, we're present to the moment and responsive to the situation around us. In the case of streets, what mode you're in is greatly effected by the design of the street and the buildings that face it. Residential streets should feel like a living room, like a place you'd like to slow down and enjoy. Of course every city needs a mixture of of both modes; the trick is to make the distinction obvious.
With the above in mind, here are some suggestions for calming our streets:
  • Decorative "gateways" at the borders between the "going somewhere" streets and the "being somewhere" streets, so people feel like they're entering a special space, rather than just passing through.
  • Cobblestones at intersections or throughout the street.
  • City Repair-style murals on the surface of key intersections.
  • Benches on the side of the road, facing the street, to encourage the visible presence of people.
  • Paint the edges of the street to reduce perceived lane width.
  • Prominently displayed children's art, to show that children are present, in a more effective way than "Children At Play" signs.
  • Roundabouts, which tend to slow people down without the antagonistic effect of speed bumps and stop signs.
  • Block part of a lane off with planters.
For an interesting take on the subject, I recommend the book Mental Speed Bumps.

Labels:


Thursday, December 29, 2005

Organic Design

So how does one create in a more organic way? Some patterns to consider:

• Shorten Feedback Loops: The shorter the path from creation to use and back to creation, the more fluidly things can evolve. Examples abound: web vs. traditional publishing; wiki & blogs vs. traditional web; iterative software development vs. "waterfall"; smaller teams, focused projects (see Less as a Competitive Advantage); houses people can easily modify (see Stewart Brand's How Buildings Learn); small pieces, loosely coupled.

• Embrace Fuzzy Principles: Not everything that counts can be counted, and not everything that can be counted counts. Even if you don't have metrics for something, perhaps especially so, if you think it's important, make it an explicit guiding principle. This is made easier with shorter feedback loops: after all, metrics are just a way for us to grasp that which is too big for us to get an intuitive sense of.

• Trust Your Instincts: The human mind and spirit are amazingly rich breeding grounds for creativity. Don't let yourself get bogged down in justifications when you already know what's right. In fact, embracing fuzzy principles is possible only if you allow yourself to trust your instincts.

• Patterns, Not Rules: As we go about our work, we often discover useful practices that help us work better. It's tempting to turn these into rules to lock in their innovation. The problem is that rules are rigid and circumstances change. Better to declare patterns: nuggets of wisdom packaged for easy use. Trust in the individual's instincts to select the right set of patterns for the situation, thus shortening the feedback loop between pattern selection and pattern use. (Are patterns just rules you don't take strictly? Sure, in the same sense that tags are just loose keywords. Terminology matters.)

• Question Purity: Purity is very appealing, and it has an important place in the world, but probably not in your creation. Life is full of imperfection, constantly adapting. If you find yourself falling under the sway of a single design ideology or a pure mathematical formula, remember to leave a little room for funkiness.

• Grow, Don't Build: Think in terms of creating a supportive space and providing the right resources to let your thing grow. See Kevin Kelly's Out of Control.

• Observe Christopher Alexander's 15 Properties of Life: 1. Levels of Scale, 2. Strong Centers, 3. Boundaries, 4. Alternating Repetition, 5. Positive Space, 6. Good Shape, 7. Local Symmetries, 8. Deep Interlock And Ambiguity, 9. Contrast, 10. Gradients, 11. Roughness, 12. Echoes, 13. The Void, 14. Simplicity and Inner Calm, 15. Non-Separateness. For more detail, check out his The Phenomenon of Life, or this write-up (from a software perspective).

I'd love to hear your experiences using these and other related patterns.

Labels: