Writing · 4 min read
How to write a story for a phone screen
A craft essay on writing fiction for a phone: message length, pacing with silence and delay, reveals that arrive rather than appear, and choices as replies.
A phone is the most intimate screen most people own. It is held close, read in the gaps of a day, and full of conversations with real people. A story told on it borrows all of that. It also inherits the phone's rules: small text, short attention, and an expectation that messages come from someone, at some time, for a reason.
These notes are about writing to those rules. The example throughout is invented: Jun texts his sister at 3 a.m. from an airport. His flight was canceled, and he has something to tell her before their mother wakes up.
One thought per message
On paper, a paragraph holds a thought and its qualifications. In a chat, people send the thought, then the qualification, then the correction. Splitting is not a stylistic tic; it is how the medium sounds. It also gives you control over timing, because each message is a beat you can place.
JUN: are you up JUN: sorry. stupid question it's 3am JUN: flight got canceled JUN: I'm fine JUN: I need to tell you something before mom's awake
Five messages, and the reader already knows three things about Jun: he is anxious, he apologizes for himself, and the canceled flight is not the real news. As a single paragraph, the same words would read as a summary.
Keep messages short enough to read at a glance
A message that fills the screen stops being a message and becomes a letter. Most lines should fit in a line or two of a phone bubble. When a character does send something long, make it an event: the sister's reply after twenty minutes of silence can be a wall of text, and its length is part of what it says.
Pacing lives in the gaps
Prose paces with sentence length. A phone story paces with time: the typing indicator, the delay before a reply, the message that never comes. Treat those as lines you write. “Typing…” that appears and disappears without a message is one of the most expressive beats the form has; the reader knows someone started to say something and stopped.
- A fast reply reads as eager, angry, or unguarded.
- A slow reply reads as careful, or as someone doing something else.
- No reply is a scene in itself, as long as the story acknowledges it.
- A time label, such as “4:10 a.m.”, tells the reader how long the silence really was.
Let reveals arrive
On a phone, information does not appear; it arrives. A photo lands in the thread. A new contact appears with a first message. A notification slides down over the conversation you are reading. Each of these is a reveal the reader experiences as an interruption, which is stronger than being told.
For Jun, the real news should not come from Jun. Let his sister ask why he was flying home a week early, let him start typing and stop, and then let a message arrive in a different thread, from a number the reader has not seen, that makes the answer clear. The reader connects the two, and that moment of connection is the reveal.
Every contact needs a thumbprint
Names are tiny on a phone, so voices have to do the identifying. Give each character habits a reader can spot without looking: capitals or none, full stops or none, emoji or never, long messages or single words. Jun writes in lowercase and apologizes. His sister writes in full sentences, which makes her sound calm, until she stops.
Choices are things the player sends
In a phone story, the player's choices are usually messages. That makes them intimate and a little dangerous: the player is putting words in their own mouth. Write the options in one consistent voice, the player-character's, and make them differ in intention, not just tone.
SISTER: Jun. Why were you coming home early? > "I'll tell you when I land." > "Can you call me? I can't type this." > "It's about Dad."
Each reply protects something different: Jun's control, his courage, or the truth. None is simply right. And whatever the player sends, the next message is the consequence, so the answer to a choice should come as a reply, not as narration.
End with something the phone can hold
A phone story does not need a final scene in the usual sense. It can end with a message left on read, a call that comes in and the screen going dark, or a photo that finally explains everything. Choose an ending that is a thing on the screen, not a summary about the characters, and let the reader sit with it.
If you want to build one, Pominis has a phone chat story format that handles the mechanics described here: threads, typing time and delays, photos in messages, time labels, and replies the player sends as choices. The how-to guide covers the steps.
