Fintech · Mobile app · Product design

Gentle: A connected investment portfolio experience

Helping people understand their investments, explore individual holdings, and set a price alert through a clear, connected mobile journey.

UX ResearchInformation ArchitectureUser FlowsInteraction DesignFigma Prototyping
Explore the interactive prototype ↗ Portfolio home ↗
01 — The challenge

Make portfolio information easier to understand and act on.

Gentle helps people track different investments in one place. The design challenge was to create a connected experience where users can review their portfolio, drill into Stocks and a specific holding, set a price alert, and return later to review or edit that alert without losing context.

My focus

Build a clear journey from portfolio overview to a specific stock alert, while keeping invested value, current value, and alert conditions easy to distinguish.

Scope boundary

The experience is for monitoring and understanding investments. It does not execute trades or recommend what users should buy or sell.

02 — Research & understanding

Start with user needs, then study existing patterns.

This was a hypothesis-led design exercise, not a completed user-interview study. I used a proto-persona to make assumptions visible, reviewed competitor patterns, and translated those findings into the proposed flow.

Proto-persona · Assumption

Priya, 24 — early-career investor

Needs a quick overview of portfolio performance and a simple way to monitor individual holdings. The persona represents a working hypothesis to validate, not a verified research participant.

Needs: understand returns, compare invested and current values, create alerts, and edit saved rules without financial jargon.

Competitor patterns

INDmoney & Groww

The review focused on portfolio overview and context, stock and mutual-fund information, performance presentation, and how price alerts and notifications are communicated.

Design takeaway: keep the portfolio summary as context, make the selected holding clear, and show the exact alert threshold before saving.

Question to validate with users

When setting a price alert, would you rather choose a percentage drop or enter an exact target price?

03 — User journey

Keep the path forward, backward, and editable.

1

Portfolio overview

Orient the user with total invested value, current value, and asset distribution.

2

Stocks category

Narrow the portfolio to one asset type and compare individual holdings.

3

TCS holding

Show shares owned, average purchase price, and sample current price.

4

Set a price alert

Choose the alert type and preview the exact trigger value before confirming.

5

Saved alert

Confirm the rule, then provide a route back to TCS to review or edit it.

The prototype brief also called for an alternative state, such as an alert that fails to save, alongside the back and edit routes.

04 — Key design decisions

Make financial information and system feedback explicit.

Separate invested and current value

Use explicit labels and a consistent hierarchy so users do not confuse the amount invested with the current portfolio value.

Preview the trigger

Show the resulting alert threshold before saving, helping users confirm the rule they intended to create.

Preserve navigation context

Allow users to move back through the portfolio and return to the saved alert without restarting the journey.

Design for clarity and accessibility

Use legible labels, sufficient contrast, usable touch targets, and indicators that do not rely on color alone.

05 — Outcome & reflection

A connected prototype built around a clear monitoring task.

The deliverable brings together problem framing, a proto-persona, competitor-pattern review, a user flow, mobile UI, and an interactive Figma prototype. It is a concept/assessment project, so I am not presenting usability results or business impact metrics that were not measured.

What I would validate next

Test whether people understand the difference between invested and current value, whether the alert setup language is clear, and whether users can find and edit a saved alert without assistance.

View prototype ↗