Public Voice Network
- Agencies in Amsterdam? 88
- Pic of the Day 70917091
- Help! 44
- blog 2349323493
- EC: Build - Pritt 99
- Car photography
- superfuture is malware??? 1111
- London in 3 days 1515
- Last day on the Job 3535
- Qwitter 148148
- post your local heros!
- CSS Text Replacement 33
- Scooters & Vespas 2727
- www.martin-brown.net 1010
- Who here owns? 6363
- Crisis in Burma 88
- Introducing a cat to a do… 55
- portfolio build 1212
- EC: Dimension Hatröss 1111
- Dogs in Cars - Postcards! 66
- You play guitar? 2020
- Show some recent work 737737
- Pul Fittion 22
- NSFW: Official Thread. 115115
Wireframes 2525 Responses
Last post: 1 month, 1 week ago | Thread started: Jul 8, 08, 3:27 p.m.
- doesnotexist
this is great
- Dog-earJul 8, 08, 4:37 p.m. – Permalink
- ukit
@ monkeyshine - I see where you're coming from with the total separation thing. On the other hand, it doesn't really address usability - I always thought one of the advantages of using wireframes was that you could nail down the most usable layout without worrying about the visual end of things. I guess ultimately it depends on who's involved in the process and what their roles and abilities are.
- Dog-earJul 9, 08, 12:33 a.m. – Permalink
- monkeyshine
Ukit, I totally agree. I think the problem is that you can't really nail down a layout without thinking about the visual end of things. It's much easier to be the designer who is fleshing out the wire frame (or at least intimately involved with the wire frame build).
I have issues with wire frames in general. In my experience, the wire frames go to the client for approval before design. When the IA (who likely has no design experience - and you can only hope they realize this) puts in visual elements like tabs or color the client can get fixed on that and think it's designed. Connected to this, sometimes a client will see a wire frame and not really understand what it is they are looking at or how they need to access it.
If wire frames were only used internally to guide the UI I'd be less concerned. I realize this isn't a perfect solution. In my eyes, a wire frame is meant to convey hierarchy and flow of content, not layout.
- Dog-earJul 9, 08, 3:52 a.m. – Permalink
- madirish
"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?
- Dog-earJul 9, 08, 6:26 a.m. – Permalink
- bulletfactory
taken from - http://www.digital-web.com/artic…
- Dog-earJul 9, 08, 7:51 a.m. – Permalink
- studderine
madirish has it down.
- Dog-earJul 9, 08, 7:52 a.m. – Permalink
