Mirelle
  • Work
  • About
  • Let's Talk
Back to Work
NDA — Company & product details anonymised
UX/UI Design · Mobile App · Financial Services

Designing clarity
and trust — for a
wealth management app

Existing clients expect more than a functional app. They expect an experience that reflects the standard of service they already receive — clear, composed, and built around their needs. This case study is about how I designed that experience from the ground up.

Role
Product Designer (UX/UI)
Platform
iOS & Android mobile app
Users
Existing clients
Scope
End-to-end UX/UI design
Status
Shipped
02 · Context

A high-trust relationship, moving into a digital channel

The platform serves existing wealth management clients — people who already have an established relationship with the firm and their dedicated advisor. This wasn't a product for acquiring new users. It was a product for deepening an existing one.

That context changed everything. The users were not looking to be impressed by the app — they were looking for the app to quietly do its job: show them their portfolio with accuracy and clarity, give them access to their documents, and let them reach their advisor without friction. Trust had already been established offline. The app's job was not to build it from zero — it was to not damage it.

Financial data added a further layer of complexity. Portfolios involve multiple asset classes, currencies, time horizons, and performance metrics. Presenting all of this clearly — without oversimplifying or overwhelming — was one of the central design challenges throughout the project.

Portfolio visibility
Clients need an accurate, readable view of their investments — across asset classes and performance periods.
Document access
Statements, reports, contracts, and signed documents — structured, searchable, and securely accessible.
Advisor access
A direct, human line to the client's dedicated advisor — messaging and meeting requests built into the experience.
Secure authentication
Multiple auth flows for trusted and new devices, designed for security without creating unnecessary friction.
03 · The Challenge

Designing for people who are used to the best

Wealth management clients have high expectations — not because they are difficult, but because they are used to a standard of service that most digital products don't reach. The app had to match that standard across every screen.

Challenge 01
Making complex financial data legible
A private portfolio is not simple. Multiple asset classes, mixed currencies, varied time horizons, unrealised vs realised gains, risk metrics. Presenting this with clarity — without stripping out the detail clients actually need — required careful hierarchy and progressive disclosure throughout.
Challenge 02
Creating trust through visual design alone
In financial services, trust is built over years of human interaction. A digital interface has seconds to signal the same credibility. Every visual choice — spacing, typography weight, colour usage, iconography — needed to feel deliberate, composed, and worthy of the context.
Challenge 03
Onboarding existing clients without friction
Clients entered through a secure, personalised invitation flow — not a standard self-sign-up. That entry point had to be seamless. A client who has already placed significant trust in their advisor cannot encounter a generic, confusing registration experience — it would undermine that trust immediately.
Challenge 04
Authentication complexity across device types
The app needed different authentication flows depending on whether the device was trusted or new — balancing security requirements with the usability expectations of clients who are not technically minded. Security friction had to be justified and clearly communicated at every step.
Challenge 05
Handling sensitive documents with confidence
Document management involved legal and financial records, including contracts requiring digital signatures. Every interaction in this area needed to feel deliberate and controlled — clients needed to feel in command of every action, not uncertain about what they were agreeing to.
Challenge 06
Balancing detail and simplicity across user types
Clients varied in their financial literacy and interest in detail. Some wanted a high-level summary; others wanted access to every data point. The design needed to serve both without creating two separate products — a single adaptive information architecture was the only sustainable solution.
04 · My Role

End-to-end design ownership

I was responsible for the full UX and UI design of the client-facing application. That meant not just producing screens, but understanding the context deeply enough to make the right decisions — about what to show, how to sequence it, and what to leave out.

I worked closely with stakeholders who had domain expertise in wealth management operations, and with developers who were building the platform in parallel. Balancing those two inputs — business requirements and technical constraints — while keeping the client experience at the centre was the ongoing challenge of the role.

UX / UI Design
Wireframes, flows, and high-fidelity screens for the full app.
Onboarding Experience
Personalised onboarding from secure invitation through to active account.
Authentication Flows
Trusted device, new device, and session recovery flows.
Portfolio Dashboard
Financial data hierarchy, asset breakdown, and performance views.
Document Management
Document library, viewer, signing flows, and history.
Advisor Interaction
Messaging and meeting request flows between clients and their dedicated advisor.
Stakeholder Collaboration
Regular reviews with cross-functional stakeholders across product, compliance, and delivery.
Design QA
Reviewing built screens against design intent, raising discrepancies, and iterating.
05 · Key Flows

