A Practical Guide to Writing for Mobile Readers
Adapting content for people reading on phones, with shorter paragraphs, clear headings and front-loaded information.
Why does it matter?
Many readers use phones, where long paragraphs and dense layouts are harder to read and navigate.
What are the numbers?
- Screen size less content is visible at once
- Scanning readers skim headings and first lines
- Reflow content must work at narrow widths
- Tap targets links need enough space to tap
What should I do?
- Keep paragraphs short
- Front-load key information
- Use descriptive headings
- Avoid wide tables where possible
- Test content on real phones
What should I avoid?
Avoid:
- Long introductions
- Wide tables without responsive handling
- Dense link lists
- Text embedded in images
When should I get help?
Short answer Bring in help when mobile readers engage less than desktop readers.
Where this comes from
- Nielsen Norman Group — Reading content on mobile devices
- W3C Web Accessibility Initiative — Understanding SC 1.4.10 Reflow
The figures and practices above come from the sources listed.
Working on something like this?
We take on Content Strategy work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.