Springboard Navigation Version Print this Page
Navigation Pattern Set
Return to Top
The Springboard Navigation pattern represents separate functionality as icons and presents them to the user as a grid of visual options. The pattern addresses designs for the initial page of the application, known as the springboard, and an application header that returns the user to the springboard. Each set of functionality must be a concrete concept that can be represented by an icon. This pattern works better for native applications because it requires a deeper commitment to creating artwork optimized for specific screen sizes and platforms.
Pattern Set Decision Table
Return to Top
List Navigation
Springboard Navigation

The application contains a large amount of functionality that can be presented to the user as a grid of easily understood icons.



The application is optimized to show application data immediately upon entry.



The design needs to scale across a wide variety of device screen sizes and platforms.



Springboard Pattern Sample
Return to Top

Large icons that are clearly labeled are used to represent each category.

Springboard Example
Figure 1. Oracle Fusion Sales springboard
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Page Header Name of application A Sign Out button can be placed in the top-right corner.
Icons A minimum of six easily understood mobile icons A four-across layout can be used for devices that have a landscape orientation.
Input Field Input field and action (optional) Use for search or another key input action. Use only one input field on the springboard.
Personalization Animate and make icons editable upon touch-and-hold inline action NA

Once the user drills down from the springboard, a return-to-springboard icon appears on the top left of the screen. Use this icon only for the first drill-down level. When an additional drill down occurs, use a standard Back button.

Application Header
Return to Top
Navigation on detail pages
Figure 2. Detailed pages with navigation buttons
Required Screen Elements
Component Type Required Components Customizable or Extendable Components
Page Header (one-level down)
  • Page title that links back to the springboard
  • Return-to-Springboard icon
Page Header (two-plus levels down)
  • Page title that links back to the springboard
  • Back button
Key Considerations
Return to Top

This pattern works well when users must perform a wide variety of tasks in no particular order.

Interaction Examples
Return to Top
This flow shows how a user selects the Opportunities section and then drills into a specific opportunity to see details. To return to the navigation options from the opportunity details, the user selects the page title name.
Springboard Navigation Flow
Figure 3. Oracle Fusion Sales application navigation flow
On Device Examples
Return to Top
Here are two examples from Oracle Fusion Mobile Sales.
Springboard on iPhone
Figure 4. iPhone
Springboard on BlackBerry
Figure 5. Blackberry Bold
These examples are from Oracle Expenses and Human Capital Management (HCM) Person Gallery.
iPhone Expenses Application
Figure 6. Financials expenses
HCM Springboard
Figure 7. HCM person gallery
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights