Enables user orientation and seamless movement across the app’s layers, by displaying essential context and navigation capabilities
A three layer approach
There are three types of headers – one for the ‘home’ layer, one for layer 1 pages and the third for layers 2, 3 and 4. Whilst ‘home’ and layer 1 look similar at a glance the height differences and labels help the user distinguish which page they are on as they navigate to where they need to be. The layer 2 header is even more contextual, with specific titling and the ability to access help, contextually.
Home overview
Home has a specifically designed header which is different to the Layer 1 pages. This helps differentiate it as the personalised layer, and brings OVO personality and branding to the page. To complement the header and the new home page, we are working on new scroll animations.
In-situ: Pay monthly
- Access to account and/or chat (AVA)
- Header composition asset incorporates balance card
In-situ: PAYG
- Ability to stack multiple cards – header background extends to accommodate
- If more than two cards, maximum height of green background aligns with the £ on the second card
Home specification
Layer 1 overview
Layer 1 headers are shorter than the home ones, and the heading should match the name of the page (if it says ‘bills’ in the global navigation, the heading should say ‘bills,’ too).
- Name of the layer – should match the global navigation
- Access to account and/or chat (AVA
- Drop shadow ON – present on ALL layer 1 pages – content scrolls behind
- Layer name and buttons hide on scroll and re-reveal when scroll is reversed (layer is named/selected in global navigation to aid way finding
- Drop shadow ON – present on ALL layer 1 pages – content scrolls behind
Layer 1 specification
Layer 2, 3, 4 overview
As a consistent signifier of focused information and journeys, the header designed for layer 2 should also be used for layer 3 (and layer 4, if an exceptional circumstance).
Layer 2 headers:
- Drop shadows are always ON
- Have Android and iOS variants
- Heading should be derived from origin card
- Heading should be short and concise
- Contextual help button can be turned on
- Stepped variants can be used within journeys to remain at the same layer
Note: header extensions should not be used on layer 3 or 4.
- iOS variant
- Drop shadow ON – present on ALL layer 2, 3, 4 pages – content scrolls behind
- Android variant
- Access to contextual help wherever necessary
Layer 2, 3, 4 specification
Character limits
After 30 characters truncate.
The page heading should reference the origin card and remain consistent throughout onwards journey.
We strongly recommend keeping headings short.
In places where titles are linked to an article for example, this may not be possible, but consider simplifying headings wherever possible.
Header extensions
A header extension has been created for use at layer 2. The design is specifically focused on a PAYG use case, currently, with it being the final state of the balance card when transferring from home/layer 1 to layer 2.
For now, the use cases are standalone.