If I never see wireframe as a deliverable again, I will be a
happy man. The age of visio, omniograffle, axure, iRise, etc. I hope
come crashing down (now offense to all the coders who worked hard on
these tools), in favor of Fireworks, Catalyst, Flash, Blend and
Illustrator, Coda, etc.
Hi Milan,
Thanx for asking me to explain so nicely. ;-)
First, let me say this REALLY all depends on context and this is what
I would call part of the Pendulum effect of practice shifting. I.e. we
went from IMHO no user testing to focusing so much on the user we
forgot about the value of the
On Mar 12, 2009, at 6:20 AM, David Malouf wrote:
If I never see wireframe as a deliverable again, I will be a happy
man. The age of visio, omniograffle, axure, iRise, etc. I hope come
crashing down (now offense to all the coders who worked hard on
these tools), in favor of Fireworks,
Todd? If a best in class designer as yourself isn't using wireframes and
hasn't for ages (2 yrs in our biz = ages) it seems to me that you are just
being open to be nice.
1st, I didn't say don't do storyboards. I did say don't do wireframes and
YES I do teach my students to work in interactive
When asked what tool to you use to create that
presentation, (abstraction - that *deliverable* because it is a
common enough question that can be abstracted up a level); what did
John Maeda say in response?
Yes - this is a test Professor, and there is no sliding scale here.
~ will
Where
1st, I didn't say don't do storyboards. I did say don't do wireframes and
YES I do teach my students to work in interactive ALL the time.
Sketch scenarios/storyboards (that are ALWAYS human situated; more on this
below) low-fi interactive hi-fi interactive
So that means you start with
I agree. In my experience, any client who sees color and images focuses
on whether they like that color or whether that image fits, and don't
pay attention to the more important elements (at this stage in the
process), which include the related issues of clarity of navigation, how
easy it is for
On Mar 12, 2009, at 8:00 AM, Dave Malouf wrote:
Todd? If a best in class designer as yourself isn't using wireframes
and hasn't for ages (2 yrs in our biz = ages) it seems to me that
you are just being open to be nice.
I'm a realistic dreamer. A paradox of balance.
Actually, I'm not
FireWorks too, but here you have
usually added color and images (unless people are making grayscale
prototypes in FireWorks?)
Yep the core of my process revolves around wireframes in fireworks
with simple image maps. Super easy to maintain and iterate as you can
use the PNGs for the
This is one of those threads that won't ever tip either way, because 'it
depends'. Everything that's been said here is valid. Let me throw out one
more scenario (that I work in)- very large scale products. We
have separate folks who do
1. User Research/ Sketches/ Wireframes/ Process Flows/ UI/
I think it is worth emphasizing what Todd said. Wireframes will be
around until the sophistication of the buyer gets to the point where
they are not needed.
When doing consulting in large corporations or government, when you
developing new tools for complex processes, wireframes allow you to
On Thu, Mar 12, 2009 at 9:34 AM, Nicholas Iozzo i...@humansize.com wrote:
Reason two has to do with detailed screen specifications. When you
are designing an application to aid highly trained experts, the
business rules within the system need to be documented and
illustrated in a
Milan Courtney,
Why do you assume that I mean that low-fi interactive means using color?
I used to believe that whole message about distraction until I realized
through conversations about wireframes with clients that there were OTHER
distractions, or more importantly lack of focus. I found
On Mar 12, 2009, at 4:33 AM, dave malouf wrote:
But what is really clear to me is that what has been delivered as
wireframes in the past and all the efforts for making all these
stencils and palettes for wireframes has been where we have sold
ourselves WAY short.
Wow... I think I just woke
For what it's worth, the larger point isn't about wireframes. The
larger point is what Dave is saying. If all you create is wireframes,
then you're not really an interface or interaction designer.
Further, using software tools to create wireframes is largely
busywork. You can do wireframes
Andrei writes:
For what it's worth, the larger point isn't about wireframes.
The larger point is what Dave is saying. If all you create is
wireframes, then you're not really an interface or interaction
designer.
Response:
I completely disagree, which simply goes to show that there can be
very
On Mar 12, 2009, at 12:46 PM, Jim Leftwich wrote:
I completely disagree, which simply goes to show that there can be
very different informed perspectives on what constitutes an
interaction designer.
Honestly and with all due respect, you're basically talking out of
both sides of your mouth
I think we're in agreement regarding the difference between just
simple wireframes and flows that are composed of production source
images and elements.
But I do believe that some of us find it easier and more to iterate
and explore using digital tools, than by sketching. I do. And as I
stated,
18 matches
Mail list logo
