Review a Cryptocurrency Trade Before Placing It
Design a trading ticket that explains price movement, fees, network conditions, and order consequences before confirmation.
The brief
Understand the problem
Background
Digital asset prices can move quickly, and users may confuse quoted value with guaranteed execution. Market orders, limit orders, fees, and network transfers expose different risks.
User context
Luis has previously bought small amounts of cryptocurrency. He wants to sell part of a holding if its price reaches a target while understanding the fees and possible execution range.
Product problem
Dense market interfaces can encourage action without comprehension. The trade flow must communicate uncertainty, order behavior, and irreversible consequences at the right moments.
Objective
Create a transparent sell-order flow with market context, order configuration, review, and status tracking.
What to design
Define the experience
Required experience
- Asset overview with price history and data freshness
- Market and limit order entry
- Order review with estimated proceeds and fees
- Open, partial, completed, and cancelled order states
Screens and states
- Asset detail
- Order ticket
- Order review
- Open order
- Execution detail
Core user flow
Follow the critical path
- 01
Luis reviews the asset price and selects sell
- 02
He chooses a limit order and enters amount and target price
- 03
He reviews estimated proceeds, fees, and how partial execution works
- 04
He confirms with account security verification
- 05
He later sees that the order has partially filled
Product rules
Requirements and constraints
Requirements
- Label delayed and live market data clearly
- Explain market and limit order behavior in context
- Show fees, estimated proceeds, and available balance before confirmation
- Require an explicit review for irreversible actions
- Represent partial fills and cancellation consequences
- Avoid celebratory or urgency-driven trading cues
Constraints
- Prices can change between entry and confirmation
- Trading availability varies by region and asset
- Precision and minimum order sizes differ by asset
- Security verification may time out
Reality check
States worth considering
Finish line
What to deliver
- Design five screens for a limit sell order, including partial execution and unavailable-market states.
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.