Sharing good and bad examples of interaction design?
23 Nov 2010 - 9:11pm
10 replies
2250 reads
We are thinking about creating a service for the interaction design community that allows members to:
- Quickly create 1-2 minute narated screencasts of interesting interaction design ideas they see on the web or have created themselves. For example a really smooth registration flow, etc.
- Maintain a personal stream of these vignettes.
- Share them with the rest of the community to generate discussion and spark ideas.
Most pattern libraries are more about aesthetics than about interaction design. Will the format of a short narrated screencast be better suited to the IxDA community?
Does this sound interesting to anybody? Is it worth doing?
Comments
sounds AWESOME !
Kunal. Why do you think it sounds awesome? What do you like or not like about the idea?
Thank you for bringing this up, this is a great idea and I would love to see it implemented.
Herbert
Herbert,
Why do you think this is a great idea? What do you like about it? How do you envision it working?
For all the reasons you already mentioned in your first post about your idea. I think it's great to have a tool that can help to collectively raise our understanding of UX issues.
Just imagine how helpful it could be if I need a solution for a particular problem and simply search your database to find what others have posted. The best part for me is that it would allow me to feel connected, integrated with all of you.
Herbert
On Nov 25, 2010, at 2:44 AM, Sani Elfishawy wrote:
> Herbert, > > Why do you think this is a great idea? What do you like about it? How do you envision it working? > >
I think its better to keep only authentic ideas in picture otherwise sooner of later it will become something like Twitter/Linkedin where people are mostly resharing the stuff.
--niteshÂ
On Thu, Nov 25, 2010 at 9:59 PM, herbert68 <herbert@reiningers.com> wrote:
Good idea!
Is it your intention to create a pattern library? In that case it could be an option to let the community group the vignettes under a shared design problem. To make it a 'universal' design pattern the community should add the context (when to use the pattern), the solution (how to use the pattern) and why this pattern is best practice.
The screencasts then function as good (or bad) examples, or as anti-pattern (exception to the best practice).
- Yohan
Yohan that is a wonderful idea.
You are so right there should be way to organize, categorize, and search the vignettes so they can serve as a sort of curated repository of reference intraction design flows. They can then be used for inspiration or as a guide to best practice when one is stuck with a particular design problem.
Is that what you mean?
I think like a pattern library but for interaction design flows. There are a few pattern libraries out there. Some recent ones like pattern tap however devolve into screenshots focusing on aesthetics of design.
Do you think the medium of a short narrated screencast where the submitter walks the audience through a flow would help keep the focus on Interaction Design rather than graphic design?
I would see a repository of interaction design flow as a first step towards a pattern library. A repository alone would be very useful for inspiration and for checking whether a certain interaction principle works or not. A design pattern takes the examples onto a higher, more abstract, level.
Pattern libraries like http://www.welie.com and http://developer.yahoo.com/ypatterns/ already focus on interaction design, there is little graphic design in these patterns. But you might say that these patterns cover (pretty static forms of) user interface design. I agree that there is little attention to task flows or state transitions. A chart, storyboard or screencast could certainly fill that gap.
Robert Hoekman jr covers interaction design frameworks in his latest book. Whereas a design pattern is a common solution to a specific, recurring problem (such as pagination interfaces), an interaction design framework is a set of design patterns used together to guide the design of a complete task flow.
What I like about the concept of frameworks (or archetypes) and your idea for the repository of screencasts is that they acknowledge the complexity of interaction design.
Good idea. Should work because you are explaining the interaction through a screencast. So it is easier to understand.