Marcus Andrey Study
Ler em português Library

Motion and Interaction · Step 4 · 6 min read

The spatial model of an interface

People remember where things are, even on a flat screen. Motion is how an interface tells them where a screen came from and where it went. How to map an app as a space, the three directions most products use, and the one promise every transition has to keep.

Two screens standing on a stage, one in front of the other, with dashed rails for their paths. Slide the pointer across: the front screen moves aside to the right and the one behind comes forward into its place, travelling the same way. That's this step: an interface is a place, and a transition tells you where the next screen was and where the last one went. This step has four lessons: the spatial model of an interface, navigation transitions, shared element transitions, and scroll and motion.Illustration: Marcus Andrey, drawn with Hairline (MIT, Lucas Marques).

A screen has no "where", until motion gives it one. Without animation, tapping a message just replaces one picture with another. Slide the message in from the right, and suddenly it lives to the right of the inbox; going back means going left. People build a map from those movements without thinking about it. Design the map on purpose and every transition becomes a little lesson in where you are.

What you'll be able to do after reading:

  • Explain what a spatial model is and why motion creates it
  • Map a product into three directions: sideways, deeper, on top
  • Keep the one promise of spatial motion: leave the way you came
  • Spot transitions that break the map, and fix them

1. An app drawn as a space

On topOverlays: closer to you, the page stays behind

  • Share sheet
  • ↑ ↓Rises from the edge it hides in, and goes back there
  • Delete?
  • ◎Fades and grows in place: it belongs to no edge

DeeperDetail: forward into one thing

  • Message
  • → ←Forward slides in from the right; back slides out the way it came
  • Reply

Top levelSections side by side, no order between them

  • Inbox
  • Calendar
  • Files
  • ⇄A quick fade between them: no direction to suggest
One small mail app drawn as a space, not a list of screens. Each layer has its own way in and out, and every motion keeps the same promise: if something arrives from the right, it leaves to the right; if it rises from the bottom, it sinks back there. That promise is the spatial model.Diagram: Marcus Andrey, CC BY 4.0, after Material's transition patterns and Apple's Human Interface Guidelines.

Most products use the same three directions, whether their designers drew them or not:

  • Sideways, between equals. Tabs and top-level sections. Nothing is "before" or "after" Calendar; it's just next to Inbox.
  • Deeper, into one thing. A list item opens its detail; a folder opens its files. The detail is "in front of" or "to the right of" the list, depending on the platform.
  • On top, for a moment. Sheets, dialogs, menus. They sit over the page, closer to you, and the page waits behind.

Material's transition patterns are built on these relationships. Its shared axis pattern is "used for transitions between UI elements that have a spatial or navigational relationship", and it moves screens along x, y or z to show it; elements with no strong relationship get a fade through instead (Material Components for Android, Motion; Material Design 3, Transition patterns).


2. Why motion builds the map

NN/g puts the purpose of this kind of animation plainly: when the person is already looking, motion can convey "how that element relates to other elements on the page and to any actions that the user has just taken" (NN/g, Animation for Attention and Comprehension, 2014). A cut from one screen to another gives no clue. A movement does: the new screen came from somewhere, so it must still be somewhere when it's gone.

Apple's guidelines make the same point from the other side. In their words, feedback motion that doesn't make sense can make people feel disoriented, and the example is spatial: "if someone reveals a view by sliding it down from the top, they don't expect to dismiss the view by sliding it to the side" (Apple HIG, Motion).


3. The one promise: leave the way you came

Everything in this step comes back to one rule. If something arrives from a place, it goes back to that place.

  • A detail that slides in from the right leaves to the right.
  • A sheet that rises from the bottom sinks back to the bottom. On iPhone, people expect to swipe a sheet down to dismiss it (Apple HIG, Sheets).
  • A card that grew into a page shrinks back into the same card, in the same spot in the list (Shared element transitions).
  • A dialog that faded in at the centre fades out there. It belongs to no edge, so it shouldn't fly off to one.

Keeping the promise is also what makes gestures possible. Because the detail came from the right, a swipe from the left edge can push it back; the gesture just follows the map (Gestures and direct manipulation).


4. Platforms have their own maps

You don't have to invent the space. Each platform has one, and people already know it.

  • iOS drills into detail sideways: the new screen slides in from the side, and Back, or a swipe from the edge, returns (Apple HIG, Gestures). Sheets come up from the bottom; tab bars switch without a direction (Apple HIG, Tab bars).
  • Material shows parent to child on the z axis, as depth, and steps in a flow on x or y; a bottom navigation bar uses fade through (Material Components for Android, Motion).
  • The web has no single map. A site's transitions are whatever its designers choose, so they need to be decided, written down and kept consistent.

Use the platform's map when you build for a platform. On the web, pick one and keep it.


5. Depth without much movement

You can show space without moving things far. Small cues do a lot:

  • An overlay dims the page behind it: the page is further away now.
  • The screen you left slides back only a little, and a bit darker, as if it went behind the new one. The next lesson does exactly that.
  • A shadow or a slight scale shows that something lifted towards you.

These cues matter for reduced motion. When large movements are replaced with fades (Designing a reduced-motion version), a dimmed backdrop and a consistent order still tell people where they are. The map should survive without the motion that taught it.


6. Common mistakes

  • Every transition the same slide, whether the screens are siblings, parent and child, or a dialog.
  • Arriving from the right and leaving downwards.
  • Tabs that slide left and right as if they had an order, then don't when you skip one.
  • Inventing a space that fights the platform's (a detail that rises from the bottom on iOS).
  • A map that only exists in motion, and is lost under reduced motion.

7. Vocabulary

Term Meaning
Spatial model The map in people's heads of where screens are relative to each other
Hierarchy (depth) Parent and child: a list and its detail
Siblings Screens at the same level, like tabs
Overlay Something placed over the page for a moment: a sheet, a dialog, a menu
Axis The direction a transition uses: x (sideways), y (up and down), z (depth)
Continuity The sense that it's the same world before and after a change

8. Try it (no tools needed)

  1. Take a product you know and draw its screens on paper as a space: siblings in a row, details further out, overlays on top.
  2. Open it and watch every transition. Write the direction each one uses next to your drawing.
  3. Circle every place where something leaves differently from how it came.

Reflection questions: Could a new person draw your product's map after five minutes of use? Which screen has no clear "where"?


9. If you already practise

  • Put the map in your design system: a diagram of the three directions and which transition each uses, next to the Motion tokens.
  • Review navigation in pairs: every "in" in a spec needs its "out".
  • When a flow feels confusing, check the motion before the layout; a wrong direction is a cheap fix.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Navigation patterns · Information architecture · Navigation transitions · Shared element transitions · What motion does in an interface

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close