Extended Off-Screen Keyboard

This is a quickie concept.  A while back I had an idea for a multi-touch keyboard. It was an interesting idea and I’m sure at some point it will become reality. However we’re a software company not a hardware player. What could we do in software using existing hardware?

What if you took the essence of that idea and made it as a complimentary tool to your existing keyboards:

The basic idea is that the device connects back to your computer and acts like a secondary display. This would be application sensitive so in PhotoShop you see visual tools on your secondary display and in Word you get editing tools.

Post to Twitter

Iphone Clipboard Concept for Cut, Copy, Paste

One of the current drawback of certain touch devices (Iphone) is it’s lack of copy/paste functionality. The difficultly in creating this functionality on a mobile device is that the interaction technique has to be non-intrucive to the core interface. 

Unlike a desktop application where you can toss commands into a menu the interaction model on a phone has to be more direct and gestural.  The copy/paste model I’m proposing tries to address some of these issues. 

When a user is viewing a core text area:

  1. They can scroll (tap + drag ).
  2. They can move the insertion pointer (tap)
  3. They can use the magnifier loupe to position the insertion pointer (tap+hold)
In my illustration you could activate additional copy/paste gestures:
  1. You can bring up the copy/paste pallet ( tap+tap near the insertion pointer)
  2. Once the panel is open you can mark a selection (tap+dragging) from the insertion point creates a selection. Similarly you could create a selection with two fingers marking both corners..
  3. When in copy/paste mode the keyboard is replaced by your recently cut/copied blocks of text or images.  You can tap a piece of text to insert it into your document 
Note: The tap+tap gesture is sometimes used in application to zoom however it is never used to zoom while editing text or viewing read-only text such as in emails or contact lists. 
Unfortunately at this point it’s not possible for third party application developers to write an extension such as this so it’s a concept sketch only at this point. 
P.S. Did you know we’re now developing and designing mobile apps?  Check out our latest design work for a new fitness startup focused on running. 

Post to Twitter

Threading Comments for Conversations

The mistake that a lot of websites make with comments is treating comments like data-structures. The website Digg.com recently released a new commenting system that was met with a lot of hostility. The commenting system is overly complex both in it’s use and it’s interaction.

A typical data structure approach would be to have each comment parented to another comment allowing things to cascade deeper and deeper. The problem with this is that conversations don’t work like that. Comments on a website represent a conversation between people. When you have a conversation you don’t have a structured flow. You talk, you interupt you introject, you catch parts of various conversations, you’re human.

Most commenting systems aren’t setup for this. The interface encourages users to have an intimate discussion with hundreds of people…. And we wonder why it doesn’t work well.

I took a stab at creating a concept for an alternative commenting system based on the Digg design. The objectives:

  1. Make it easy to read and understand.
  2. Have one central topic and make it easy to have secondary replies and off-shoot conversations.
  3. Optimize the design and layout for shorter comments (most comments are a couple lines)

Digg Comment System Concept

Concept explanation

The first column is the main thread of the conversation. You can follow the core comments reading straight down the page. Secondary comments and replies are read to the right of a comment in the second and third column. If there are more replies then fit in three columns a fourth column holds the additional replies as icons. Users can hover over the smaller icons to continue reading the conversation. They can also click to read the conversation on a seperate page.

This keeps the main conversation on topic and allows for deeper in-depth discussions to continue. This encourages people to actually talk and discuss a topic in smaller groups rather then commenting and moving on to the next story.  (This will also help people who have something to say to contribute without fear of being dugg down)

The layout assumes that most comments are short and allows for one, two or three columns for text. Most comments would be one column but if someone wants to write a lot that’s ok. The height of the comment would be flexible as well.

One key element of the design is that it greatly increases the information density. You’re no longer scrolling to track a conversation or expandin/collapsing nodes. The key conversations drift to the top and secondary topics are discussed in smaller sub-groups.

The key is to think about comments and discussions in terms of communication tools instead of as a datastructures.

Post to Twitter