Blue means one thing here: the range you are looking at.
The value chart is a row of thin gray bars, and only the selected date range fills in blue. You read the period that matters and keep the months around it as context.
The phone carries the same chart above the holdings list. Each coin gets its own small bar chart between the name and the amount, so you can scan the whole portfolio for movement without opening a single coin.
Trading screens get busy fast. This one stays light and calm, so the numbers lead: total value, realized and unrealized P&L and open positions, all on one screen.
Your SaaS product might be solving the wrong problem. And most designers don't realize it.
Before jumping into Figma, designing dashboards, or creating beautiful interfaces, there's something much more important to understand.
The difference between a Business Problem and a User Problem.
In Part 01 of my SaaS Product Design Masterclass, I'm breaking down:
πΉ 1.1 β Start with the Business Problem
πΉ 1.2 β Understand the Business Impact
πΉ 1.3 β Identify the User Problem
πΉ 1.4 β How Business Problems and User Problems are connected, but different.
Here's an important thought:
A business wants to achieve a goal.
A user wants to solve a problem.
Great digital products understand both.
This is where meaningful product differentiation begins β not with UI, but with problem understanding.
π― This is Part 01 of my 10-hour practical SaaS Product Design series, where I'll walk through the complete process of understanding and designing a SaaS product.
If you're a UX/UI Designer, Product Designer, aspiring designer, or SaaS founder, this series is for you.
One question: Do you start your design process with business problems or user problems?