The Mobile Presentation
A working definition
Most of what we still call a "presentation" was designed for a room. A projector, a speaker at the front, an audience facing forward, slides clicked through in real time. That format made sense for the desk and the conference room. It does not make sense for the device the world now reads everything on.
A mobile presentation is not a smaller version of a deck. It is a different kind of document, one with its own vocabulary, its own gestures, and its own job. The format has emerged faster than the language for it. This is a first pass at the language.
The mobile presentation rests on five principles.
1. Portrait-native
The phone is held in portrait orientation almost all the time it's used. Every other presentation format assumes landscape. The projector is wide. The laptop screen is wide. Even "responsive" decks shrink a landscape canvas until it fits, asking the viewer to rotate, pinch, or squint. A mobile presentation is designed for portrait from the first pixel. Width is the constraint that defines the canvas, not an afterthought to it.
2. Scroll, not swipe or click
On a phone, the dominant gesture is the vertical scroll. Forward navigation should be the gesture the thumb is already doing. A presentation that demands tiny arrows, horizontal swipes, or hunted-for navigation chrome is a desktop deck wearing a phone costume. A mobile presentation rewards the scroll. Every section, every transition, every interaction is triggered by it.
3. Linkable
A mobile presentation is one URL. The link is the document. No download, no app install, no login, no attachment. This is what lets it travel inside iMessage, WhatsApp, Slack, LinkedIn DMs, email. Anywhere a link can be pasted. Like a web page or a podcast episode, it is delivered by URL.
And the URL is the canonical destination, not a mobile-optimized fallback. The portrait flow is the presentation on every device, not a downgrade for phones. The desktop view does not get a different version with more on the screen. The format is portrait first, everywhere.
4. Asynchronous by design
The desk presentation assumed a presenter in the room. The mobile presentation assumes the opposite. It travels alone, it introduces itself, and it has to do its job without anyone narrating. This is a deeper change than it sounds. It means the first screen has to earn the second. It means the last screen has to ask for something. It means context, voice, and rhythm have to live inside the document, not in the room around it.
5. Signal-rich
Because a mobile presentation is delivered as a link, the sender can know what happened. Was it opened? How far did the viewer get? Where did they linger? Where did they leave? Mobile presentations return signal. This changes the loop. Every send becomes data, every data point sharpens the next send. The presentation stops being a one-way artifact and becomes the start of a conversation.
These five properties are not features of any one tool. They are properties of the medium. Any product that wants to make mobile presentations must honor them. Any product that ignores them is making something else: a deck, a PDF, a video, a webpage.
The implications are large. Sales pitches, school projects, investor decks, marketing pages, board updates, product walkthroughs, course materials, internal docs. All are being asked, every day, to live on phones. Most still arrive as PDFs or as landscape slide images that pinch into illegibility. The job of the mobile presentation format is to become what those documents turn into.
We have decades of language for what makes a good slide. Most of it descended from print and projection. We need new language for what makes a good mobile presentation. That is the work ahead.
Brent Brookler is the founder of Flow2. He has been building for the mobile screen since WAP and J2ME, and has spent the last twelve years on presentation software.