# Placement Guidance: Where Each Component Goes and Why

> Placement guidance tells designers where a component sits on a screen and next to what, so users find it in the same spot every time.

**In short:** Placement guidance tells designers where a component sits on a screen and next to what, so users find it in the same spot every time.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/placement-guidance

## What you will learn

This lesson teaches placement guidance. It is the part of a design system that says where a component should go on a screen, and where it should sit next to other items. Teams use a design system as a shared reference, so that designers and builders agree on how things look and work. Placement is one of the topics that system covers.

- **Design system:** A shared set of parts, looks, and rules that a team uses to build products in a consistent way.
- **Component:** A reusable piece of a screen, such as a button, a dialog, or a banner.
- **Element:** Any single item on a screen, such as a label, an icon, or a line of text.
- **Layout:** The way items are arranged on a page or screen.
- **Default position:** The spot a component uses unless there is a good reason to move it.
- **Relative placement:** Where an item sits compared with other items, such as beside or above them.
- **Reading order:** The order in which people scan a screen. In left-to-right languages, this starts at the top left.
- **Convention:** A habit that people already expect, such as where a close button usually appears.
- **Anchor:** To attach a small item to a fixed point on a bigger item, such as one of its corners.
- **Exception:** A written case where the normal rule does not apply.

By the end of this lesson, you should be able to explain what a placement rule says, why it exists, how it treats neighbouring items, and what to do when space runs out. You will also follow one real dialog from start to finish.

## What does placement guidance answer?

Placement guidance answers three questions for each component. Where does it go by default? Where does it sit next to other things? What should a designer do when the best spot is already taken? A good guide answers all three in plain words, so no designer has to guess.

- **Default position:** The usual spot in a layout. For example, a team rule might say that the main action in a dialog sits at the bottom right.
- **Relative position:** How the item sits beside its neighbours, such as a secondary button placed next to a primary one.
- **Fallback:** The backup plan when the preferred spot is not free, such as a small screen or a crowded footer.

Each part needs its own clear rule. If a team writes only the default position, designers will still have to decide what happens on a phone, or when a second button appears. That is why good guidance covers all three.

## Why is a position chosen?

A placement rule should always come with a reason. When a rule has a reason, a reviewer can check it, and a designer knows how far they may bend it. Three reasons appear again and again.

- **Reading order:** People scan a screen in a set direction. One UX blog explains that primary buttons often sit on the right because readers finish their scan there, in left-to-right text.
- **User expectation:** People form a mental picture of where things live on a screen. When the same action appears in the same place, people find it faster.
- **Platform convention:** Each platform has habits that users already know. Several major systems, including Google's Material Design, keep button order predictable across their products.

> **Tip:** Write the reason beside every position rule, in one sentence. For example: Primary action sits bottom right because people finish a task there. A reason turns a rule into something a teammate can understand and apply.

## Default positions in practice

The default position is usually the first thing a placement guide states. It answers the question every designer asks: where do I put this? The examples below come from Material Design, a public design system from Google that documents its rules in detail.

### Dialog buttons

A dialog is a box that appears over the screen to ask for a decision. <cite index="4-3">Dialog containers appear above other screen elements and hold the dialog's headline, text, buttons.</cite> Material's guidance aligns the buttons to one edge, which keeps the action area easy to find.

For simple dialogs, the rule puts the affirmative button, meaning the one that confirms, to the right of the dismissive button, meaning the one that backs out. The same guidance limits how many actions a dialog should carry.

Material also shows examples of the wrong look. Its button pages compare a correct flat button with raised buttons that look too strong for a dialog, so the reader can see the difference rather than just read about it.

### Snackbars and short messages

A snackbar is a small, temporary message that reports what just happened. <cite index="22-14">Place a snackbar in front of the main content</cite>. On mobile, the message stretches across the bottom of the screen. <cite index="25-1">Although all snackbars will span across the bottom of the screen on mobile devices, they can be left or right aligned on desktop/tablet devices.</cite>

