Case file · Banking
Neobiz Mobile (Egypt)
Thesis
The Egypt web journey solved a regulatory problem: how far can account opening go without a verifiable digital identity. This case file solves the same journey again for a different reality: one hand, interrupted sessions, and a camera instead of a scanner.
The rule I held throughout: nothing about the regulation changes, so anything that changes must be justified by the environment. The documents required, the declarations, the partner rules, the meeting at the end: identical to the web. What changed is how a person moves through them on a phone they pick up and put down all day.
I am in an unusual position for this product: I designed the UAE mobile journey, and I designed the Egypt web journey. This app sits at the intersection: Egypt's regulatory reality, delivered with mobile patterns proven in the UAE. I am the sole designer on it.
What it is
Two systems in one native app:
1 · Mobile Onboarding: the full acquisition journey, restructured as a task dashboard rather than a linear stepper.
2 · Mobile Customer Portal: the waiting relationship, with push notifications joining email and SMS.
Sibling case file: [Egypt Acquisition (Web)]: the six-system architecture this app plugs into. The Application Workflow, fulfilment and AOF described there serve this app unchanged.
Status, honestly
Designed in full: every screen, every case path, both languages. Validated internally with stakeholders. Not developed yet while it’s a standalone major project.
So this case file makes design claims only. Any number you may want (completion time, conversion, drop-off) belongs to the web case file. When this ships, its results table gets written; not before.
Why it matters anyway
This design became a reference. Teams that came after built on it: partner-facing versions of the web journey, mobile work with partners, and white-label variants for other companies. The patterns documented here (the dashboard structure, the case-matrix approach to ownership, the camera capture model) outlived the single product they were made for.
Three ways in
- Show me a platform decision.The stepper became a dashboard: same enforced sequence, presented as accumulating achievement instead of remaining distance. And it replaced the review page entirely. Onboarding → Decision.
- Show me complexity handled.One dropdown on the web became a case matrix on mobile: structure × nationality × residency × role × signing authority, each combination a short path of one-question screens. Onboarding → The case matrix.
- Show me a lesson carried forward.The multi-page commercial register broke on the web after launch. On mobile, the capture tool itself solves it: sequential scanning merged into one file, before the mistake can happen. Onboarding → Capture.
- Chapter 01OnboardingCarry the same regulated journey (same documents, same declarations, same partner rules) through a device that gets picked up in a car, on a break, walking down a street, and put away again mid-sentence.
- Chapter 02Customer PortalKeep the waiting customer informed through the device that is actually with them. And make sure an interrupted application is remembered by the phone, not by the customer.
Sibling case files
the six-system architecture this app plugs into. The Application Workflow, fulfilment and AOF described there serve this app unchanged.