App overview

Layer 1

A re-imagined, focused view that organises key information, elevates buried actions and makes critical statuses timely and relevant.

A focused view

Layer 1 pages are the first focused view users access when they move directly from the Home page. These pages offer a reimagined, clear, concise and organised view of key account areas, such as bills, usage, and help. 


The primary objective is to deliver timely and relevant information,
allowing users to immediately grasp their status and progress without being overwhelmed by detail. By making payment and bill status explicitly visible, and by providing quick actions, we ensure the user can resolve their most pressing issues in a single tap.

Intro graphic

 

How do I access Layer 1 pages?

Layer 1 pages are the main structural entry points for the app's key features. They must be one click away from Home as these are the key actions users need to take.

Users access these pages directly from the global navigation bar located at the bottom of the screen (present on home and layer 1 pages). This ensures that essential pages are always visible and instantly accessible, aligning with our goal of making key actions never more than 3 taps away.

Accessing layer 1 pages
  1. Access to account and chat
  2. Key focused
information
  3. Layer 1 pages
  4. Quick actions
  5. Action lists

 

Accessing layer 1 pages from nav

Rules

Do
  • Be clear and concise Offer a focused view of the topic (e.g., bills, usage, help). 
Do not introduce unnecessary detail that belongs in Layer 2 or 3.
  • Elevate actions Bring previously buried actions (like viewing the latest bill or submitting a reading) directly to the surface with clear CTAs.
  • Be explicit
Make key actions explicitly visible at the top of the relevant page. 
Users should know their standing instantly.
Don't
  • Unauthorised expansion
Do not proceed with handing over or implementing new Layer 1 pages without formal approval. These critical additions require oversight 
and sign off from the App team to ensure correct hierarchy and integration
– the app alignment session on Mondays is the best way to do this
  • Avoid information overload Layer 1 is not a dashboard. Do not try to show every piece of data and information, only show what is timely and relevant
  • Cards should hero simple, glanceable information that drills down into more granular detail when tapped (opens a layer 2 page)
  • Ignore relevance Do not display quick actions that are not relevant to the current page topic.
  • Forget hierarchy Don’t introduce multiple complex onward points. The primary function
of Layer 1 is to move users logically into the next layer of detail (Layer 2).

 

Interactions

  1. Vertical page scroll
    Header collapses on scroll
  2. Layer 1 header
  3. Opens account
(Layer 2)
  4. Opens chat
(Layer 2)
  5. Chart data card (large)
  6. Quick actions
    Horizontal scroll
  7. Icon data card
  8. Chart data card
  9. Tapping opens respective Layer 2 pages
  10. Progress bar data card
  11. Image card
  12. Navigates to selected
Layer 1 page
Interactions

 

Page content

Here is an overview of the types of tiles and content which can be displayed
on a home layer.

Please reference tile documentation and guidance for specific information
around designing and content rules for cards.

 

Header

Main purpose

  • Wayfinding

  • Entry points to account/chat

  • Present alerts

Key rules

  • No edits to be made
  • Must have a drop shadow

Interactions

  • Not tappable
(aside from entry to account and chat)

  • Entry into account/chat

Component variants

  • Layer 1 header
Header example

Quick actions

Main purpose

  • Provide quick entry into relevant journeys

  • Prioritisation of required actions

Key rules

  • Minimal words + image/icon
  • Maximum of 3 quick actions
  • No CTAs to be used

Interactions

  • Tappable actions
  • Scrollable actions

Component variants
More detailed information
to be found within card
documentation

  • Standard quick actions
  • Urgent quick actions

 

Quick actions example

Cards

Main purpose

  • Communicate glanceable information

  • Entry point to more granular detail

Key rules

  • Must have a title
  • Subtitle must relate to timeframe
  • No CTAs to be used within card

Interactions

  • Tappable variants
  • Non-tappable variants

Component variants
More detailed information
to be found within card
documentation

  • Text cards
  • Data cards
  • Image cards
  • Offer cards
  • Disruptive cards
  • Tappable cards
  • No non-tappable cards

 

Cards example

Main purpose

  • Swipe through a set of
information

  • Manage page height

Key rules

  • Must have a title
  • Minimal copy
  • No CTAs to be used within card

Interactions

  • Tappable cards
  • Scrollable cards

Component variants

  • Tappable cards
  • Pagination must be visible
  • No non-tappable cards

 

 

Other page content

Main purpose

  • Enhance user efficiency by providing structured context specific functions,
and flexible data

Key rules

  • Action list
  • Date filter
  • Tabs

Interactions

  • Tappable variants
  • Non-tappable variants

Component variants

  • Standard action list
  • Urgent quick actions

 

Other content example