Nebulla · Fintech · 2022
Dashr
One app for the money jobs people juggle across many: bills, transfers, cards, group savings, budgets and loans. I was UX design lead on a team at Nebulla in 2022.

- Client
- Nebulla, my studio
- My Role
- UX design lead
- Timeline
- 5 months, 2022
- Team
- Eight product designers, three project managers, a content manager and developers
- Platform
- Mobile app, plus a landing page
- Read Time
- 4 min
Results at a glance
- 120+screens designed, with a dark mode
- 50%of test users loved the look and wanted to download it at launch
- 6“how might we” questions the team designed against
01 · Problem
People install one app to save, another to budget, another for loans and another to pay bills. Most finance apps solve one money problem, so users churn and phones fill up.
02 · Insight
Surveys, interviews and field studies said the same thing: people want one product that simplifies their money, and that is easy enough for everyone, including older users.
03 · What I did
As UX design lead on a team of eight designers, I made sure every step of the process answered users’ pain points and kept user and business goals in balance, from research and journey maps to flows, 120+ screens and testing.
04 · Result
Half the test users loved the look and wanted to download it at launch. Testing also showed where it fell short: QR and URL payments confused people, and older users needed more iterations.
01 — The problem
Too many apps for one wallet.
Finance apps were downloaded 4.6 billion times in 2020, up 15% year on year, yet people still installed a different app for each money job: saving, budgeting, loans, payments and investments.
So many platforms created a paradox of choice. Most solve one problem, few bring them together, and users churn between them. The question became simple: why not one app that does it all?
02 — My role
Not a solo project.
Dashr was a team effort: eight product designers, three project managers, a content manager, developers and stakeholders, brainstorming together throughout.
As UX design lead, I wasn’t the only designer, but I took a key role in making sure every part of the design process accounted for users’ pain points, and in keeping user goals and business goals in balance.
03 — Research
Built for 18 to 35.
Research started with stakeholders and product owners, the first source of the idea, then moved to the people who would use it:
- Offline field studies, online interviews, surveys, and a competitive analysis of the fintech products already out there.
- A core audience of 18 to 35, who our research put at 71% of online banking requests.
- Four personas: a college student, a saleswoman, a remote worker and a businessman. One, Jasmine, is a 20-year-old hairstylist studying psychology at UNILAG who spends a lot on data and shopping, and had tried many utility apps without finding one easy enough.
- Journey maps for buying airtime and data, paying, and budgeting, tracking how each step felt, down to where a user got confused choosing a type of budget.
04 — How might we
Six questions to design against.
The research became six questions the whole team designed against. How might we design a product that:
- solves all the day-to-day financial challenges of a user?
- makes users feel safe and secure carrying out online transactions?
- helps users invest in local and global stocks and bonds?
- helps users transfer and receive funds across borders?
- has a better interface for financial transactions, and is easy to use?
- helps users choose the best savings plan for themselves?
05 — First screens
A quick start, then everything at a glance.
Onboarding walks a visitor through what Dashr does in a few swift screens. Then the home screen leads with the account balance, set on a moving mesh gradient, and quick links to send and receive money, save, borrow, swap and invest.
Below sit recent transactions, and an illustrated empty state for a new account that has none yet.
06 — Bills and cards
Bills and cards in a few taps.
Utilities gathers airtime and data, electricity, cable and transport bills in one list, each paid through the same short flow: choose a network or provider, an account and a recipient, then pay.
Cards were the most interesting feature: new at the time, brainstormed, validated and added to the MVP. Users request a virtual or physical card, top it up, and freeze or unfreeze it in a tap.
07 — Budgets
Budgets that don’t start from a blank page.
Creating a budget from scratch is stressful, especially for the older users Dashr also had to serve. So instead of an empty form, Dashr starts from editable budget templates: utilities, transport, shopping, travel and groceries, ready to adjust, with as many budgets as a user needs.
08 — Save and pay
Save together, borrow, pay by QR.
The rest of the money jobs users told us they juggled:
- Thrifts and group savings: friends pick a sum and contribute at their own pace, and one member is credited each week or month until the thrift ends.
- Savings goals, and investing in bonds, real estate and stocks.
- Short-term loans up to ₦500,000 with no collateral, where paying on time raises the limit.
- QR code and URL payments: generate a code or link to get paid, or scan someone else’s to pay them.
- Dashr to Dashr: find any Dashr user by their ID and send them money.
09 — The whole product
120+ screens, a dark mode and a landing page.
Beyond the core flows, the team designed more than 120 screens, a full dark mode iteration, and the landing page that introduces Dashr: Bank Like Royalty.
10 — Results
What testing showed.
From testing the prototypes before launch:
| Test users who loved the look and wanted to download it | 50% |
|---|---|
| Adult users who found it hard to navigate at first | 14% |
Users strongly preferred one app for everything. Testing also showed what to fix: QR code and URL payments confused people, early navigation issues caused drop-offs, and older users needed extra iterations before it felt seamless.
To judge future iterations, I’d track drop-offs when people try to get a loan or save (regular, emergency and thrift savings), whether they get lost using QR and URL payments, and drop-offs when creating a physical or virtual card.