Notice that the position depends on the screen size. A corner placement, which some teams want for their short messages, is a team choice. If a team picks a corner, it should write down the screen sizes where that corner rule applies.

## How does relative placement work next to related items?

Relative placement describes how an item sits next to its partners. A button rarely stands alone. It sits with the other buttons in its group, with the field it fills in, or with the parent item it belongs to.

### Buttons side by side

When two buttons work as a pair, the guidance tells designers to keep them together. The arrangement also tells users which action matters most. <cite index="8-8">The arrangement of on-screen elements should clearly communicate that other buttons are less important.</cite>

Material pairs buttons by their level of emphasis. A text button can sit to the left of a filled button, and that is the pattern used when a dismissing action sits beside a main action. Pairing an outlined button with a filled button is also allowed.

### Labels and anchors: examples your team can write

Not every placement rule comes from a public source. Your own team writes rules for its own parts. These two are examples of the form such rules can take. They are not facts about any named product.

- **Label position:** Example rule: a label sits above its input field on every form. Reason: the reader sees the name first, then types the answer.
- **Badge anchor:** Example rule: a count badge is anchored to the top right corner of its icon. Reason: the corner stays visible, so the badge is easy to spot at any icon size.

## What if the preferred spot is taken?

Sometimes the default spot is not free. A good guide tells the designer what to do next. The steps below follow the fallback pattern shown in the Material examples.

1. **Keep the default first:** Start with the rule. Move the item only when a real problem stops it from fitting.
2. **Stack only when side-by-side does not fit:** Buttons can stack when the text is long, but stacking takes more room.
3. **Move the item along the same edge:** Snackbars are equal in elevation to a floating action button.
4. **Do not hide what the user needs:** Material advises against letting a snackbar fully cover an element that has focus, because the user could lose their place.
5. **Write the exception down:** Record the case, the screen, and the reason. The next designer then sees a pattern, not a surprise.

A snackbar also shows why some fallbacks are not allowed. The safe fallback is to move the snackbar up.

## Worked example: a Delete project dialog

Here is how a designer uses the Material dialog guidance for a 'Delete project?' dialog. The steps follow the way a designer would reason through the placement, one choice at a time.

1. **Identify the component:** The dialog is a box above the screen, with a headline, a short message, and buttons. It asks the user to confirm one choice.
2. **Count the actions:** There are two actions: Delete, which confirms, and Cancel, which backs out. Two is the limit the guidance sets for a dialog.
3. **Place the buttons on the trailing edge:** In a left-to-right layout, the trailing edge is the right side. The buttons sit at the bottom right of the dialog.
4. **Put the confirming action on the right:** Delete goes on the right, as the affirmative action. Cancel goes to its left, as the dismissing action. A designer does not need to decide this again.
5. **Check the destructive case:** Delete removes data, so the designer checks whether the system allows any exception. The designer follows the system's own default unless the team has written an exception.

> **Tip:** In the design file, write one line next to the dialog: Delete is on the right, the default for confirming actions; Cancel is on the left. The next designer can then copy the pattern without asking.

## What are the exceptions for right-to-left languages and smaller screens?

Every placement rule needs its exceptions written down. Two cases come up often. The first is language direction. Material's button guidance is written for left-to-right text, and it says to align text buttons to the right edge in that case. In a right-to-left language, the trailing edge is the left side, so the guide must say how the layout flips.

- **Right-to-left languages:** Arabic and Hebrew read from right to left. The layout mirrors, so the trailing edge moves to the left. Check the system's written rule for these languages instead of guessing.
- **Smaller screens:** Buttons and containers change as screens change. The size and placement of buttons can change as parent containers adapt for larger screens. Mobile may need stacked actions or a full-width bar.
- **Desktop and tablet:** Some components move on larger screens. For example, snackbars can be aligned left or right on a desktop or tablet instead of spanning the bottom edge.

## How do you write placement rules people can use?

