Wireframes
Out of context: Reply #16
- Started
- Last post
- 25 Responses
- madirish0
"it doesn't really address usability"
complete, total, fail on that assessment there, ukit; sorry. :(the #1 role a wireframe serves a team/project, is to account for all required functional items across a site/application within a rough structure said functional items should fall into. A second cue they lend to, is establishing a visual hierarchy through volumetric representations of items within a layout; void of any 'design' or aesthetic vocabulary. This is why b/w or greyscale works well, along with F.P.O. call outs and system buttons/form factors are appropriate.
An effective wireframe set does not include refresh, input, or interactive elements, IMO. Items of this nature should without question be detail noted as functional specs in an area of the page (side/column/etc) but not presented as elements within the wireframe itself. This is the role of the design comp artwork, and the nature of those elements and how they interact with the user should be worked out by the designer; not in a functional roadmap/spec document that a wireframe is.
Make sense?
- i want to make sure it is clear that this is purely my opinion, and not that of some sort of global 'standard'.madirish
- life would be easier if it were a global standard.monkeyshine
- again, i see where you're coming from , but you should keep in mind they are used differently by many agencies/ organizationsukit