Ustocktrade

Project overview

Ustocktrade came to Amodhi with a web-first trading platform, an unclear target audience, and a competitive landscape dominated by dark, crypto-forward interfaces built almost exclusively for experienced male traders.

Their opportunity was the opposite: a platform that could serve sophisticated day traders and complete novices within the same experience of being welcoming without being patronizing, and powerful without being intimidating.

Challenge

The core challenge was strategic, not just visual.

Ustocktrade needed one product that worked for two groups with fundamentally different needs:

• Experienced day traders who wanted advanced automation and control.
• First-time investors who felt overwhelmed by jargon and complex order types.

Designing purely for power users would alienate newcomers. Designing only for beginners would frustrate serious traders. Splitting into two separate products would create operational complexity and dilute the brand.

It was imperative to find a way to make a single interface feel safe for beginners and powerful for experts.

Strategy & Research

It was clear that the solution would be found through deeply understanding both audiences before making any design decisions.

Amodhi ran a series of focus groups and one-on-one interviews across four segments, ranging from active day traders to first-time investors. Some sessions were conducted in person, others remotely, to see how people interacted with trading tools in different contexts.

Three strategic questions guided the research:

• Who sits at the extremes of each audience, and what do they absolutely need?
• Where do their needs genuinely overlap, and where do they conflict?
• What must be visible in the default view, and what can safely be one layer deeper?

This gave a clear picture of where complexity helped and where it created paralysis.

Key insights

From the research, a few patterns emerged quickly:

• Active traders needed to set and manage complex automation rules, without being tethered to a screen all day.
• New investors wanted the ability to buy and sell with confidence, but found concepts like stop losses and limit orders intimidating and anxiety-inducing.
• Both groups cared about clarity at the moment of making a trade: they wanted to know exactly what was happening and what would happen next.

The insight: the problem wasn’t that the platform had “too much” power. The problem was that all of that power was exposed too early, in the wrong place, and in the wrong way.

Solution

The solution wasn’t two separate products. It was one carefully structured interaction.

The approach centered a single trading tile that surfaced only what every user needed at a glance:

• Current stock value
• Bid and ask
• Immediate buy and sell actions

From there, complexity became optional rather than unavoidable.

• Simple, common rules and actions appeared by default.
• Advanced automation, custom rules, triggers, and order types, lived one tap deeper for the people who wanted it.

For experienced traders, the tile felt powerful and efficient: everything they needed was available with minimal navigation.

For first-time investors, the tile felt understandable and safe: nothing “scary” or overly technical stood between them and a basic trade, but the platform could grow with them as they became more comfortable.

The core design principle was progressive complexity: show the minimum to act with confidence, and allow depth for those who seek it.

Results

Ustocktrade launched on iOS and Android with this new interaction model at its core.

Within six months of launch, the platform became the number six trading app in the United States.

The product was able to attract and retain both types of users without fragmenting into separate beginner and advanced experiences.

Key lessons

Working with Ustocktrade reinforced a few beliefs that guide how Amodhi approaches complex products:

• Designing for power and accessibility is not a compromise. It is the strategy.
• Dual-audience products work best when complexity is layered, not split into different products.
• You only find the right threshold between “simple” and “powerful” by talking to both audiences early, before you commit to your product architecture.

For us, this project is a reference point: whenever a client comes to us with a complex, multi-audience product, the same question applies: what belongs in the first glance, and what belongs one layer deeper?