2 valid points of view 1 video:
http://www.youtube.com/watch?v=wx2nomhuMHseurl=http://www.plantingseeds.ca/blog/2009/03/skittles-useless-effort-or-great-experiment/
My 2 cents:
Is the new Skittle site the best use of social media? No!!
But, is it fitting for time (time = no one knows exactly
I followed the whole Skittles / Modernista hype on Twitter a couple
days ago, and I can't say that I am as enthusiastic about it as
everyone else.
Most of the reactions I saw flying by were similar to:
Wow, this is really great!
Great! Finally a company that let's the people represent them
Great
I saw that as a creative experimentation in application of networked
publics to a brand. Without having been paid to research their core
audience, without being paid to do a heuristic evaluation or usability
analysis, I can't say whether its affective or not.
Did Skittles scuttle its brand?
Just in terms of the user experience, I found the implementation awful.
I'm using chrome and if I use my mouse wheel to scroll, I get an
undocumented feature: row upon row of skittles menus. Even without
scrolling, there is no way to move the menu and it blocks out a large
section of the page,
I disagree. Even a one-page paper sketch can be a prototype - just a
low-fidelity prototype. See Carolyn Snyder's book, Paper Prototypes. I
often sketch ideas out before heading to Visio where they become
mid-fidelity prototypes. Once you add some colors and images - then it's
a high-fidelity
As far as tools go, if you are looking to just put together some
screencaps of potential interfaces, Teehan lax has a nice psd
template: http://www.teehanlax.com/blog/?p=447
I adapted it to illustrator here:
http://dfarkasdesign.com/downloadfiles/iphoneelements.ai
. . . . . . . . . . . . . . .
What sites like FB do really well, though, is encourage the small
congratulations/condolences that would otherwise get left behind.
This sounds like more bad news for greeting card companies.
Welcome to the Interaction Design
I really feel you folks are confusing mock-up with prototype.
IMHO, if I can't use it, it ain't a prototype. Maybe, human as
computer paper-prototypes fit the bill, but otherwise, a series of
screens, are mock-ups and an interactive click-through is a
prototype.
The distinction is important b/c
I agree with the point of view. All kinds of systems tend to be less
dependable and more autonomous requiring less control devices.
In system interaction, tangible, sound and visual feedback will
always be important.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted
On Mar 6, 2009, at 6:41 AM, David Malouf wrote:
I really feel you folks are confusing mock-up with prototype.
IMHO, if I can't use it, it ain't a prototype.
exactly. If it is not something that a user can actually engage with,
then its a sketch, or wireframe or picture. If there is no
Well, Webster's has this to say about it: Proto*type\, n. ... An
original or model after which anything is copied; the pattern of
anything to be engraved, or otherwise copied, cast, or the like; a
primary form; exemplar; archetype. Whereas a mock-up is a model,
often full-size, for study,
On Mar 6, 2009, at 9:42 AM, Katie Albers wrote:
Well, Webster's has this to say about it: Proto*type\, n. ... An
original or model after which anything is copied; the pattern of
anything to be engraved, or otherwise copied, cast, or the like; a
primary form; exemplar; archetype. Whereas a
Good lord this thread has just devolved into an embarrassment! (and
whatever happened to Saffer's admonition--no more tedious endless
definition threads!)
For the last time: http://www.ghostinthepixel.com/?p=130
And if you're still that confused about wireframes (and mockups) vs
prototypes, well
Hi everyone,
Apologies in advance for the long post. The agency where I work as an
IxD recently started an employee driven lunch and learn series where I
had the opportunity to introduce the idea of Heuristics to the group.
I covered off the basics and background from Nielson on and it was
all
Hi list
Since this thread is about the nature of prototypes, I might push for
a paper I wrote with some colleagues on the topic. It was published in
ToCHI last summer. You can download it here
http://www.box.net/shared/static/6cg0s7crjh.pdf
it is called The Anatomy of Prototypes
Best
Erik
The VMware User Experience Team is recruiting candidates for an
internship with our Server team in Palo Alto, CA
The summer intern will work with a UX lead on a project to specify
the interaction design for enterprise management and monitoring tools
for virtualized infrastructure environments.
As it grows, the company I work for is becoming more metric-driven.
Ultimately, I support the idea of having goals and metrics that help
us understand whether we're doing good work, the right work, etc.
I don't expect goals metrics to ever tell the whole story; the
world is squishy and numbers
Hi,
This is a very interesting approach. Some general points:
What is your measure of success for your new heuristics? There is
some lively debate about success metrics with some examples being:
number of problems found; number of major problems found relative to
usability testing, abiltiy of
Hello Alan,
You might want to get the book Built for Use: Driving Profitability
Through the User Experience
By Donoghue, Karen and Schrage, Michael D
The book never got the attention it should have, but it is full of
good information and stories about how to connect:
Business goals with User
There are several flavors of these sorts of things, but ironically setting
metrics to measure is often done without a well formed goal. Are you trying
to measure the value of your group? The value of people on your team? To win
arguments with other groups? It's usually a mistake to create metrics
Here are some classic references that discuss usability goals. The
earliest examples of usability specifications that I could locate came
from Tom Gilb in the late 1970s and early 1980s. Whiteside, Bennett,
and Holtblatt's chapter in the Handbook of HCI described usability
specifications and
I've been working on using desired user responses as a way to
communicate design intent. These responses are potentially measurable
goals, but more importantly they are effective at getting
non-designers to understand the core objectives of a project.
It's important to be able to measure design
A liaison between a Graphic Designer and a Programmer (an Engineer or
a Developer?) sounds like a Web or Interactive Producer to me.
For what that's worth.
On Mar 6, 2009, at 8:15 AM, Petra Bennett wrote:
I conduct research viability analyses on potential program ideas for a
College.
I
Applying an input mask to the input field is an elegant solution. Try the
jQuery masked input plugin:
http://www.conetrees.com/2009/03/blog/jquery-masked-input-plugin-increase-usability-for-masked-format-input-fields/
-Abhay
--
Cone Trees- User Research Design
http://www.conetrees.com
Liason sounds like an administrative support role.
While not a very accurate analogy, interaction design can be seen as
the third leg of a stool for software development with visual design
and coding being the other two legs.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25 matches
Mail list logo
