A paragraph about the difference between a close-miked scrape and a distant room recording can read easily on a laptop and feel endless on a phone. At a narrow width, it may fill most of the screen. Add a release title, several names and a parenthetical note, and the reader has to keep track of all of them before reaching the point. The music is not too demanding for mobile reading; the page is making it harder to follow.
For an independent music blog, this is an editorial problem as much as a design one. Someone might open a review while checking a label’s catalogue, comparing a cassette in a shop or listening away from a desk. They need to find a name, follow an observation and return to a passage without fighting the layout. Good mobile editing does not simplify difficult music. It gives the details room to register.
A small screen changes the shape of an argument
A long section can look modest on a desktop. On a phone, each line holds fewer words, and headings, images and embedded players interrupt the text more often. The argument has not changed, but its rhythm has. If a description of a drone recording moves through its source sounds, processing and effect on the listener, those turns need to be visible. Otherwise they blur into one block of text.
Scrolling also makes context easier to lose. On a wide screen, a heading, image and opening paragraph may sit in view together. On a phone, a long caption or oversized player can push the heading away before the next paragraph appears. A clear transition tells the reader whether the article is still describing the sound, explaining its production or offering a critical judgment.
That does not mean every sentence must be short. A longer sentence can hold a careful comparison. Watch instead how many new facts, qualifications and references arrive without a pause. Keep a technical distinction when it matters, but give it space apart from the surrounding description. No one should have to reread a line just to work out which artist, recording or instrument “it” refers to.
Readable prose preserves the details that matter
Experimental music writing depends on distinctions that are easy to lose in a rushed edit. Field recordings are not interchangeable with a studio simulation of an outdoor sound. Cassette hiss may be audible, but hearing it does not tell us, by itself, how a work was made. Putting one main observation at a time within reach helps preserve that precision.
Take a sentence that introduces an artist, a label, a format, three sound sources and a comparison with another release. Splitting it need not cost any information. Identify the recording and format first. Describe what can be heard next. Then explain why the comparison matters. The evidence is the same, but the reader can check and remember it.
Let paragraph breaks follow changes in thought, not a word limit. A review might describe an opening sound in one paragraph, trace a change in texture in the next, then ask whether that change holds the listener’s interest. Some paragraphs will run longer than others. What matters is that each has a discernible task, so a reader can pick it up after looking away.
Place specialist terms with the same care. Electroacoustic, drone and contact microphone are useful when they name a method or sound more accurately than a loose adjective. Briefly explain an unfamiliar term when it first matters, then use it consistently. Replacing every precise term with something vaguer may make the prose look simpler while leaving the reader less informed.
Give readers reliable places to land
Headings should name the turn in the discussion
Headings help someone return to recording details, background or critical assessment without scanning the whole piece. Name what changes below them. “What the room contributes to the recording” is more useful than “Atmosphere” when a section examines reverberation and background sound. The heading need not give away the judgment; it should identify the subject.
Hierarchy matters on a phone, too. Use a main heading for a substantial section and a smaller one for a distinct point within it. Give every couple of paragraphs an equally prominent heading and the review starts to look like disconnected notes. Leave a long review unbroken, and readers have no easy way back to a particular observation.
Lists are for comparison, not for disguising prose
Lists work when the items do parallel jobs, such as information to check before publishing a release note or ways an embed might fail on a phone. They are less useful when each item is really a paragraph in an argument. For a mobile edit, these questions are worth checking separately:
- Names and titles: Can a reader tell which words name an artist, release or label?
- Transitions: Does a new paragraph make clear when description gives way to interpretation?
- References: Is a comparison clear without scrolling back several screens?
- Interruptions: Does an image, player or table break the flow between a claim and its explanation?
These checks matter in an archive. Someone arriving at an older review may not have read the publication’s earlier coverage. Give them enough context to understand the claim without retelling an artist’s entire history. An internal reference can add depth when it is genuinely relevant: a discussion of circulation through DIY networks might point to [Japanese Experimental Music and the Cassette Network](/japan-underground-tape-culture/). The paragraph at hand should still make sense on its own.
The page has to remain usable around the words
Clear prose cannot rescue a layout that demands pinching and zooming. Body text should resize naturally, have comfortable line spacing and avoid columns so narrow that nearly every word wraps. The page should fit the viewport without horizontal scrolling. Test it with the phone’s text size increased, not just at the designer’s preferred setting. Larger text exposes cramped headings, overlapping controls and containers that refuse to grow.
Contrast and spacing affect how long someone can comfortably read. Light gray type on a pale background is tiring; long runs of emphasis make emphasis useless. Give body copy strong contrast, save bold type for signposts and leave enough room between links and nearby controls for a finger to select the right one. A link should be identifiable without relying on color alone.
Wide material needs separate attention. A table comparing editions may fit a desktop column and spill off a phone screen. If the information is simple, a short list may work better. If the table is necessary, keep its row and column headings understandable and test how it scrolls at narrow widths. Shrinking all the type until it fits merely trades one problem for another.
Captions and credits deserve the same care as the main text. They may contain exactly the name or format detail a collector wants, yet end up tiny and cramped beneath an image. Keep them legible and close to what they describe. The blog’s piece on writing alt text addresses a separate question—how to describe visual information to readers who cannot see it—but an on-screen caption still has to work for readers who can.
Audio and images should support, not obstruct, reading
Embedded audio can be valuable in a music article, but a player may load slowly, take up most of a screen or behave differently across devices. Put it near the passage it helps explain, not between a claim and its evidence or in the middle of a sentence. Name the recording in ordinary text so the argument survives if the player fails to load. Playback should never be the only way to discover which track or passage the prose discusses.
Avoid autoplay. Someone may be reading in transit, listening to something else or using a screen reader; let them decide when sound begins. Before publishing, check the height of any promotional panel or repeated controls inside an embed. Two large players can bury a short passage of analysis.
Images can clarify a physical format, artwork or recording setup, but they should not make the page jump as they load. A suddenly expanding image can move the sentence someone was reading. Choose dimensions the layout can accommodate, and check whether labels or text inside an image remain meaningful on a phone. If an essential detail appears only in a tiny photograph of a cassette sleeve, put it in the article text as well.
Editing for mobile without writing down to the audience
Start with what the article is trying to do. A review might trace how a sound develops and judge whether its choices hold up. A label profile might explain how releases were selected or distributed. A guide to field recordings might distinguish listening practice from recording technique. Cut detours that get in the way, not the details that make the piece credible.
Read the draft at phone width and mark where you lose the thread. Often the fix is small: repeat an artist’s name instead of using “they” after several other names; put the format beside the release title; start a new paragraph when the writing shifts from what is audible to what is inferred. If a claim comes from listening rather than documented production information, say so. A shorter line does not make an uncertain conclusion more certain.
A practical pass can follow the order in which a reader encounters the page:
- Check that the title and first paragraph establish the subject without depending on an image or embed.
- Scroll at an ordinary reading pace and mark any section without a clear point of return.
- Increase the device’s text size; check paragraphs, headings, captions and controls for clipping or overlap.
- Try the article with images or audio unavailable. Names, descriptions and the main argument should still be intelligible.
- Open it at a second screen size and test links, tables and players by touch, not just with a mouse.
Use a real article for that test, not only a clean template. A long release title, italicized foreign-language text, a two-line credit and a player after a dense paragraph can expose problems a sample page misses. When fixing an older post, do not silently change its historical judgment along with the layout. If the assessment needs revision, handle that as an editorial update.
Readability is also about returning later
Music writing is often consulted again. A listener might come back for an artist’s name, a distinction between versions or the description of one passage. Page search helps, but the result still needs to make sense when found. Headings, consistent naming and direct sentences do that work. If a release appears under its full title once and an unexplained abbreviation later, the connection can be hard to recover on a small screen.
Before publishing a long review, pick a passage someone is likely to revisit—perhaps the paragraph where a recording’s background noise changes. Open it on a phone. If the heading has scrolled away, the subject is called only “it,” and the next sentence depends on a comparison made three screens earlier, revise those sentences in place. The observation can remain demanding without making the reader reconstruct its context.