Skip Navigation

Introduction to Messaging

Guiding Principles

Our approach to messaging is in keeping with the broader guiding principles of Sabre Spark. Providing real-time feedback to users is an important part of designing an application that keeps users informed, gives users confidence and drives them forward in achieving their goals.

Determining Which Message to Use:

Form Messages

Form messages are validation and informational messages appearing in the context of forms and Tabular data.

Toast Notifications

Toast messages are messages that disappear automatically after a defined amount of time.

Badge Indicators

Badges are used to call attention to important status, labels and other indicators warranting attention.

Remains on screen?
Form Message: Yes
Toast Notifications: No
Badge Indicators: Yes
User’s area of focus

Form Message: Primary

Toast Notifications: Primary or background

Badge Indicators: Background is most common

When to use
Form Message:
  • All form validation, including validation messages displayed within:
    – The input field
    – The panel or screen
    – Modals
  • System errors
  • Informational content that benefits from additional visual prominence
  • In Tabular data sets
Toast Notifications:
  • Messages that do not require user action.
  • Non-critical messages intended to interrupt the user from a task with an important update (to make the user aware, even though no action is needed)
  • Information that the user is unlikely to want to remain on the page
Badge Indicators:
  • Indicating a status that can change based on system or user actions
  • Indicating the presence or availability of something (wifi, gym, meal)
  • Indicating a count or tally
When not to use
Toast Notifications:
  • Messages that require the user to take action before advancing
  • Messages that provide a primary link or access point
  • Any other message that is best displayed persistently
Badge Indicators:
  • Indicators or messages requiring the user to take action. These can appear as badges but should be paired with a validation-type message to better direct the user.

Primary Types of Messages

Form Messages
Toast Notifications
Badge Indicators

Putting It All Together

The example below shows variations of Spark messaging (in-context), which demonstrates the following:

  • Spark Messaging Types
  • When / Where each should be used.

(Click image to open full resolution image in new tab)

Responsive Grid - (Click image to open full resolution image in new tab)

Spark Messaging Guide Assets

Use the Messaging Guide Assets as templates to help communicate proper messaging types and locations within a design. The PSD and Sketch files can be customized to fit your needs.

  • PSD and Sketch assets for the design above are available for download on the Designer Resources page.
  • Messaging-themed example of how designers and developers can utilize Figma’s comment feature as a collaboration and communication tool.