What it is:
One singular App download from any App Store
Launchpad for Moniepoint to spin up a product/app in any market with the goal of
reducing the time to launch
reducing wastage
eliminate multiple apps being built
creating a template system for the overall look and feel of the MP app irrespective of market
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
A common brand and design system being used across all markets.
Design System: Kamona V3
Brand : TBD
Currently, this is just focused on MFB product
And the coming together of personal and business banking in Nigeria
and streamlining of Nigeria and UK
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
What it is not:
It is not a common point for product teams/business lines across countries. Each local entity will continue to own their business lines and products even if they offer the same general product. Eg. Onboarding Nigeria team will be different from Onboarding UK team OR Transfers Nigeria will be different from Transfers UK
It does not mean that a user can move around with their accounts globally. ie. I cannot carry my Nigeria accounts into UK or elsewhere if I move countries and continue to use them seamlessly
It should not be confused with a central point of excellence for a design function. We should treat them differently. i.e. Design principles, Suggested UX flows, templates etc. should be sitting outside of this.
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
It does not influence other products outside of the MFB
Teams and Specific Product Flows Global App Team will Manage:
Appstore Listing and Framework
Onboarding (user & device setup)
Initial Splash Animation ( if any)
Feature Slider + Country Selection
User Set up Flow
Mobile Number input
OTP Verification
Password/Passcode setup
Device related setup
Push notification setting
Device Biometrics setting
* Please note: anything beyond these in onboarding is a local flow (anything involving KYC/KYB) collection.
Login for Staff Users ( TBD)
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, IA for the top and bottom navigation of app
Widget Designs and logic for all parts of the Dashboard
*content within these will be defined by local teams
* there may be some additional widgets that are introduced and designed by local teamsDefined 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
TBD
A common Vocab:
Global Banking App: Launch pad 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 ( eg. MP Nigeria, MP UK etc.)
Local Flows: All flows and content of an app under a local entity
Global Design System: KamonaV3, as it applies to all markets
Centre of Excellence for Design: A standard and framework of principles, templates, and learning sessions to ensure the highest quality of design delivery.
Additional reference: Adrian's Going Global Doc
0 Comments