A retail investment app needed to reach two audiences it wasn't built for.

I was the only full time designer on the project. I shaped the strategy and wireframes with a principal designer, designed most of the UI, and led every client presentation.

My role
Sr. Product Designer
Context
Two designers, contracted through the loyalty solutions tech company
Period
Feb to May, 2026
Platform
Mobile
Tools
Figma Used for workshops, wireframes, and UI design. Claude Used throughout the project to organise research, explore directions, and build prototypes. Gemini Used for illustration. Lovable Used to explore UI directions.

Context

Built for one investor. Needed to work for two more.

A retail investment app wanted to reach two audiences it wasn't connecting with: tech-native younger users who expected something more game-like and exploratory, and white-collar, entrepreneurial investors who wanted to invest with more confidence and structure.

The product had the tools and market data to support both. It didn't have a way to bring either audience in and keep them there.

Problem

User

Users didn't know how to start, where they stood, or how to progress.

The app lacked an experience that guided the investor and made their journey visible. Many users opened it without trading, traded at random, hesitated for lack of knowledge, or stopped after the first trade.

Business

Locked into today's investors, missing tomorrow's.

The product served experienced investors well. It couldn't reach tech natives or entrepreneurs, the audiences the business needs now and in the years ahead. These users matter for growth, not just today's numbers.

Deliverables

From workshop to handoff, across three pillars.

The work ran in phases across three pillars: simulation, learning and gamification. Simulation came first, and each phase was meant to build on it. The gamification framework belonged to the loyalty solutions tech company. My part was the experience around it: simulation, learning, entry points, and games that teach.

2 Client presentations approved, unlocking UI design
2 Pillars designed in UI: simulation across three phases, and learning
3 New game mechanics approved by the loyalty solutions tech company's founder and team, after researching and narrowing down from 43

Approach

Focus first. Then back to discovery, twice.

I worked from a clear focus to low-fidelity wireframes, then went back to the exploring phase twice when the work needed more than a fix.

  1. 1A working session as the team of 2 to define the strategy
  2. 2End-to-end wireframes to reflect the strategy
  3. 3Build consistency before reaching for range
  4. 4Back to discovery, twice

Constraints

Working inside someone else's system

SDK boundary

A technical SDK limited what we could touch. We had to design new entry points without modifying the pages and widgets outside our scope. The constraint shaped where simulation could live in the app.

Data provider limits

Technical difficulties with the market data provider's integration kept simulation lightweight. Buy and sell only, watch the position grow over time. The constraint shaped the final scope, not the ambition behind it.

Execution

Step 1

Strategy into wireframes

Starting point: a tier and currency based framework

The strategy started from a framework suggested by the loyalty solutions tech company and refined with the project team and the client after the workshop. It was their system, and everything we designed was built on top of it.

Gems decide the tier. They come from missions and from recent investing, so a high volume user doesn't start at the bottom. If users stop making transactions for a while, their gems expire and their tier drops. That keeps them investing and playing.

Tiers

Tier 150

Tier 2100

Tier 3200

Benefits

Unlocking paid features

Reduced or zero commission fee

Missions

Trading+N +N

Onboarding, discovery and retention+N

Rewards

Unlocking paid featuresN

Reduced or zero commission feeN

Discounts from partnersN

Embed, don't rebuild

We kept the app's structure and placed entry points where learning made sense: first level pages, detail pages, and key moments in the journey.

One connected learning system

People will be able to learn by experimenting, playing, repeating and competing with friends. Each part leads to the next: lessons connect to missions, missions to the simulation where it fits, and quizzes and tournaments test what stuck.

Reading

Visual

Audio

Doing and experimenting

Social

Repetition

Playing

Tooltips

Onboarding and walk through

Academy articlesBeginner, intermediate, advanced

Micro learningLessons and stories

Data visualization

Listen to articles

Compare returns

Simulation

Friends and activity

Tournaments

Polls

Quiz

Game mode

Prediction games

Never mix the virtual and the real

Simulation had to feel safe. Users should always know whether they are trading with real money or not.

