Monie

Monie is a consumer fintech app that brings a spending account, a card, and everyday money-management tools into a single mobile experience. Its promise, stated across onboarding and the marketing site, is to let people control their finances with one account for budgeting, spending, and sending, staying "always in control of your money." The headline benefit is simple: control your daily expenses better, powered by instant, real-time transfers between Monie accounts at no extra fees.

The product was built for the Egyptian market, with balances in Egyptian pounds, phone-number onboarding, and local merchant and location examples, and it was pitched around financial wellness for everyday users rather than finance experts. Day One Technologies was the design partner and the work ran as an end-to-end engagement: turning the client's early concept into wireframes, exploring several high-fidelity directions, converging on a final design and a reusable design system, and designing a responsive marketing website to launch the product.

Everyday consumers who wanted to manage their money well were juggling disconnected tools and opaque banking. Spending, budgeting, saving, and sending money lived in different places, so there was no single view of where money went. People had little insight into what they spent, on what, and with whom, and no easy way to set and hold a budget. Sending money was slow and carried unpredictable fees, which the product answered with instant fee-free transfers and a promise of fair, fixed pricing and no hidden fees. And saving happened, if at all, without structure, with no motivating way to put money aside for a specific goal inside the same app people spent from.

Two further tensions shaped the work. First, the product had to earn trust as a money app, which meant secure but friendly onboarding and login, while still feeling effortless for a mainstream, finance-averse audience carrying genuinely sophisticated capabilities like analytics, per-category budgeting, and goals. Second, the design had to converge a client and a multi-designer team, several people were producing wireframe and direction variants, onto one coherent visual language before committing to a final build.

The core idea was a single mobile money app, backed by a marketing website, that unifies spending, sending, budgeting, analysis, and saving under one account with a clear, approachable interface. One account and card sit at the center (total balance, top-up, transactions), surrounded by the four money jobs a person actually has: sending, through instant fee-free peer-to-peer transfers between Monie accounts; understanding, through categorized transactions plus a spending analysis and insights view; controlling, through per-category budgets with live progress tracking; and saving, through goal-based Money Box savings kept separate from the spendable balance. Every transaction is enriched with category, merchant, location, receipt, notes, and a split-the-bill action, so a raw feed becomes something users can actually learn from. Onboarding and login were designed to build trust fast, with phone-number verification, memorable-information login, and Face ID.

Reaching that product was itself a method. Rather than commit to one look early, I turned the client's concept sketches into structured wireframes, then produced several distinct high-fidelity design directions, including full light and dark theme studies, so the client could compare complete experiences before converging on a final direction and a reusable design system. A responsive marketing website was designed in parallel to introduce the product and drive early sign-ups ahead of launch.

Structured data is what makes a money app feel smart. The features users value most, spending insights and budgets that actually hold, are only possible if the transaction data underneath is rich and categorized from the start. Designing enrichment into the transaction itself, rather than bolting analytics on afterward, was the decision that made everything downstream work, and it taught me to design the data model, not just the screens.

On a long, multi-direction engagement with several designers, structured comparison prevents churn. Presenting one look invites subjective debate, but rendering complete directions and full light and dark themes side by side gave the client and the team something concrete to choose between. Turning "which do you prefer" into a real comparison of finished experiences was the single most useful move for converging a group without circling.