Mamo, iOS and Android, 2025–2026

Mamo Business app

The app was mostly web views. Every screen meant loading the web dashboard inside the app and logging the merchant in automatically while it did.

We moved four flows to native: payments list, create payment link, Mamo Card, and expense transactions. I designed them for the phone. Mamo Card went native first, in May 2025, because Apple Pay needed it. Expense transactions followed in April 2026, then the payments list in July and create payment link in August.

4
flows moved from web view to native
Dec 2025
Apple Pay launched on the native card flows
+21%
successful Apple Pay card spend, June to July 2026
Team
Mujtaba M (me)Product DesignerJoharah AlomairHead of DesignAsma AlyamaniChief Product OfficerAlex StolarSenior Flutter Developer
The four flows in one minute: creating a payment link, the payments list, adding Mamo Card to Apple Wallet, and closing out an expense. Rebuilt from my Figma designs.

The challenge

A web view has to load a lot of assets just to show you one screen, and it logs you in to the web while it does. For a screen without much on it, that wait isn’t worth it. You’d have been faster opening the mobile dashboard.

It was slow, clunky and unpredictable. Bugs came from both sides, the app and the web dashboard, and it was hard to tell which. Merchants are on the go, and that’s when you want things done quickly. Waiting on a web view to create a payment link or issue a card kills your momentum.

How I approached it

01

Payments list and disputes

You glance at this list on the go. You want the amount, the date and who paid, right away, and whether anything went wrong. So statuses are words in a badge, not vague icons, and payments are grouped by date so a long list stays easy to scan.

The hardest call was failed payments. I wanted to show the reason right in the list, but it got crowded fast. So the reason lives in the payment details, and the row just says it failed.

Disputes got their own tab. A business can have hundreds of payments and a couple of disputes. Behind a filter, those disputes get buried, and a missed dispute costs the merchant money, and us too. Disputes also have their own data, so they got their own filters and status words. In the designs, an orange dot flags a dispute that needs a response, instead of a count.

Web viewNative
Drag to compare: the old web view crammed into the app, and the native rebuild. Grouped by date, legible rows, and status as a plain-language badge. — native
Drag to compare: the old web view crammed into the app, and the native rebuild. Grouped by date, legible rows, and status as a plain-language badge.
Disputes in their own list: what is due today and soon up top, filters, and a badge on each dispute that needs a response. The orange dot on the Payments tab is how it surfaces in the designs.
Disputes in their own list: what is due today and soon up top, filters, and a badge on each dispute that needs a response. The orange dot on the Payments tab is how it surfaces in the designs.
02

Create payment link

I designed three full flows: one step, two steps and three steps. We pressure-tested them in a working session the day before the team review, then took all three to the cross-functional group to decide.

One step won. This is for people on the go, with a customer waiting on WhatsApp for a simple payment link. You don’t want extra views or taps. The work was fitting the information on one step without overwhelming it.

The success animation was my first go at Figma Motion. A checkmark on its own does very little, especially if you create links all day. What matters is what happens next: you want to share it. So the checkmark turns into the QR code, and a customer standing in front of you can scan it right away. Or you send the link over WhatsApp or Messenger. Things appear one by one, not all in one frame, and it doesn’t take long.

The success sheet: a checkmark, then the QR code, then the link and share actions. The first thing I built in Figma Motion (opens in new tab).
The three flows I designed, top to bottom: one step, two steps and three steps.
The three flows I designed, top to bottom: one step, two steps and three steps.
03

Mamo Card: native cards and Apple Pay

Before this project, Mamo Card had no native experience. Card management was a web view inside the app. Apple requires a fully native card experience before it allows Apple Pay provisioning in an app, so without going native we couldn’t ship Apple Pay.

We did a lot of work at the start: laying out the Apple Pay flows, and being careful about every way a card can get added to a wallet. The watch, the phone, different wallet situations, different entry points. We showed what the native add-to-wallet flow looks like. The point was for Apple to see we’d accounted for everything, and it kept the back and forth low. While designing Apple Pay, I made sure the same flows also worked for Google Pay and Samsung Pay, so they could launch alongside it.

