Tithi Mondal

Article7 min readUpdated

Modal Design: When to Use Pop-ups, Dialogs and Bottom Sheets

Modal design explained: when to use a pop-up, a confirmation dialog or a bottom sheet in an app, with clear do and do-not examples for each.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Modal Design: When to Use Pop-ups, Dialogs and Bottom Sheets: cover illustration

A user opens a bus booking app. Before she sees a single bus, a pop-up asks her to rate the app. She closes it. A second pop-up offers a discount and asks for notifications. She closes that. A third asks her to allow location. She has not yet done anything she came to do, and she is already tired.

Pop-ups are easy to add and costly to the user. This article explains modal design: how to decide when a modal is right, and how to build one that helps. A modal is a layer that appears over the page and blocks it until the user responds.

What is a modal, and how is it different from a pop-up or a bottom sheet?

A modal is any layer that sits above the page and takes the user's focus. "Pop-up" is the everyday word for it. A dialog and a bottom sheet are two common types of modal.

TypeWhat it looks likeBest for
Dialog (alert)A small centred box with a short message and 1 or 2 buttonsSerious decisions, confirmations
Full modalA large panel or full screen with its own header and close buttonA short task that is separate from the page, such as adding an address
Bottom sheetA panel that rises from the bottom of the screenChoices, filters, share options, short forms on mobile
Toast or bannerA small message that does not block the pageLight confirmations and notices

The last row is not a modal, and that is the point. Many things that appear as pop-ups should be a banner or a toast, because they do not need the user's full attention. See button states and feedback design for toast messages.

When should I use a pop-up?

Use a pop-up only when the user must make a decision or provide information before the app can continue, or when an action cannot be undone. If the content can wait or sit on the page, do not use a pop-up.

Good reasons for a modal:

  • Confirming a permanent action, such as deleting an account.
  • Asking for a permission at the moment it is needed, with an explanation first.
  • Collecting one small piece of information the flow cannot continue without, such as a delivery pincode.
  • Showing a serious problem, such as a payment that failed.

Poor reasons:

  • Promotions and offers on every app open.
  • Asking for a rating before the user has used the app.
  • Announcing a new feature.
  • Showing information that could be a normal page or section.

A simple test: if the user ignores this message, does something bad happen? If not, it should not block the screen. The same rule applies to push messages, as I explain in notification UX for push, SMS and WhatsApp.

How do I design a good confirmation dialog?

A good confirmation dialog states the action, states the result, and uses buttons that repeat the action. The user should be able to understand it without reading the whole text.

Compare these two:

  • Do not: Title "Are you sure?". Buttons "Yes" and "No". The user has to guess what Yes means.
  • Do: Title "Delete this address?". Text "This address will be removed from your account." Buttons "Delete address" and "Keep it".

Rules I follow:

  1. Name the object in the title: "Cancel booking?", not "Warning".
  2. Put the consequence in one short sentence. Add the money or data detail when it matters: "You will get a refund of ₹320 in 3 to 5 days."
  3. Use action words on both buttons. Avoid "OK", "Yes" and "No".
  4. Make the dangerous button look different, such as a red text or fill, and keep it away from the easiest tap position.
  5. Keep the safe option easy to choose.

Do not use a confirmation for every small action. If users see "Are you sure?" ten times a day, they stop reading. For small actions, such as removing an item from a cart, allow the action and offer "Undo" instead. See cart and wishlist screen design.

When is a bottom sheet better than a dialog?

A bottom sheet is better when the user needs to pick from options or fill a few fields, because the controls are within thumb reach. A bottom sheet is a panel that slides up from the bottom edge and covers part of the screen.

Good bottom sheet uses:

  • Sort and filter choices on a product list.
  • A list of saved addresses to choose from.
  • Share options.
  • A date or time slot picker in a booking app.
  • Payment method selection before checkout.

Why it works on a phone: the thumb already rests near the bottom, the panel feels connected to the screen behind it, and the user can dismiss it by swiping down. I cover reach in thumb zone design.

Design notes:

  • Show a small handle at the top so people know they can drag it.
  • Let the sheet be dismissed by swiping down, by tapping outside, and by a visible close or "Done" button.
  • Keep the primary button inside the sheet, near the bottom, and above the keyboard if there are fields.
  • Limit the height. A sheet that covers 90 percent of the screen is really a full page, so build it as a page.

I explore filter patterns in search and filter UX design.

What goes wrong with modals?

Most modal problems come from blocking users without a way out, or from stacking one modal on another. These are the failures I check in every audit.

  • No obvious close. A small "x" in the corner, 16 points wide, is hard to tap. Make the close target at least 44 points, and also allow tapping outside the modal where it is safe.
  • Modal on modal. A dialog that opens from a bottom sheet that opened from a page is confusing. Replace the inner layer with a new screen.
  • Long content in a small box. Scrolling inside a scrolling page frustrates users. Move long content to its own screen.
  • Modal on app open. Never put a promotion between the user and the first screen.
  • Lost keyboard. On a form modal, the keyboard covers the Submit button. Keep the button visible.
  • The back button does nothing. On Android, the system back button should close the modal first.

Also check the first-time experience, because permission pop-ups often appear there. Explain why you need location or notification access before the system asks. See app onboarding UX best practices.

How do I make a modal accessible?

An accessible modal moves focus into the modal when it opens, keeps focus inside, and returns focus to the button that opened it when closed. Screen reader users must hear that a dialog has opened and be able to close it.

Checklist:

  1. The modal has a clear title that a screen reader reads first.
  2. Focus moves to the title or the first control when the modal opens.
  3. The background is not reachable while the modal is open.
  4. The Escape key and the back gesture close it, where they exist.
  5. The close button has a text label for assistive tools, not only an icon.
  6. Text and buttons pass the contrast guidelines. See colour contrast in UI.

More on this in accessibility in app and web design.

Is this the same on websites?

The principles are the same, but the details differ on a website. A website pop-up can hurt search ranking and annoy readers if it covers content right after they arrive. Mobile browsers also make it hard to find a small close button.

For websites, use a pop-up only for a clear need, such as a cookie notice, a login or a short enquiry form that the visitor asked to open. Avoid pop-ups that appear within the first few seconds. A banner at the top or an inline section is usually kinder. See landing page design that converts and mobile-first website design.

When I plan screens in my mobile app design work, I list every modal in the flow, ask what happens if it is removed, and often turn half of them into inline messages. If you want a second pair of eyes on the pop-ups in your product, you can get in touch.

Frequently asked questions

What is the difference between a modal and a dialog?

A modal is any layer that blocks the page until the user responds. A dialog is a small, focused type of modal, usually a short message with one or two buttons.

Are pop-ups bad for UX?

Not always. Pop-ups that ask for a needed decision are fine. Pop-ups that show promotions or appear before the user has done anything are harmful.

Should a bottom sheet have a close button?

Yes. Support swiping down and tapping outside, and also add a visible close or Done button for users who do not discover the gestures.

How many modals should an app flow have?

As few as possible. If a modal is not needed to make a decision or prevent a serious mistake, use an inline message or a toast instead.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.