Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

NTF-003 Published · Updated

Floating Card Notification UI Design

A floating card UI that shows a small card with a photo and a short text at the bottom right of the screen.

FigmaThis part is included in our free, editable Figma file: 235 website UI patterns across 32 parts, 2 designs each Open in Figma Community ↗ (opens in a new tab)

Wireframe (desktop) | Floating card notification

Floating card notification UI design (desktop wireframe)

Wireframe (mobile) | Floating card notification

Floating card notification UI design (mobile wireframe)

What changes on mobile

  1. The card spans the full width: Pushed to the right in a narrow width, the title would wrap into hard-to-read fragments.
  2. A smaller photo: Keeps the card short so it hides less of the content.

Before you choose this pattern | Floating card notification

Good fit

  • Notices that a photo helps sell: seminars, fairs, new services
  • A one-line bar cannot convey the appeal
  • You want to make a quiet suggestion to readers who have read on, without covering the content

Poor fit

  • Everyone must be told, such as a temporary closure or an outage (<a href="/patterns/en/announce-priority/">priority announcement bar</a>)
  • The bottom right already holds a chat button or a sticky CTA (<a href="/patterns/en/notify-drawer/">drawer tab notification</a>)

Why this wireframe works | Floating card notification

A photo and a short text catch the eye better than a bar

A photo, title, date and link are gathered in a small card. The feel of an event or fair, which a one-line bar struggles to convey, comes across at a glance.

Shown late, and only to readers who have read on

It is not shown as soon as the page opens, but once the reader has got some way into the content. Something floating up right after opening gets in the way of finding what they came to read.

Does not cover the content, and stays away once closed

The card is small and at the edge of the screen, so the content stays readable. It can be removed with the close button; the closed state is remembered and the same notice is not shown again.

Its own place among the floating elements

It stacks above elements already at the bottom right, such as a chat button, so nothing overlaps.

Common mistakes | Floating card notification

Shown the moment the page opens

When the card floats up right after opening, readers look for the close button before the content. Show it after some scrolling or after a set time.

A card so large it hides the content

When the card covers much of the screen, the content cannot be read until it is closed. On mobile especially, keep it to a small part of the bottom of the screen.

Comes back on the next page after closing

A closed notice that keeps returning feels like nagging. Remember the closed state and do not show the same notice again.

Overlapping the chat button or sticky CTA

Overlapping elements at the bottom right are all hard to press. List every floating element at the screen edge and stagger their heights.

A floating notice that steals focus

A floating notice should not take focus when it appears, and its visible position and HTML reading order should match. Make the close button and detail link reachable by keyboard, and return focus to a sensible place when it closes.

FAQ | Floating card notification

When should the floating card appear?

Not right after the page opens; once the reader has scrolled some way in, or after a set time, is the guide. The notice then arrives when the reader has shown interest in the content.

How is this different from a pop-up?

Unlike a pop-up that covers the whole screen and blocks interaction, the card is small and at the edge, and the content stays readable. The page can be read on without closing it.

Can it be shown on mobile too?

Yes, kept to a small part of the bottom of the screen with an easy-to-press close button. If it would cover much of the screen, not showing it on mobile is a reasonable choice.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published