True or False: In a perfect world we'd all createhtml clickable wireframes after the static ones have been done

30 Aug 2007 - 7:29pm
6 years ago
4 replies
432 reads
bminihan
2007

True. For relatively sized fonts, legibility, localization, above-the-fold
positioning, and reality-checking, it's the best step before moving to
"development". With the right front-end coder, it's only a little slower
than updating wireframes - once built and tweakable, sometimes faster.

This could be my special case, but with our outsourced developers,
prototyping also drastically reduces the ambiguity of docs alone, or doc'd
wireframes - sometimes, no matter how thorough your docs, you miss things
without a prototype - logical field sizes being one of them (incidentally,
why is 255 still the default "comment" field size, when most systems have
very few restraints on the size of data they can handle?).

Now that I think about it, in a truly *perfect* world, I wouldn't have a
job, as good design would be ingrained in the human psyche.

- Bryan
http://www.bryanminihan.com

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
Akanowicz Ron
Sent: Thursday, August 30, 2007 7:43 PM
To: IxDA List
Subject: [IxDA Discuss] True or False: In a perfect world we'd all
createhtml clickable wireframes after the static ones have been done

Same format at (static) wireframes, but done in html with all
clickable navigation and intra-copy links leading to the appropriate
pages.

Ron Akanowicz
Usability Consultant
786-853-1666

ron at softerwareconsulting.com
www.softerwareconsulting.com

________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://beta.ixda.org/guidelines
List Help .................. http://beta.ixda.org/help
Unsubscribe ................ http://beta.ixda.org/unsubscribe
Questions .................. list at ixda.org
Home ....................... http://beta.ixda.org

Comments

30 Aug 2007 - 8:30pm
SemanticWill
2007

For an assertion of this type to be false - I only need to find one instance
of this being false. It is, in fact - false for a very important reason -
you did not stipulate the type of application, the environment, and the
constraints of the system.
For web-based thin client sites and applications, it could arguably be true.
Try doing a meaningfully interactive wireframe in html for a thick,
installed application...
I currently do a significant amount of wireframing for thick client
applications, and clickable html wireframes are not just meanlingless, but
impossible to in anyway mimic the commands, behaviors and interactions of a
rich-gui application. Try using html wireframes to test the interaction of
dragging multiple drawn objects from a palette to a viewport, and then
connecting them. Now do the same behavior with a stamp tool from the tool
palette -- can't be done! Try designing html wireframes for an application
like Visio or Adobe Photoshop....not IN those applications - but FOR... and
you see my point.

Lets not forget than many, many people on IxDA don't currently - or haven't
ever - designed websites or applications - we also design thick client
applications, interfaces for hardware, for devices for which html wireframes
are completely inappropriate - if not both theoretically and practically
impossible.

