So by now most of you have heard about Google Gears. If not here's the deal:
"Google Gears is an open source browser extension that lets developers create web applications that can run offline."
Google Gears is a fully functioning relational database that lives within a browser plugin and gives programmers access to it to it's structure. This allows for off-line editing of data and post-off-line syncing.
So the question is: What does Google Gears mean for Interaction Designers who design web applications?
Well, it looks like this may be the year of multi-touch. Last week, Microsoft announced a new multi-touch digital coffee table called Surface, to be released Winter 2007. Below is the first of three videos they released.
Bill Scott of Yahoo! posted a short article about how he uses an "Interaction Matrix" to document rich interactions. I really like this approach because of how it explicitly details out each actor and state within the interaction.
Luke Wroblewski wrote a piece over at UX Matters on the topic of Selection-Dependent Inputs. In short, these are forms that have fields that depend on a choice made previously in the form. Luke goes on to give 8 solutions/patterns for this type of UI problem. While the solutions are good, it got me thinking about good experiences that I have had with forms.
Software that claims to make the documentation process easier always catches my eye. I am a big sucker for it. They make claims such as: time wasted creating boxes and arrows will no longer be, life will be better for everyone, and documentation will be more agile and easy to create and maintain.