One singular app download from any app store

It is not a common point for product teams/business lines across countries. Each local entity will continue to own its business lines and products even if they offer the same general product/flow.

For example; the onboarding Nigeria team will be different from the onboarding UK team OR transfers Nigeria will be different from transfers UK.

Launchpad for Moniepoint to spin up a product/app in any market with the goal of:

• reducing the time to launch

• reducing wastage

• eliminating multiple apps being built

• creating a template system for the overall look and feel of the MP app irrespective of market

It does not mean that a user can move around with their accounts globally.

For example; I cannot carry my Nigeria accounts into UK or elsewhere if I move countries and continue to use them seamlessly

A way to own all user identity-related data and device-related data in a central place:

• what is user identity-related data: all login info (mobile number, password/passcode, country of residence)

• what is device-related data: things like push notification settings, biometrics settings

It should not be confused with a central point of excellence for a design function. We should treat them differently.

Design principles, suggested UX flows, templates, etc. should be sitting outside of this.

A common brand and design system being used across all markets.

• Design system: Kamona v3

• Brand : TBD

It should not be confused with unified/global view of one user’s multiple accounts. This is purely about a global app. Unified views will sit under/be a feature under this global app

Currently, this is just focused on the MFB product

• and the coming together of personal and business banking in Nigeria

• and streamlining of Nigeria and UK

It does not influence other products outside of MFB.

It is a huge undertaking to start with, but will not necessarily need high design effort after it has been rolled out

• unless a new global flow or widget needs to be created

• or to manage and change an existing flow/design

App store listing and framework

Onboarding (user & device setup)

Initial splash animation (if any)

Feature slider (carousel) + country selection

User set up flow:

• Mobile number input

• OTP verification

• Password / passcode setup

Device related setup:

• Push notification setting

• Device biometrics setting

Login for staff users (TBC)

Login and credentials

Login flow when a user signs in

Login credential management

Login credential recovery

Global dashboard shell

Overall layout, logic, design, and IA for the dashboard of the app

Overall layout, logic, design, and IA for the app’s top and bottom navigations

Widget designs and logic for all parts of the dashboard

Defined space for entry points and logic for all other parts of the app

Some widgets of the dashboard may be managed by the global team. For example:

• Alerts

• Notifications page (or aspects of it)

Specific aspects of user profile page and settings

TBC

Global banking app

Launchpad for MP banking app irrespective of the market, as defined above

Global app flows

All flows managed by global app team, as defined above

Local entities

Entities defined by markets (MFB NG, UK)

Local flows

All flows and content of an app under a local entity

Multi-brand design system

Kamona v3

Centre of excellence for design

A standard and framework of principles, templates, and learning sessions to ensure the highest quality of design delivery.