Presenting a wireframe to clients became an essential requisite part of the design process. But wireframes started to be handed out to clients for clear contextual reasons and not just because you “had to”. With the coming of HTML prototypes, we’ll discuss here what questions you should ask yourself before starting the design process.
The importance of wireframe
Whether they’re just a couple of boxes sketched quickly on a paper or detailed drawings with real content, every project now includes a wireframe of some kind. They provide guidance for designer… that’s why they are called wireframe.
Some see wireframes as simple blueprints for the general layouts but the relevance of wireframes shouldn’t be underestimated. Despite their sketchy and basic looks, wireframes are guidelines that follow both designers and developers all through the creation process.
Why wireframe
In most cases wireframes can bring valuable insights before starting a design, like for:
- forms
- general layouts
- news sites
- when you lack of content
In most cases, wireframes are usually easily approved by clients as they lack visual context like non-content graphic elements. In such contexts, black and white wireframe helps to get a clear picture of how the final result will look like.
Why not to wireframe
However, a wireframe can’t convey important design components. Grey boxes and lorem ipsum content can’t communicate how colours and contrasts influence content, the visual impact of brand design or the visual weight of graphics elements and the visual path created by colours, contrasts and components.
But because the purpose of a wireframe is so much intricate with design, it’s sometimes best to start with the design. In some cases, the client might not fully grasp the point of a wireframe, or simply doesn’t agree on the objectives you have set… and bad starts are never a good sign for a project. In these cases, it’s thus best to first agree upon a clear direction for the design and then start wireframing specific layouts.
Why Prototype
When the time comes to create the final design, what seemed logical at first might not fit the final output. Changes often have to be made as textures and images can influence relationships between elements.
And as time goes by, the further design moves away from functional requirements, the less effective becomes the wireframe. Inversely, a wireframe can also look dull and little attractive to a client when the actual design is actually very effective and impacting.
The alternative here is to create a quick HTML prototype of the future app. The prototype can integrate both a sketchy wireframe and a more final draft of design. Furthermore, the prototype is functional and some like those made with Justinmind Prototyper, even feature interactions and real data behaviour so that clients can test their future app before starting developing it.
Wireframes for information or promotion purposes lose their effectiveness, especially when it comes to questions of branding and images. You need the full design to assess the successful quality of the output. That’s why, in some cases, prototypes are more relevant than wireframes.
At the beginning of every project, all parties should assess the need to wireframe or rather to prototype, so that they can best serve the needs of the client.