Where design decisions had the most weight

Five flows defined the core experience. Each came with its own set of design problems — and each required careful thought about trust, clarity, and control.

Flow 01 Personalised Onboarding

From first touchpoint to active account — without a single moment of confusion

The problem
Clients entered the app through a secure, personalised invitation — not a generic sign-up. Their first touchpoint had to feel as considered as the relationship itself. Standard onboarding patterns — "Welcome to our app, enter your email" — were completely wrong for this context.
The solution
I designed a personalised entry experience: the client was welcomed by name from the first screen, their dedicated advisor was introduced visually, and the flow was scoped to what they specifically needed to set up. The registration steps were minimal — only what was essential for security. Nothing else. Each step was framed in plain language with a clear explanation of why it was needed.
A first experience that felt like it was built for them, not for everyone.
Onboarding flow diagram showing the full sequence from secure invitation to active account
Onboarding Flow
Secure invitation flow — personalised onboarding entry screen
Invitation entry
Secure invitation flow designed for a guided onboarding experience
Flow 02 Authentication

Security that explains itself — without making users feel suspected

The problem
The app needed two distinct authentication experiences: a streamlined login for a trusted device (where biometrics or PIN was established), and a more rigorous flow for a new device — verifying identity and re-establishing trust before access was granted. Many financial apps solve this technically but communicate it poorly — leaving users confused about what's happening and why additional steps are required.
The solution
I designed clear state transitions between the two flows, with contextual explanations at each step. The new device flow was framed as a protection measure rather than an obstacle — the language was transparent about why verification was needed. The trusted device flow was minimal by design: login should feel effortless when trust is already established. Error states were designed to guide rather than block — offering a clear recovery path at every failure point.
Security communicated clearly enough that it builds confidence, not anxiety.
Simple and secure login experience for returning users
Returning user login
Simple and secure login experience for returning users
Flow 03 Portfolio Dashboard

A portfolio overview that informs without overwhelming

The problem
A private investment portfolio contains a significant amount of data — total valuation, asset class breakdown, individual holdings, performance across multiple time periods, income, unrealised gains, currency exposure. Showing everything at once creates a dashboard that reads as noise. Showing too little fails the clients who want precision.
The solution
I structured the dashboard around three levels of information density. The top level presents a single headline figure (total portfolio value) with period performance — the number clients check most often. The second level shows asset class allocation — the context behind the number. The third level gives access to individual holdings for clients who want to drill down. Each level is accessible from the one above it, but none forces the user deeper than they want to go.
Every client type — from overview readers to detail seekers — finds what they need without compromise.
Overview dashboard providing clear visibility of client portfolios
Portfolio overview
Overview dashboard providing clear visibility of client portfolios
Flow 04 Document Management & Signing

Sensitive documents handled with the care they deserve

The problem
Clients access account statements, quarterly reports, investment proposals, and legal contracts through the app. Some of these documents require a digital signature. The challenge was creating an experience that felt organised and professional — not like a file storage afterthought — and that handled the signing flow with the gravity it required.
The solution
I designed a categorised document library with clear organisation by type and date, search functionality, and unread indicators that drew attention to new items without being intrusive. The signing flow was separated from passive document reading — entering a signing context was a distinct mode with its own visual language. Before any signature was captured, the document content was surfaced with a summary, so clients knew exactly what they were committing to.
Document interactions felt as deliberate and controlled as the financial decisions they supported.
Document flow diagram showing the categorised library, document viewer, and signing sequence
Document Flow
Structured document management with clear categorisation
Document library
Structured document management with clear categorisation
Flow 05 Advisor Interaction

Keeping the human relationship at the centre of a digital product

