liveBook · Manning

Chunking

As explained in Design for Developers

A technique for dividing content or a task into smaller, manageable units or sequential steps.

Chunking divides a large task or body of content into smaller, manageable units. In mobile forms, it reduces overload, clarifies progress, and helps users focus on one step at a time. section 6.5.1

Use chunking to make long mobile tasks clearer and easier to recover from:

  • Separate payment, shipping address, and shipping options into individual screens. section 6.5.1
  • Show users where they are and provide clear controls to move backward or forward. section 6.5.1
  • Keep errors local to the relevant step so users can fix one problem without scanning a full form. section 6.5.1

A manageable checkout

Instead of placing payment and shipping fields on one long page, guide the user through payment, shipping address, and shipping options as separate steps. section 6.5.1

Figure 6.28 Break up larger task flows into individual pages when possible and indicate where users are in the flow to keep the task manageable.

Use the flow illustration to compare a large task with a sequence of individual pages and visible progress. section 6.5.1

How Design for Developers covers it

How deep it goes
Explains sequential screens, progress cues, and focused error correction, but does not specify implementation code.
Examples
Uses payment, shipping address, and shipping options as separate checkout steps.
What you can do after
Apply chunking by splitting a long mobile form into focused screens with clear movement between steps.
How it connects
Connects mobile web design with form design, navigation, and error handling.

Also explained in

Compare how 5 books explain chunking →

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.