Dart: ROSCA Fintech Mobile App

DART is a US-based fintech app bringing the traditional committee savings model to modern mobile banking. The core challenge wasn't payments. It was trust.

A fintech app designed around trust helping US users participate in group savings circles with people they know.

End-to-end product design discovery, research, IA, user flows, wireframes, UI, and dev handoff. Shipped to closed beta.

Before I opened Figma, I had to understand the thing I was designing.

A committee is simple. 10 people. Each contributes $1,000 a month. Every month, one person receives the full $10,000 pool. No bank. No interest. Just trust — and a guaranteed turn. Millions of people around the world run these in living rooms and WhatsApp groups. My client wanted to bring that to the US and make it trustworthy enough for people to actually use.

The brief landed. Something immediately stood out.

I received the scope of work, read it carefully, and the challenge became clear fast this wasn't a payments app. It was a trust app. The design problem wasn't how to move money. It was how to make people feel safe giving it to strangers.

Trust how do you make strangers feel safe handing over money? Simplicity the mechanic is completely unfamiliar to US users. Focus too many features would break the core promise.

Before touching visuals, I mapped every screen and every decision point.

This is where I caught something important something the brief hadn't flagged. The full navigation structure, every user path, every edge case mapped before a single frame was designed.

I killed public groups. Here's why.

The original scope included public groups open circles where strangers could join freely. The more I mapped the flow, the more it broke the core promise of the app. You can't ask someone to hand over $1,000 to people they've never met and expect them to feel safe. Public groups introduced too many unknowns identity, reliability, trust. It wasn't a feature problem. It was a trust problem. I went back to the client with the data, the reasoning, and a clear recommendation: cut it. Keep it invite-only. Private groups only. He agreed. We never looked back.

Structure before surface.

Before committing to any visual decisions, I built out low fidelity wireframes to get the skeleton right. This was the approval checkpoint nothing moved to full UI until the layout logic was signed off.

I didn't hand over files and walk away.

I worked with the development team through implementation answering questions, flagging edge cases, making sure the design intent stayed intact all the way to skeleton screens. Near-zero revisions on the final UI. The handoff worked because the thinking was documented from the start.