The problem
The dedicated advisor is the most important person in a private client's financial life. The app couldn't become a wall between client and advisor — it had to reinforce that relationship. This meant making the advisor feel present in the product, not reduced to a support ticket system.
The solution
I designed an interaction model that was personal rather than transactional. The advisor's name and photo were present throughout the app — not just on a contact page. The messaging interface was positioned as a direct channel, not a generic inbox, with clear message threading and response indicators. Meeting requests were simple to initiate — a contextual shortcut tied to the portfolio view — so clients could act on financial questions immediately rather than navigating away to find contact details.
The advisor relationship felt continuous across digital and in-person touchpoints.
Centralised notifications keeping users informed and in control
Notifications & updates
Centralised notifications to keep users informed and in control
06 · Key UX Decisions

The choices that shaped how the product feels

In a product built around trust and financial clarity, the smallest UX choices carry significant weight. These were the decisions that defined the experience most.

Decision 01
Progressive disclosure as the structural principle
Every screen was designed with a primary piece of information — the one thing the client needed to understand first. Additional detail was accessible but not forced. This wasn't about hiding information; it was about presenting it in the order that matched how a client actually thinks about their portfolio. The total value before the breakdown. The breakdown before individual lines.
Clients felt in control, not overwhelmed, at every level of the product.
Decision 02
Typography doing the heavy lifting in data screens
Financial data screens can quickly feel like spreadsheets. I used typographic hierarchy — weight, size, and colour — to create visual structure without relying on lines, boxes, or heavy visual chrome. A larger, heavier headline figure reads as primary. A smaller, muted supporting figure reads as secondary. The structure communicates itself without needing to be drawn around everything.
Data-heavy screens felt calm and readable, not dense or technical.
Decision 03
Deliberate use of colour as a trust signal
In consumer finance apps, green and red are used aggressively — gains celebrated, losses alarmed. I took a different position. Clients with significant portfolios are sophisticated investors. Oscillating colours create anxiety without insight. Colour was used sparingly and purposefully — not as commentary on performance, but as structural differentiation between data types.
The tone of the product matched the composure of wealth management itself.
Decision 04
Friction as a feature in high-stakes interactions
For irreversible or legally significant actions — signing a document, confirming a meeting, acknowledging a disclosure — I introduced intentional friction. A review screen before a signature. An explicit confirmation before submission. This friction was not an obstacle; it was a signal that the action mattered — and gave clients confidence that the system was taking their actions seriously.
Clients felt the appropriate weight of consequential actions — without feeling obstructed.
Decision 05
Naming and language as a design material
Financial terminology is precise but not always plain. I worked with stakeholders to establish a language register for the app — formal where required by regulation, plain everywhere else. Labels, headings, and button copy were all treated as design decisions. "View report" is clearer than "Open document." "Confirm meeting request" is clearer than "Submit." Every word was chosen, not defaulted.
The app communicated with the clarity and confidence of the brand it represented.
Decision 06
Empty states as experience moments
New accounts have no history. A new client seeing their portfolio for the first time might have no statements yet, no documents, no performance history. I designed empty states that felt intentional — contextual explanations of what would appear, and when. A new client shouldn't feel like they've broken something; they should feel like they've arrived somewhere with a clear sense of what comes next.
The first-use experience felt guided and purposeful, not incomplete.
07 · Key Screens

Selected views from the application

All client data, names, and identifying information are anonymised. Placeholders preserve the intended proportions for mobile screens.

Secure invitation flow — personalised onboarding entry
Welcome — Invitation Entry
Personalised welcome within the secure onboarding flow
Uploading required documents as part of a secure verification process
Verification — Document Upload
Uploading required documents as part of a secure verification process
Multi-step verification flow to ensure secure account setup
Verification — Mobile Confirmation
Multi-step verification flow to ensure secure account setup
Document flow diagram showing the categorised library, document viewer, and signing sequence
Document Flow
Secure document review and approval experience. Context is shown first; the approval action comes after.
Onboarding flow diagram showing the full sequence from secure invitation to active account
Onboarding Flow
Full onboarding sequence from secure invitation to active account setup.
Overview dashboard providing clear visibility of client portfolios
Portfolio Dashboard
Headline value, allocation, and performance
Detailed asset view with performance insights and contextual data
Holdings Breakdown
Detailed asset view with performance insights and contextual data
Structured document management with clear categorisation
Document Library
Structured document management with clear categorisation
Centralised notifications to keep users informed and in control
Notifications
Centralised notifications to keep users informed and in control
08 · Design Thinking

Designing for a context where mistakes cost more than friction

