Day 261 / 365 — Continuing the daily UI momentum with a bold, modern, and high-impact digital des...Day 261 / 365 — Continuing the daily UI momentum with a bold, modern, and high-impact digital des...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Day 261 is quite a sustained design practice. How do you decide which parts of each daily concept to explore deeply and which to keep as a quick experiment?
Designed a dashboard concept for tracking net worth across every asset type — stocks, crypto, property, pensions, funds, cash, and liabilities — all in one place.
Instead of the usual pie chart or bar graph, the centerpiece is a dial: a single, glanceable gauge showing where your wealth actually sits. Behind it, a quiet grid of every asset category fades in and out of visibility, reinforcing that everything's accounted for even when it's not the focus.
Dark UI, a single confident green accent, and a lot of negative space — built to make a genuinely overwhelming task (seeing your entire financial picture at once) feel calm instead of cluttered.
Employee list screens are the homework assignment of SaaS design. A table is a table is a table. Nobody's winning an award for this view and that's exactly why it matters.
The restraint here is the point. No colored tags, no status badges fighting for attention, no dashboard widgets crammed into the sidebar. Just the data, breathing in a dark container with enough row spacing that your eyes don't blur at record five.
That split between a bold brand identity and a restrained product UI is one of the hardest things to get right in B2B SaaS.
"A table is a table" is the harder argument to make internally than the design itself - most teams would've shipped colored status tags just to have something to show in a review.
Icon cards for me, bouquets are such a visual purchase that a scannable icon beats reading "small/medium/large" every time. Did the compact chips version convert worse in testing, or are you still gathering data on that?