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
designs.
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!
-Daphne
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
the
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.
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
unless
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
learned
a lot about the new designs, and I
think we're in good shape to
break
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:
+Overview
Pager:
Uploader revisions:
Daphne and Jess are working on
getting the component design pages
into
a more common format along the
lines of the Inline Edit Design
Overview page, which will be great.
Colin
---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource
Centre, University of Toronto
_______________________________________________
fluid-work mailing list
--
University of Toronto - ATRC
Tel: (416) 946-8312
_______________________________________________
fluid-work mailing list
. . . . . . . . . . . . . . . . . . .
Eli Cochran
user interaction developer
ETS, UC Berkeley
_______________________________________________
fluid-work mailing list
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
cell (510)847-0308
_______________________________________________
fluid-work mailing list
