Design walkthrough meeting on Thursday?
daphne at media.berkeley.edu
Fri Jun 6 18:06:04 UTC 2008
Just a thought... How about putting a picture of your rough sketches
on the wiki? Pretty illustrations are great but are not at all
necessary in early design -- and in fact there are many reasons not to
rush into finished mockups. I am a huge fan of wireframes whether
they be hand drawn sketches or basic boxes drawn in your favorite wire
framing application. They help us focus on the interaction rather
than the visual design which sounds like the stage you may be at.
As far as the 80/20 question. Can you say more about this? Are you
saying it meets use cases that fall into < 20% of pager use? It would
be great to see what use cases the design meets when you share the
The 80/20 rule is really about deciding what usage to support in the
component. We don't want the less often needed functions to get in
the way of those that are required more often. And the bottom line is
that most software tries to do way too much and it becomes
overwhelming to accomplish anything. What could be the case is the
20% you refer to are actually common use cases for a certain user
group and so perhaps we would decide to create an additional component
that is focused specifically on that user group. I'm kind of jumping
ahead here but this is a pretty common situation.
Looking forward to seeing the new design options!
On Jun 5, 2008, at 2:33 PM, Eli Cochran wrote:
> You're such a tease... show us!
> Then let us figure out a way to make the 20 work. We're a creative
> bunch, I'm sure that we can figure out a way.
> - Eli
> On Jun 5, 2008, at 1:40 PM, Jonathan Hung wrote:
>> I echo Colin's remarks. Today's meeting was really good!
>> During the discussion I became inspired and doodled two alternatives
>> to the pager design... and they're keyboard navigable too. Erin and I
>> chatted about it and it seems really cool, but one design falls in
>> 20 of the 80/20 rule.
>> Aside remark: what if programming for that 20 adds that "delight"
>> aspect to a design? Should that 20 be pursued?
>> I think Erin is going to help make some pretty illustrations of
>> them. :)
>> - Jonathan.
>> 2008/6/5 Colin Clark <colin.clark at utoronto.ca>:
>>> Hi everyone,
>>> On 5-Jun-08, at 11:02 AM, Colin Clark wrote:
>>>> Great, thanks for helping with the scheduling. It looks like both
>>>> times work for everyone. Let's go with the 9 am PDT time slot
>>>> you guys would prefer something a bit later in the day.
>>> Just a quick note to say how useful I found today's meeting. I
>>> a lot about the new designs, and I think we're in good shape to
>>> down the work and start iterating on user stories.
>>> For those of you who weren't at the meeting, here are some links to
>>> the in-progress designs:
>>> Inline Edit:
>>> Uploader revisions:
>>> Daphne and Jess are working on getting the component design pages
>>> a more common format along the lines of the Inline Edit Design
>>> Overview page, which will be great.
>>> Colin Clark
>>> Technical Lead, Fluid Project
>>> Adaptive Technology Resource Centre, University of Toronto
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org
>> Jonathan Hung / jonathan.hung at utoronto.ca
>> University of Toronto - ATRC
>> Tel: (416) 946-8312
>> fluid-work mailing list
>> fluid-work at fluidproject.org
> . . . . . . . . . . . . . . . . . . .
> Eli Cochran
> user interaction developer
> ETS, UC Berkeley
> fluid-work mailing list
> fluid-work at fluidproject.org
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
daphne at media.berkeley.edu
More information about the fluid-work