Building Home: a new activation layer for a trading app

How a new section gave new users a reason to stay, and the team a platform to keep learning.

RoleProduct Designer · Growth
ContributionDesigned Home end-to-end, from research to shipped UI. Contributed to the design system. Partnered with the PM and trading specialist on prioritization and logic. Worked closely with engineering and analytics through implementation.
CORE TEAM
(1)

About Doto

Doto is an international trading platform available on mobile and web. Users trade currency pairs, stocks, and commodities. The product attracts a wide mix of users: from experienced traders to complete beginners.

Main markets: South Africa, Vietnam, LATAM, MENA.

Platforms: iOS, Android, web.

(2)

The problem

New users landed straight inside the trading terminal: a dense interface built for people who already knew how to trade. There was no onboarding, no orientation, no clear next step.

Most of them never made it to a first deposit. Both paid and organic traffic dropped off early, often within the first session: users opened the app, tapped between tabs trying to figure out what they were looking at, and left.

First-deposit conversion was a known business problem; one that several teams had been working on for a while, from different angles.

(3)

Before Home: earlier experiments

The work was scattered and parallel. A few examples of what had been tested:

  • Two product tours. My team (Growth) tested a post-registration fork with multi-step tour variations inside the terminal. Most users stayed in demo, engagement dropped after step two, deposit didn't move.
  • A deposit bonus. Up to +50% in matched bonus funds, with banners on Accounts and Deposit pushing the offer. It didn't meaningfully move conversion, and the users it did attract tended to lose money quickly and never return.
  • A redesigned deposit flow. Simplified screens, new payment methods per geo, and a clear post-transaction status screen that cut related support tickets. Helped at the margins, but didn't change the overall picture.
  • The team had tested landing new users on different existing screens: Accounts, Watchlist, the Terminal itself. None worked as a starting point.

The same pattern kept showing up: every intervention was layered on top of the existing structure. None of it changed the moment that was actually breaking the experience: a new user landing inside a trading terminal and not knowing what they were looking at.

(4)

Reframing the problem

The pattern across these attempts pointed to something: the product was missing a layer. A place to land users before the rest of the product — a section that could support onboarding, orientation, education, account setup, and discovery.

To shape this layer, I ran the research: a competitive analysis, user interviews, and a funnel and drop-off review with the PM. Throughout, we kept aligning with C-level stakeholders and the team, turning workshops and research into tested hypotheses and activation modules.

(5)

Shipping it across 11 releases

Building Home wasn't just adding a new screen, it was a structural change that touched app navigation, account management, and guidance patterns across the product.

We shipped it incrementally across 11 releases, starting with the frontend, then the harder product logic: margin levels, leverage warnings, bonus safety. Each release had to stand on its own, so my job was to make every step read as a finished product, not a work-in-progress.

(6)

Home

The old navigation organized the entire app around execution. Trading was the primary tab, but Watchlist, Positions, and Accounts all assumed the same mental model: you're here to trade, here are the tools. That worked for users who already knew what they were doing, and against everyone else.

Home was designed as a different kind of starting point. The product's center of gravity shifted from execution to orientation, without losing access for users who came to trade.

(7)

Onboarding

Account setup at Doto involved real-world dependencies: identity verification, source-of-funds checks, deposit methods that varied by geo. Any of these could stall, and when they did, users had no way to see why or what to do next.

The onboarding widget on Home made that path visible: where the user is, what the next required action is, and what's blocking them when something gets stuck.

(8)

Account management

Account management was redesigned around one decision: show one active account at a time.

The old Accounts screen did three jobs at once: listing every real, demo, and archived account, surfacing detailed financial metrics, and offering multiple actions.

On Home, those three jobs were split into three surfaces. The active account sits at the top with three primary actions: Deposit, Withdraw, Manage. Switching accounts moved into a dropdown at the top of the screen. Detailed metrics moved into Manage, available when needed but no longer competing with the primary actions.

(9)

AI Market Insights

User research had already surfaced a clear signal: users didn't want a "magic make money" button. They wanted to understand why an action might make sense.

Combined with another finding (that breaking news was often what pushed users to trade in the first place) the opportunity took shape: structured, explainable insights tied to the news driving user decisions.

Working with a PM, engineer, and trading specialist, we designed AI Market Insights: a widget that pairs news from verified sources with signals from our market data provider, then uses an LLM to turn them into a short, structured read. I shaped the card format and the three-part structure: what happened → why it matters → what to do next, so a non-expert could act on it at a glance.

(10)

Home as platform

Beyond onboarding and account management, Home was designed to host a set of lightweight, modular blocks: places where the team could try things, learn fast, and swap what didn't work. I designed the modular structure itself: how blocks slotted into Home, and how each could be reordered, tested, or replaced without a full redesign every time. That's what made every block independently testable, replaceable, and measurable. Three examples:

Stories: integrated via Storily (a third-party tool with built-in polls and voting), giving the team a flexible channel for promos, product updates, and segment-specific education.

Asset discovery: a block for surfacing trading opportunities, tried in three variants: Top Movers (by price change), Popular (by user interest), and Most Traded (by volume). Because variants could be reordered or A/B tested, the team could learn which logic actually helped users find trades.

Learn: a surface for short-form education tied to specific trading actions, with reach and engagement tracked per topic, so the team could see which areas users actually wanted to understand better.

Home stopped being a screen and became a layer the team kept building on!

(11)

Outcome that compounds

Because every module could be tested and swapped on its own, the team stopped rebuilding structure for each new idea: activation hypotheses that used to need a redesign now shipped as blocks on Home, about 3x more per quarter with the same team. Faster experiments, compounding into real numbers:

1.7x

First deposit conversionnew users, within 7 days of signup

1.5x

30-day retentionnew-user cohorts

*New-user cohorts, before vs after Home became the default landing for new users.