Work is read inside something: a scrolling app, a paged reader, a browser, or a printed book. Each of these treats the same pages differently, and several of the structural tools available to a comic exist only in some of them. Making work without knowing which container it will meet means several of those tools are being used on faith.

This is a practical matter rather than a purist one. The difference between a spread and an endless column changes how a scene lands, and no amount of drawing quality compensates for a structural device that the container does not support.

Scrolling removes the page turn

The concealed reveal after a page turn, described in the piece on panel rhythm, does not exist in a scrolling container. The reader moves continuously and sees what is next arriving, so surprise has to come from pacing and from vertical spacing instead.

Vertical formats developed their own equivalent: long empty stretches that delay the next panel. That is a genuine substitute and it has to be designed in, which means a work made for pages and reflowed into a scroll loses the device and gains nothing in its place.

Paging preserves structure and adds constraints

Paged readers keep the turn but frequently show one page at a time on a phone, which destroys the spread. A composition designed across two facing pages becomes two unrelated images, and any element crossing the gutter is cut in half.

Where both single-page and spread reading are likely, the safe approach is to compose so each page stands alone and treat spreads as an enhancement rather than a requirement. That is a real constraint on layout and it is better accepted than discovered.

Apps impose their own processing

Containers resize, recompress and sometimes crop. Lettering sized comfortably at full resolution can arrive unreadable, and flat colour can arrive banded, which is the compression behaviour described in the piece on delivering animation applied to stills.

Testing in the actual app, rather than in the file, is the only way to know. It regularly reveals that a carefully judged panel has been rendered at a third of the intended size and half the intended contrast.

Readers choose the container

Creators tend to design for the container they use themselves, which is usually a large screen. Most readers are on a phone, in an app, in short sittings, which is the reading situation described in the piece on one-thumb readers.

Knowing the actual distribution matters. If ninety per cent of readers are scrolling on phones, designing for print spreads is designing for almost nobody, however satisfying the spreads are to make.

Making work that survives several containers

The durable approach is to keep the structural weight inside individual pages, use spreads and turns as enhancements, size lettering for the smallest expected container, and avoid designs that depend on adjacency. That work reads acceptably everywhere rather than perfectly in one place and badly elsewhere.

Where a work is genuinely built for one container, say so, and produce a separate version for others rather than letting an automated reflow ruin it. That is the same edition argument made in the piece on re-editing for a market.

Offline reading and file size

Readers download for offline reading more than creators expect, and file size affects whether they bother. Very large files fail to download on poor connections and get abandoned, which loses exactly the readers who were most committed.

Providing a reasonably sized version alongside a high-quality one solves this. It is the same reasoning as sizing images for the web, and it costs one export.

Accessibility settings are the part nobody tests. Readers use larger text sizes, inverted colours, reduced motion and screen readers, and a container will apply those to whatever you supply. Text baked into an image cannot be enlarged or read aloud, which is worth knowing before deciding that all lettering belongs inside the artwork.

Designing for where the work is read

Find out which containers your readers use, keep structural weight inside single pages, treat spreads and turns as enhancements, letter for the smallest case, test inside the actual app, and provide a sensible file size. That covers nearly all of it.

Characters here are fictional and unmistakably adult in every format, as set out in the reader agreement.