Wireframes for the whole strategy

A click-through prototype based on lo-fi wireframes

Step 2

Laying the simulation foundation

Simulation came first because of an upcoming launch campaign. Users needed a safe place to practice buying and selling.

With the green light confirmed, simulation design began. The first two phases were about consistency, not invention. Entry points, the buy and sell flow, order management. Getting the basics right so everything built on top could hold together.

When we presented the virtual mode switch to the General Manager, the concern was what could go wrong. Backed by our benchmark, we proposed a sandbox: a modal appears when users activate simulation, supported by in-app communication.

Missions and rewards entry widget Simulation entry widget

Step 3

Room to design

Simulation phases 3 and 4 were a different kind of work. Tournaments, leaderboards, joining and leaving flows, a results view that connected simulated decisions to real outcomes.

For the first time the project had space to explore. This phase was built in close collaboration with the client's internal design team, working through directions together across multiple rounds.

Tournaments list Tournament detail Tournament detail with countdown and leaderboard
Click to enlarge designs to see in full

Hard feedback. Worth understanding.

The second presentation to the General Manager covered the complete simulation and learning work. Gamification existed only as wireframes at that point, because the launch campaign put simulation first. That choice had consequences.

One fair critique, one that needed translating

Gamification had not been shown in full. Simulation had inherited the app's core problem. It didn't guide the user. It expected them to find their way around. The feedback also came with permission: leave the app's existing patterns behind, and be braver.

I didn't react immediately. I wrote down exactly what was said, what she had seen, and what it actually meant before deciding what to change. Translating a blunt comment into a real design problem is its own skill.

Empathy map of the General Manager: thinking, expecting, seen and said

Step 4

Back to discovery with AI as a partner

I rebuilt the simulation concept from a different question. Not "how do I trade" but "what am I actually trying to do." The new flow started by asking a user's financial situation and goal, then routed them through the app's existing tools toward a real decision.

I used Claude to map every combination of financial source and goal (nine in total), the tool sequence for each, and the resulting logic. Then I built a working prototype to present it.

An HTML prototype developed with Claude

After I presented the prototype, the team's feedback was direct: stop focusing on simulation. We parked the concept for reuse, and the focus moved to gamification.

Step 5

Finding the right mechanics

With the redirect clear, I researched fintech and edtech apps on Mobbin for gamification patterns, then used Claude to synthesize the screenshots into a structured pool of 43 candidate mechanics from products like Duolingo, Kahoot, and Brilliant.

Free resource

Download the .MD file and use it on your project

Nebula Mechanics Palette: 43 learning mechanics, compiled from benchmark sources, merged, and adapted to the Nebula context.

Download .md file

I filtered against four criteria: context fit, persona fit, sustainability, and build complexity. Three mechanics made it through: rapid-fire concept matching, swipe-based signal sorting, and branching market scenarios.

I presented these to the loyalty solutions tech company first, then to the client. Both aligned on a focused set of lightweight games.

Rapid-fire matching: which instrument Rapid-fire matching: fundamental or technical Rapid-fire matching: concept memory

Step 6

Framework alignment, UI concepts and handoff

After aligning on the games, we worked in two groups from the same brief, exploring framework alternatives. The principal designer and I proposed a linear progression. The loyalty solutions tech company proposed something closer to their original framework, and we aligned on theirs.

I created these UI concepts. They were the last screens I prepared before handing off and closing the project, as the loyalty solutions tech company continued the UI design with the principal designer.

Missions screen Rewards screen Games screen
Click to enlarge designs to see in full

Key insights

A fair start keeps users in the game

If everyone starts at zero, a game feels unfair to your biggest investors. If it only rewards volume, it shuts everyone else out. Counting recent investing toward gems let power users start where they belong, while missions gave everyone else a way to earn their place.

Learnings

A feature can't patch a deeper problem

I believed the app's real problem was bigger than gamification: it didn't know which financial goal users came to solve, so it couldn't help them. I raised it, but the project went ahead as scoped. I learned to say the bigger thing early, then keep designing well inside the scope.