There are two roles. A card admin issues cards, sees who’s using them, and sets spend limits. A cardholder just sees and uses the card assigned to them. If cardholders could set their own limits, it would get chaotic. A card admin is also a cardholder, with more permissions. Cards are active, inactive, frozen or canceled. The native card experience shipped in May 2025, and Apple Pay launched in December 2025.

A high-level view of the Apple Pay flows we laid out for Apple: every way a card can be added, on the phone and the watch.
A high-level view of the Apple Pay flows we laid out for Apple: every way a card can be added, on the phone and the watch.
Native card management: reveal, freeze, label, and the Add to Apple Wallet action that the whole flow existed to unlock.
Native card management: reveal, freeze, label, and the Add to Apple Wallet action that the whole flow existed to unlock.
04

Expense transactions: one thing, one place

We had three tables with overlapping information: transactions, expenses, and an accounting table for the finance team. As a cardholder, you didn’t know where to submit an expense or what to do next. Transactions held the raw financial data. Expenses held the receipts, categories and descriptions. One card swipe lived in two places.

We merged the old transactions table and the old expenses table into one expenses table. It’s where you see your expenses, what needs doing, and any approvals waiting on you. What we cut was the extra sources of truth. Update one and you’d have to update the other, and nobody knew what a transaction was versus an expense. The accounting table stays separate. Finance admins land there to reconcile, and they don’t care what happens in the expenses table.

The bugs showed how deep the split went: descriptions not saving, wrong dates from backfill, a submission screen stuck in an open-close loop. Engineers mixed up status and accounting status mid-build, and we renamed APIs to stop it. Asma drove the merger proposal in October 2025, after users reported the backfill behavior as a bug. To ship, we also cut scope: no reviewer hierarchy, no disabled states, no flag as incomplete. The app shipped on April 3, 2026, and the full launch followed on April 7 and 8, on both the dashboard and the app.

One table, one place: every card swipe as a single row with card, status, and cashback, filterable by card, date, amount, and status.
One table, one place: every card swipe as a single row with card, status, and cashback, filterable by card, date, amount, and status.

What came of it

Four native flows shipped between May 2025 and August 2026.

  • Payments list: search covers customer name and email, date headers stick while you scroll, statuses are in plain words, and disputes have their own tab.
  • Create payment link: one step, with an explicit add-fee step, a customer info drawer and a “link ready to share” success screen.
  • Mamo Card: PAN and CVV reveal, freeze and unfreeze, cancel, and activating a physical card with a QR scan. Apple Pay launched in December 2025, alongside Google Pay and Samsung Pay on Android, and successful Apple Pay card spend grew about 21% from June to July 2026.
  • Expense transactions: one table across the dashboard and the app, requirements you can customize per submission, and a dedicated Accountant Hub. The launch had an email, a help center article, a YouTube walkthrough and a LinkedIn post.

Reflection

What I’m proudest of

  • Leading the move to native: merchants went from waiting on a web view to getting things done on the go.
  • Apple Pay: it’s the part I care about most, because people use it. We built the native card flows Apple needed to make that possible.
  • The expense merge: three tables became one expenses table, and getting there meant cutting.
  • The success animation: a checkmark that turns into a QR code you can scan is where design and motion meet.

What I would do differently

  • Design for the app from the start: for any new feature or redesign, ask how it works on the app and whether it complements the dashboard or mirrors it. The answer shouldn’t be “we’ll build it for the app later.”
  • Make the app a remote control for the dashboard: we often couldn’t, because of time, and the dashboard was where most things got done. The app wasn’t as adopted as the dashboard, and the aim was to get it there. Even small things help, like notifications and action items you can handle from your phone.
  • Scope disputes with the payments list: I designed the payments list and create payment link in parallel, but disputes landed in a later sprint.
  • Check API names against the design spec before build starts: on expense transactions, I caught the naming confusion later than I should have.