Financial UX demands a different kind of restraint from consumer product design. In most digital products, the goal is frictionless — remove every obstacle, make every action as fast as possible. In a wealth management context, that philosophy can be actively dangerous. Some friction is protective. Some slowness is deliberate. Some confirmations are not unnecessary steps — they are the product doing its job.

My approach was to start with the client's mental model, not the data model. A client thinking about their portfolio does not think in database rows. They think in terms of questions: How am I doing overall? What's changed since last quarter? Do I have anything that needs my attention? The information architecture was built to answer those questions in sequence — not to expose a data schema through a UI.

Clarity is not about showing less — it's about showing things in the right order, with the right weight, at the right moment.

The best financial interface is one that makes a client feel informed — not one that makes them feel clever for using it.
Guiding principles
  • Clarity before completeness
    Show the most important thing first. Make everything else accessible, not absent.
  • Trust is built in the details
    Precise labels, consistent behaviour, and composed visual language — each signals competence and care.
  • Friction where it protects
    Not all friction is bad. In consequential contexts, deliberate slowness is a feature.
  • Human-first, digital-second
    The advisor relationship is the product. The app is the channel. That distinction shaped every decision.
09 · Outcomes

What the design work produced

The results are structural and experiential — felt in the quality of the product, not captured in numbers.

A smooth, personalised onboarding
Existing clients transition into the app with a flow that feels tailored to them — not generic. The invitation-first model reinforces the quality of the relationship from the first screen.
Portfolio data that reads clearly
The three-level information hierarchy makes the dashboard readable for clients regardless of their interest in detail — no one feels lost, and no one is denied the depth they want.
Authentication that builds confidence
Security flows that communicate their purpose clearly — without making clients feel suspected or confused. The trusted device path is effortless; the new device path is transparent about why each step exists.
Document management done seriously
A structured library and a carefully designed signing flow that matches the legal weight of the documents involved — every interaction feels deliberate, not incidental.
The advisor relationship kept central
The dedicated advisor is not an afterthought in the app — they are a persistent presence. Clients have a direct, low-friction channel to the most important person in their financial life.
A scalable design foundation
The component structure, design language, and interaction patterns are documented and consistent — ready to support new features and expanded functionality without requiring a redesign.
10 · Reflection

What this project taught me about trust and design

Designing for financial services changed how I think about product design broadly. The principles I developed here — about trust, friction, and human-centred complexity — apply well beyond fintech.

What I learned
Financial UX is trust design above everything else
  • The visual language of a financial product communicates competence — or lack of it — before a single number is read.
  • Simplicity in financial UX is harder to achieve than complexity. Removing things requires more confidence than adding them.
  • Language is as important as layout. Imprecise copy in a financial context creates anxiety and destroys trust faster than bad design.
  • The human relationship — the advisor — was the product. The app was an extension of that relationship, not a replacement for it.
What I'd do differently
Earlier client research, deeper exploration of edge cases
  • I'd advocate for direct access to actual clients — even read-only observation of how they currently manage their portfolio information. Stakeholder assumptions about client behaviour aren't always accurate.
  • I'd invest more in edge case design earlier — empty states, error states, and partial data scenarios were sometimes resolved under time pressure.
  • I'd push harder on a notification model. How the app communicates important events (new document, portfolio update) was underspecified.
  • I'd build in earlier touchpoints for regulated content review — compliance feedback on legally sensitive copy sometimes arrived late in the process.
What comes next
Personalisation, notifications, and expanding the product surface
  • Proactive notifications — alerting clients to meaningful portfolio events, document arrivals, or advisor messages in a way that respects their attention.
  • Deeper performance analytics — time-weighted returns, benchmarking, and scenario views for clients who want more detail.
  • A client preferences layer — allowing clients to configure what they see on the dashboard and how performance data is framed.
  • Expanding the advisor interaction model to include shared context and personalised proposals — deepening the app's role as a genuine advisory channel.
Continue exploring
Back to all work
Mirelle

UI/UX Designer · Motion Designer · Brand Identity Designer.
Creating work that moves and endures.

Pages

  • Home
  • Work
  • About

Connect

  • Email Me
  • LinkedIn
  • Instagram

© 2025 Mirelle. All rights reserved.