On 8/30/07, Bryan Minihan <bjminihan at nc.rr.com> wrote:
>
> True. For relatively sized fonts, legibility, localization,
> above-the-fold
> positioning, and reality-checking, it's the best step before moving to
> "development". With the right front-end coder, it's only a little slower
> than updating wireframes - once built and tweakable, sometimes faster.
>
> This could be my special case, but with our outsourced developers,
> prototyping also drastically reduces the ambiguity of docs alone, or doc'd
> wireframes - sometimes, no matter how thorough your docs, you miss things
> without a prototype - logical field sizes being one of them (incidentally,
> why is 255 still the default "comment" field size, when most systems have
> very few restraints on the size of data they can handle?).
>
> Now that I think about it, in a truly *perfect* world, I wouldn't have a
> job, as good design would be ingrained in the human psyche.
>
> - Bryan
> http://www.bryanminihan.com
>
>
> -----Original Message-----
> From: discuss-bounces at lists.interactiondesigners.com
> [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
> Akanowicz Ron
> Sent: Thursday, August 30, 2007 7:43 PM
> To: IxDA List
> Subject: [IxDA Discuss] True or False: In a perfect world we'd all
> createhtml clickable wireframes after the static ones have been done
>
> Same format at (static) wireframes, but done in html with all
> clickable navigation and intra-copy links leading to the appropriate
> pages.
>
>
> Ron Akanowicz
> Usability Consultant
> 786-853-1666
>
> ron at softerwareconsulting.com
> www.softerwareconsulting.com
>
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>

--
~ we

-------------------------------------
n: will evans
t: user experience architect
e: wkevans4 at gmail.com

-------------------------------------

30 Aug 2007 - 8:52pm
Joseph Selbie
2007

"Try doing a meaningfully interactive wireframe in html for a thick,
installed application..."

Great point. Web applications usually require significant Javascript or
other client-side code to manage complex interactions -- and even if you
could do that quickly (which would be a welcome miracle) you also sometimes
need to have the interactions with databases and middleware to truly know
how your design is going to work.

We sometimes make that kind of effort for a single complex screen just to
make sure a key idea can really work -- but we never think to do a quick
build of all wireframes.

Joseph Selbie
Founder, CEO Tristream
http://www.tristream.com

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of W Evans
Sent: Thursday, August 30, 2007 6:30 PM
To: Bryan Minihan
Cc: IxDA List
Subject: Re: [IxDA Discuss] True or False: In a perfect world we'd all
createhtml clickable wireframes after the static ones have been done

For an assertion of this type to be false - I only need to find one instance
of this being false. It is, in fact - false for a very important reason -
you did not stipulate the type of application, the environment, and the
constraints of the system.
For web-based thin client sites and applications, it could arguably be true.
Try doing a meaningfully interactive wireframe in html for a thick,
installed application...
I currently do a significant amount of wireframing for thick client
applications, and clickable html wireframes are not just meanlingless, but
impossible to in anyway mimic the commands, behaviors and interactions of a
rich-gui application. Try using html wireframes to test the interaction of
dragging multiple drawn objects from a palette to a viewport, and then
connecting them. Now do the same behavior with a stamp tool from the tool
palette -- can't be done! Try designing html wireframes for an application
like Visio or Adobe Photoshop....not IN those applications - but FOR... and
you see my point.

Lets not forget than many, many people on IxDA don't currently - or haven't
ever - designed websites or applications - we also design thick client
applications, interfaces for hardware, for devices for which html wireframes
are completely inappropriate - if not both theoretically and practically
impossible.

On 8/30/07, Bryan Minihan <bjminihan at nc.rr.com> wrote:
>
> True. For relatively sized fonts, legibility, localization,
> above-the-fold
> positioning, and reality-checking, it's the best step before moving to
> "development". With the right front-end coder, it's only a little slower
> than updating wireframes - once built and tweakable, sometimes faster.
>
> This could be my special case, but with our outsourced developers,
> prototyping also drastically reduces the ambiguity of docs alone, or doc'd
> wireframes - sometimes, no matter how thorough your docs, you miss things
> without a prototype - logical field sizes being one of them (incidentally,
> why is 255 still the default "comment" field size, when most systems have
> very few restraints on the size of data they can handle?).
>
> Now that I think about it, in a truly *perfect* world, I wouldn't have a
> job, as good design would be ingrained in the human psyche.
>
> - Bryan
> http://www.bryanminihan.com
>
>
> -----Original Message-----
> From: discuss-bounces at lists.interactiondesigners.com
> [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
> Akanowicz Ron
> Sent: Thursday, August 30, 2007 7:43 PM
> To: IxDA List
> Subject: [IxDA Discuss] True or False: In a perfect world we'd all
> createhtml clickable wireframes after the static ones have been done
>
> Same format at (static) wireframes, but done in html with all
> clickable navigation and intra-copy links leading to the appropriate
> pages.
>
>
> Ron Akanowicz
> Usability Consultant
> 786-853-1666
>
> ron at softerwareconsulting.com
> www.softerwareconsulting.com
>
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>

--
~ we

-------------------------------------
n: will evans
t: user experience architect
e: wkevans4 at gmail.com

-------------------------------------
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://beta.ixda.org/guidelines
List Help .................. http://beta.ixda.org/help
Unsubscribe ................ http://beta.ixda.org/unsubscribe
Questions .................. list at ixda.org
Home ....................... http://beta.ixda.org

30 Aug 2007 - 8:51pm
bminihan
2007

Thanks for clarifying, and I completely agree. For brevity, I focused on
the assumption implied by the question, but couldn't imagine a clickable
prototype being created (or useful) for a ball peen hammer, for instance.

- Bryan

http://www.bryanminihan.com

-----Original Message-----
From: W Evans [mailto:wkevans4 at gmail.com]
Sent: Thursday, August 30, 2007 9:30 PM
To: Bryan Minihan
Cc: Akanowicz Ron; IxDA List
Subject: Re: [IxDA Discuss] True or False: In a perfect world we'd all
createhtml clickable wireframes after the static ones have been done

For an assertion of this type to be false - I only need to find one instance
of this being false. It is, in fact - false for a very important reason -
you did not stipulate the type of application, the environment, and the
constraints of the system.
For web-based thin client sites and applications, it could arguably be true.
Try doing a meaningfully interactive wireframe in html for a thick,
installed application...
I currently do a significant amount of wireframing for thick client
applications, and clickable html wireframes are not just meanlingless, but
impossible to in anyway mimic the commands, behaviors and interactions of a
rich-gui application. Try using html wireframes to test the interaction of
dragging multiple drawn objects from a palette to a viewport, and then
connecting them. Now do the same behavior with a stamp tool from the tool
palette -- can't be done! Try designing html wireframes for an application
like Visio or Adobe Photoshop....not IN those applications - but FOR... and
you see my point.

Lets not forget than many, many people on IxDA don't currently - or haven't
ever - designed websites or applications - we also design thick client
applications, interfaces for hardware, for devices for which html wireframes
are completely inappropriate - if not both theoretically and practically
impossible.

On 8/30/07, Bryan Minihan <bjminihan at nc.rr.com> wrote:

True. For relatively sized fonts, legibility, localization, above-the-fold
positioning, and reality-checking, it's the best step before moving to
"development". With the right front-end coder, it's only a little slower
than updating wireframes - once built and tweakable, sometimes faster.

This could be my special case, but with our outsourced developers,
prototyping also drastically reduces the ambiguity of docs alone, or doc'd
wireframes - sometimes, no matter how thorough your docs, you miss things
without a prototype - logical field sizes being one of them (incidentally,
why is 255 still the default "comment" field size, when most systems have
very few restraints on the size of data they can handle?).

Now that I think about it, in a truly *perfect* world, I wouldn't have a
job, as good design would be ingrained in the human psyche.

- Bryan
http://www.bryanminihan.com

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
Akanowicz Ron
Sent: Thursday, August 30, 2007 7:43 PM
To: IxDA List
Subject: [IxDA Discuss] True or False: In a perfect world we'd all
createhtml clickable wireframes after the static ones have been done

Same format at (static) wireframes, but done in html with all
clickable navigation and intra-copy links leading to the appropriate
pages.

Ron Akanowicz
Usability Consultant
786-853-1666

ron at softerwareconsulting.com
www.softerwareconsulting.com <http://www.softerwareconsulting.com>

________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://beta.ixda.org/guidelines
List Help .................. http://beta.ixda.org/help
Unsubscribe ................ http://beta.ixda.org/unsubscribe
Questions .................. list at ixda.org
Home ....................... http://beta.ixda.org

________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://beta.ixda.org/guidelines
List Help .................. http://beta.ixda.org/help
Unsubscribe ................ http://beta.ixda.org/unsubscribe
Questions .................. list at ixda.org
Home ....................... http://beta.ixda.org

--
~ we

-------------------------------------
n: will evans
t: user experience architect
e: wkevans4 at gmail.com

-------------------------------------

30 Aug 2007 - 9:04pm
SemanticWill
2007

Or documenting possible user interactions with a Wii!

I reread my previous post and don't want to come off snippy - I would love
if there was an easy and cheap wireframe-like prototyping tool for thick
clients, but have yet to find one. And while more and more front-end gui
developers are coming up to speed and able to do fantastic things with ajax
or flash - most management want those resources on production development...
That said, i think one purpose (imho), or wireframing, paper prototyping, in
visio and omni - and then "faking" interaction in powerpoint is that it is
fast and easy - I can crank out a couple of task flows for a user scenario
and then storyboard quickly enough to get useful feedback quick - and it
goes a long way to delivering better informed design specifications for the
gui architect to do logical architecture and development design documents.
Caveat - the process i use seems to work well for the types of applications
i mentioned but would love to hear success stories of people being able to
develop useful interactive wireframes for RIAs without sucking up
development resources.
-w

On 8/30/07, Bryan Minihan <bjminihan at nc.rr.com> wrote:
>
> Thanks for clarifying, and I completely agree. For brevity, I focused on
> the assumption implied by the question, but couldn't imagine a clickable
> prototype being created (or useful) for a ball peen hammer, for instance.
>
>
>
> - Bryan
>
> http://www.bryanminihan.com
>
>
>
> -----Original Message-----
> *From:* W Evans [mailto:wkevans4 at gmail.com]
> *Sent:* Thursday, August 30, 2007 9:30 PM
> *To:* Bryan Minihan
> *Cc:* Akanowicz Ron; IxDA List
> *Subject:* Re: [IxDA Discuss] True or False: In a perfect world we'd all
> createhtml clickable wireframes after the static ones have been done
>
>
>
> For an assertion of this type to be false - I only need to find one
> instance of this being false. It is, in fact - false for a very important
> reason - you did not stipulate the type of application, the environment, and
> the constraints of the system.
> For web-based thin client sites and applications, it could arguably be
> true. Try doing a meaningfully interactive wireframe in html for a thick,
> installed application...
> I currently do a significant amount of wireframing for thick client
> applications, and clickable html wireframes are not just meanlingless, but
> impossible to in anyway mimic the commands, behaviors and interactions of a
> rich-gui application. Try using html wireframes to test the interaction of
> dragging multiple drawn objects from a palette to a viewport, and then
> connecting them. Now do the same behavior with a stamp tool from the tool
> palette -- can't be done! Try designing html wireframes for an application
> like Visio or Adobe Photoshop....not IN those applications - but FOR... and
> you see my point.
>
> Lets not forget than many, many people on IxDA don't currently - or
> haven't ever - designed websites or applications - we also design thick
> client applications, interfaces for hardware, for devices for which html
> wireframes are completely inappropriate - if not both theoretically and
> practically impossible.
>
> On 8/30/07, *Bryan Minihan* <bjminihan at nc.rr.com> wrote:
>
> True. For relatively sized fonts, legibility, localization,
> above-the-fold
> positioning, and reality-checking, it's the best step before moving to
> "development". With the right front-end coder, it's only a little slower
> than updating wireframes - once built and tweakable, sometimes faster.
>
> This could be my special case, but with our outsourced developers,
> prototyping also drastically reduces the ambiguity of docs alone, or doc'd
>
> wireframes - sometimes, no matter how thorough your docs, you miss things
> without a prototype - logical field sizes being one of them (incidentally,
> why is 255 still the default "comment" field size, when most systems have
> very few restraints on the size of data they can handle?).
>
> Now that I think about it, in a truly *perfect* world, I wouldn't have a
> job, as good design would be ingrained in the human psyche.
>
> - Bryan
> http://www.bryanminihan.com
>
>
> -----Original Message-----
> From: discuss-bounces at lists.interactiondesigners.com
> [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of
> Akanowicz Ron
> Sent: Thursday, August 30, 2007 7:43 PM
> To: IxDA List
> Subject: [IxDA Discuss] True or False: In a perfect world we'd all
> createhtml clickable wireframes after the static ones have been done
>
> Same format at (static) wireframes, but done in html with all
> clickable navigation and intra-copy links leading to the appropriate
> pages.
>
>
> Ron Akanowicz
> Usability Consultant
> 786-853-1666
>
> ron at softerwareconsulting.com
> www.softerwareconsulting.com
>
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://beta.ixda.org/guidelines
> List Help .................. http://beta.ixda.org/help
> Unsubscribe ................ http://beta.ixda.org/unsubscribe
> Questions .................. list at ixda.org
> Home ....................... http://beta.ixda.org
>
>
>
>
> --
> ~ we
>
> -------------------------------------
> n: will evans
> t: user experience architect
> e: wkevans4 at gmail.com
>
> -------------------------------------
>

--
~ we

-------------------------------------
n: will evans
t: user experience architect
e: wkevans4 at gmail.com

-------------------------------------

Syndicate content Get the feed