liveBook · Manning

Low-fidelity wireframe

As explained in Design for Developers

A minimally detailed wireframe that communicates basic page layout, interaction, and functionality for rapid ideation and iteration.

A low-fidelity wireframe is a rough, minimally detailed page layout. Shapes stand in for images and text, while spacing, color, and typography remain unresolved. Its purpose is to communicate basic interaction and functionality quickly, before detailed design makes changes expensive. section 5.3.1

Use low-fidelity wireframes to:

  • Explore page ideas rapidly with pen and paper or digital tools. section 5.3.1
  • Check whether a layout and user flow work before investing in color, typography, or detailed visual design. section 5.3.1 section 11.0
  • Align users, stakeholders, and teammates around the basic direction of a page or application. section 5.3.1
  • Prioritize detail for the pages that need it most when a site has many screens. section 5.3.1

A rough home-page structure

Sketch a hero area as a large rectangle, place simpler blocks beneath it for supporting content, and use basic marks for text and images. Review whether the structure communicates the intended path before refining the wireframe. section 5.3.1

Figure 5.9 Low-fidelity wireframes have hardly any detail but convey a general idea.

Use the figure to see how minimal shapes can communicate a general page idea without detailed visual styling. section 5.3.1

How Design for Developers covers it

How deep it goes
Defines the format and its benefits, but stops short of prescribing detailed construction steps or visual styling.
Examples
Uses pen-and-paper or digital sketches, page shapes, hero sections, image and text placeholders, and early user-flow tests.
What you can do after
Build rough page concepts, compare early directions, and identify promising layouts before investing in detailed design.
How it connects
Connects wireframing with user research, user flows, iterative design, testing, visual design, and team alignment.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Design for Developers. The section links point to the parts of the book it draws on.