A placement guide only helps if people can read it quickly and apply it. The guidance from the plan gives three habits for this: pair each rule with a do and a don't, state the exceptions, and keep the pattern the same everywhere.

- **Pair each rule with a do and a don't:** Show a correct picture and a wrong picture side by side. Material's button pages do this, with a correct example and a wrong one for the same component.
- **State the exceptions:** Name the cases where the rule bends, such as language direction, small screens, or a floating button in the way. A rule with no exceptions often gets broken in silence.
- **Keep it consistent:** Use the same placement for the same job on every screen. One UX blog describes consistency as the same placement across similar screens, which helps users learn one pattern and stop searching.

> **Tip:** Test a placement rule by asking a teammate to find an action on a new screen without help. If they look in the wrong place, the rule is not clear enough, or it is not being used consistently.

## Check yourself

Try these two short scenarios. Each one needs the ideas from this lesson to answer. Choose the best option, then read the reason.

**Quick check:** You are adding a Save button and a Cancel button to a new form. Your product's design system says the primary action goes at the bottom right. A teammate's mockup puts Save on the left. What should you do?

A. Keep the mockup, because a form is not a dialog, so the placement rule does not apply.
B. Move Save to the bottom right, put Cancel to its left, and cite the system rule and the reading-order reason in your review.
C. Place both buttons at the top of the form, so neither one sits on the bottom edge.
D. Ask the teammate to pick a side, because button placement is a matter of taste.

**Answer:** B. The system's default is the reason to act. Save is the primary action, so it goes at the bottom right, where readers finish their scan. Cancel sits to its left. Citing the rule and the reason lets the teammate see why, and it keeps this form the same as every other form in the product.

**Quick check:** A mobile screen has a floating action button at the bottom right. Your team's rule says a snackbar appears at the bottom of the screen. Where should the snackbar go so it does not cover the button?

A. Directly on top of the floating button, so the message stays near the action.
B. Above the floating button, so the two do not overlap.
C. Behind the floating button, so the button stays in front.
D. At the top of the screen, where there is no button at all.

**Answer:** B. This is a fallback case. The default is the bottom of the screen, and the nearby button is in the way. Material's guidance places the snackbar above the floating button, and it says not to overlap or hide the button. Moving to the top would break the default for no real reason.

## Key takeaways

- **Rules say where:** A placement rule states the default position of a component, how it sits beside its partners, and what to do when the spot is taken.
- **Reasons make rules stick:** Reading order, user expectation, and platform convention explain why a position was chosen, and they help teams bend a rule safely.
- **Exceptions are part of the rule:** Write down language direction, small screens, and blocking elements, along with a do and a don't for each rule.

## Sources

- [Material Design 3: Dialogs guidelines](https://m3.material.io/components/dialogs/guidelines)
- [Material Design 3: Snackbar guidelines](https://m3.material.io/components/snackbar/guidelines)
- [Material Design 3: All buttons](https://m3.material.io/components/all-buttons)
- [Material Design (v1): Buttons](https://m1.material.io/components/buttons.html)
- [Material Design: Buttons usage and placement](https://m2.material.io/develop/ios/components/buttons)
- [Material Design (v1): Snackbars and toasts](https://m1.material.io/components/snackbars-toasts.html)
- [Material Design snackbar notes (Ocha, blog)](https://note.com/ocha150432/n/nfe131fbec034?hl=en)
- [Material Design snackbar placement (daemonite docs mirror)](https://daemonite.github.io/material/docs/4.1/material/snackbars/)
- [Material UI Snackbar component docs](https://mui.com/material-ui/react-snackbar/)
- [Dialog button placement notes (Yukio, blog)](https://note.com/aganir_seshisa/n/n44d8ab108cc8?hl=en)
- [UX Button Placement: Best Practices (Design Monks, blog)](https://www.designmonks.co/blog/ux-button-placement)
- [Design system (Wikipedia)](https://en.wikipedia.org/wiki/Design_system)
