600+ projects across 12 countries. 10+ years. Adobe Certified Expert & Instructor, Google UX Certified. I build Framer sites that convert.
Concept redesign of the Booking.com landing page. I moved the hero away from the search-bar-first layout and let a full-bleed photo plus a serif headline set the mood, with the search card floating over it.
Kept the palette to deep navy and one blue accent so the destination photography stays the loudest thing on screen.
When you redesign the hero of a product people know by heart, do you keep the familiar layout or break it?
A government strategic plan with 70 deliverables and dozens of owners usually lives in a spreadsheet nobody trusts.
That was the real problem behind WorkerDI, a platform for a public education body running its 2025-2026 plan. The data existed. What was missing was a way to see, in one glance, what needed a decision today.
Two design calls shaped the whole thing.
First, one health language across every level. Critical, at risk, satisfactory. The same red, amber and green reads the same way on the full plan and on a single deliverable, so a director and a coordinator are always looking at the same signal. No translation between screens.
Second, the interface stays deliberately quiet. Neutral surface, dense layout, almost no color except the status. When everything is gray, the one red deliverable that is 18 days past deadline is the first thing your eye lands on. That is the point.
After 10+ years and 600+ projects, the pattern I keep seeing holds here too: on data-heavy tools, the job of design is subtraction. Take away everything that competes with the decision.
When you build dense dashboards, do you default to a grid of cards or a straight table? I went with both and let the user switch, but I go back and forth on which should be the default.
#productdesign #uxdesign #dashboarddesign #govtech #designsystems
Most finance dashboards dump your data and walk away.
They show you a wall of numbers and expect you to figure out what to do. That is not a product, that is a spreadsheet with better fonts.
Ledgerly took a different route. Every screen answers one question: what changed, and what do I do about it.
The decisions behind it:
One number leads. Total spent sits at the top, alone. No competing metrics fighting for attention. You know where you stand in half a second.
The insight comes before the chart, not after. "Food delivery accounted for 75% of this week's increase" is the headline. The chart just proves it. Most dashboards do the opposite and make you dig.
Every recommendation shows its reasoning. "Set a $150 delivery cap" is paired with why you are seeing it and the estimated effect. A suggestion without a reason is just noise, and people dismiss noise.
The whole thing follows one rule. Do not make the user think. Make the decision obvious, then get out of the way.
That is the difference between a dashboard that looks smart and one that actually changes behavior. Structure first, results not decoration.
If you build data heavy products, what earns more trust for you, showing everything or showing the one thing that matters?
#ProductDesign #UXDesign #FinTech #UIDesign #SaaS
Wrapped the site for Noova, a fitness app that connects people to gyms, studios and trainers in their city.
The whole page uses product UI as the visual. Real screens tilted, stacked and cropped, so the hero already shows what the app feels like.
Two typefaces only. Outfit for headings, Inter for everything else, and purple reserved for actions.
For app landing pages, do you go with real screens or custom illustration? I keep landing on real screens, but I'm curious where you sit on this.
I just designed a full fintech app, and I want to show you how it looks.
Financial UI is a digital bank built around one idea: total control of your money, without the clutter most banking apps drown you in.
Balance, cards, spending insights, transfers, security. Every screen built so the number that matters surfaces first.
The design bet: dark theme with a single green accent. Financial data needs focus, so green marks only what demands action. Nothing competes for your eye.
10+ years designing products across 12 countries taught me one thing: in fintech, clarity is the feature. People don't want a beautiful app. They want to understand their money in one glance.
Swipe through the shots and tell me: dark mode or light mode for a banking app?
Hero for an AI travel planner. Four agents watch tickets, hotels, itinerary and finances in the background.
The call I made: the headline stays short and the proof sits right under it. Instead of stacking more copy, the hero opens into the product itself — a trip in progress, real price drops, savings adding up. You scroll two inches and you already know what it does.
Warm palette on purpose. Travel sells calm, not urgency.
Finance dashboard concept. Balances, spending trends, cards and transfers in one view.
The call I made: only one number gets to be loud. Financial activity is the single card that breaks the dark layout, so the eye lands there first. Everything else sits back in the dark and waits its turn.
Green on near-black does the hierarchy work that size and weight usually have to fight for.
Ai Vou Eu — AI Travel Planner Landing Page (Figma to Framer)
One-page landing for an AI travel planner. Four AI agents track tickets, hotels, itinerary and finances while the user just relaxes.
The call I made: instead of describing the product, I showed it working.
The right side is a live-looking dashboard — trip in progress, real price drops, savings counting up. The product sells itself before the copy has to.
Figma to Framer. No dev handoff.
Studio Responsivo — Design Studio Landing PageLanding page for Studio Responsivo, a digital design studio that ships products from idea to launch with fixed pricing and a set deadline.
Case-led hero, service breakdown, transparent pricing tiers, an instant project estimator, a four-step process and client proof, structured to turn visitors into qualified leads.
Studio Responsivo builds digital structures that convert, not just decorate.
Got a project? Let's build it.
Certgon — Digital Certificate Store UI (filtering 28 near-identical SKUs)
Built this store UI for a Brazilian digital certificate provider (ICP-Brasil e-CPF / e-CNPJ).
The real problem wasn't the visual — it was navigation.
28 products that look almost the same, separated only by person type, storage method, and validity period. Dump them in a grid and the user is lost in three seconds.
The decision that mattered: I made filtering the primary structure, not an afterthought.
Three filter axes on the left (Person Type, Storage, Validity) do the heavy lifting, so each card only has to carry what actually differs — badges, price, and one line of scope.
Most people would've packed every spec into the card. I stripped the card down and let the filter carry the logic.
Result: a catalog of 28 near-identical SKUs that stays scannable.
Figma → Framer. No dev handoff.
When you've got a catalog of near-identical products, do you overload the card or lean on filters? Curious how others solve this.
600+ projects across 12 countries. 10+ years. Adobe Certified Expert & Instructor, Google UX Certified. I build Framer sites that convert.
Concept redesign of the Booking.com landing page. I moved the hero away from the search-bar-first layout and let a full-bleed photo plus a serif headline set the mood, with the search card floating over it.
Kept the palette to deep navy and one blue accent so the destination photography stays the loudest thing on screen.
When you redesign the hero of a product people know by heart, do you keep the familiar layout or break it?
A government strategic plan with 70 deliverables and dozens of owners usually lives in a spreadsheet nobody trusts.
That was the real problem behind WorkerDI, a platform for a public education body running its 2025-2026 plan. The data existed. What was missing was a way to see, in one glance, what needed a decision today.
Two design calls shaped the whole thing.
First, one health language across every level. Critical, at risk, satisfactory. The same red, amber and green reads the same way on the full plan and on a single deliverable, so a director and a coordinator are always looking at the same signal. No translation between screens.
Second, the interface stays deliberately quiet. Neutral surface, dense layout, almost no color except the status. When everything is gray, the one red deliverable that is 18 days past deadline is the first thing your eye lands on. That is the point.
After 10+ years and 600+ projects, the pattern I keep seeing holds here too: on data-heavy tools, the job of design is subtraction. Take away everything that competes with the decision.
When you build dense dashboards, do you default to a grid of cards or a straight table? I went with both and let the user switch, but I go back and forth on which should be the default.
#productdesign #uxdesign #dashboarddesign #govtech #designsystems
Most finance dashboards dump your data and walk away.
They show you a wall of numbers and expect you to figure out what to do. That is not a product, that is a spreadsheet with better fonts.
Ledgerly took a different route. Every screen answers one question: what changed, and what do I do about it.
The decisions behind it:
One number leads. Total spent sits at the top, alone. No competing metrics fighting for attention. You know where you stand in half a second.
The insight comes before the chart, not after. "Food delivery accounted for 75% of this week's increase" is the headline. The chart just proves it. Most dashboards do the opposite and make you dig.
Every recommendation shows its reasoning. "Set a $150 delivery cap" is paired with why you are seeing it and the estimated effect. A suggestion without a reason is just noise, and people dismiss noise.
The whole thing follows one rule. Do not make the user think. Make the decision obvious, then get out of the way.
That is the difference between a dashboard that looks smart and one that actually changes behavior. Structure first, results not decoration.
If you build data heavy products, what earns more trust for you, showing everything or showing the one thing that matters?
#ProductDesign #UXDesign #FinTech #UIDesign #SaaS
Wrapped the site for Noova, a fitness app that connects people to gyms, studios and trainers in their city.
The whole page uses product UI as the visual. Real screens tilted, stacked and cropped, so the hero already shows what the app feels like.
Two typefaces only. Outfit for headings, Inter for everything else, and purple reserved for actions.
For app landing pages, do you go with real screens or custom illustration? I keep landing on real screens, but I'm curious where you sit on this.
I just designed a full fintech app, and I want to show you how it looks.
Financial UI is a digital bank built around one idea: total control of your money, without the clutter most banking apps drown you in.
Balance, cards, spending insights, transfers, security. Every screen built so the number that matters surfaces first.
The design bet: dark theme with a single green accent. Financial data needs focus, so green marks only what demands action. Nothing competes for your eye.
10+ years designing products across 12 countries taught me one thing: in fintech, clarity is the feature. People don't want a beautiful app. They want to understand their money in one glance.
Swipe through the shots and tell me: dark mode or light mode for a banking app?
Hero for an AI travel planner. Four agents watch tickets, hotels, itinerary and finances in the background.
The call I made: the headline stays short and the proof sits right under it. Instead of stacking more copy, the hero opens into the product itself — a trip in progress, real price drops, savings adding up. You scroll two inches and you already know what it does.
Warm palette on purpose. Travel sells calm, not urgency.
Finance dashboard concept. Balances, spending trends, cards and transfers in one view.
The call I made: only one number gets to be loud. Financial activity is the single card that breaks the dark layout, so the eye lands there first. Everything else sits back in the dark and waits its turn.
Green on near-black does the hierarchy work that size and weight usually have to fight for.
Ai Vou Eu — AI Travel Planner Landing Page (Figma to Framer)
One-page landing for an AI travel planner. Four AI agents track tickets, hotels, itinerary and finances while the user just relaxes.
The call I made: instead of describing the product, I showed it working.
The right side is a live-looking dashboard — trip in progress, real price drops, savings counting up. The product sells itself before the copy has to.
Figma to Framer. No dev handoff.
Studio Responsivo — Design Studio Landing PageLanding page for Studio Responsivo, a digital design studio that ships products from idea to launch with fixed pricing and a set deadline.
Case-led hero, service breakdown, transparent pricing tiers, an instant project estimator, a four-step process and client proof, structured to turn visitors into qualified leads.
Studio Responsivo builds digital structures that convert, not just decorate.
Got a project? Let's build it.
Certgon — Digital Certificate Store UI (filtering 28 near-identical SKUs)
Built this store UI for a Brazilian digital certificate provider (ICP-Brasil e-CPF / e-CNPJ).
The real problem wasn't the visual — it was navigation.
28 products that look almost the same, separated only by person type, storage method, and validity period. Dump them in a grid and the user is lost in three seconds.
The decision that mattered: I made filtering the primary structure, not an afterthought.
Three filter axes on the left (Person Type, Storage, Validity) do the heavy lifting, so each card only has to carry what actually differs — badges, price, and one line of scope.
Most people would've packed every spec into the card. I stripped the card down and let the filter carry the logic.
Result: a catalog of 28 near-identical SKUs that stays scannable.
Figma → Framer. No dev handoff.
When you've got a catalog of near-identical products, do you overload the card or lean on filters? Curious how others solve this.
Concept redesign of the Booking.com landing page. I moved the hero away from the search-bar-first layout and let a full-bleed photo plus a serif headline set the mood, with the search card floating over it.
Kept the palette to deep navy and one blue accent so the destination photography stays the loudest thing on screen.
When you redesign the hero of a product people know by heart, do you keep the familiar layout or break it?
A government strategic plan with 70 deliverables and dozens of owners usually lives in a spreadsheet nobody trusts.
That was the real problem behind WorkerDI, a platform for a public education body running its 2025-2026 plan. The data existed. What was missing was a way to see, in one glance, what needed a decision today.
Two design calls shaped the whole thing.
First, one health language across every level. Critical, at risk, satisfactory. The same red, amber and green reads the same way on the full plan and on a single deliverable, so a director and a coordinator are always looking at the same signal. No translation between screens.
Second, the interface stays deliberately quiet. Neutral surface, dense layout, almost no color except the status. When everything is gray, the one red deliverable that is 18 days past deadline is the first thing your eye lands on. That is the point.
After 10+ years and 600+ projects, the pattern I keep seeing holds here too: on data-heavy tools, the job of design is subtraction. Take away everything that competes with the decision.
When you build dense dashboards, do you default to a grid of cards or a straight table? I went with both and let the user switch, but I go back and forth on which should be the default.
#productdesign #uxdesign #dashboarddesign #govtech #designsystems
Most finance dashboards dump your data and walk away.
They show you a wall of numbers and expect you to figure out what to do. That is not a product, that is a spreadsheet with better fonts.
Ledgerly took a different route. Every screen answers one question: what changed, and what do I do about it.
The decisions behind it:
One number leads. Total spent sits at the top, alone. No competing metrics fighting for attention. You know where you stand in half a second.
The insight comes before the chart, not after. "Food delivery accounted for 75% of this week's increase" is the headline. The chart just proves it. Most dashboards do the opposite and make you dig.
Every recommendation shows its reasoning. "Set a $150 delivery cap" is paired with why you are seeing it and the estimated effect. A suggestion without a reason is just noise, and people dismiss noise.
The whole thing follows one rule. Do not make the user think. Make the decision obvious, then get out of the way.
That is the difference between a dashboard that looks smart and one that actually changes behavior. Structure first, results not decoration.
If you build data heavy products, what earns more trust for you, showing everything or showing the one thing that matters?
#ProductDesign #UXDesign #FinTech #UIDesign #SaaS
Wrapped the site for Noova, a fitness app that connects people to gyms, studios and trainers in their city.
The whole page uses product UI as the visual. Real screens tilted, stacked and cropped, so the hero already shows what the app feels like.
Two typefaces only. Outfit for headings, Inter for everything else, and purple reserved for actions.
For app landing pages, do you go with real screens or custom illustration? I keep landing on real screens, but I'm curious where you sit on this.
I just designed a full fintech app, and I want to show you how it looks.
Financial UI is a digital bank built around one idea: total control of your money, without the clutter most banking apps drown you in.
Balance, cards, spending insights, transfers, security. Every screen built so the number that matters surfaces first.
The design bet: dark theme with a single green accent. Financial data needs focus, so green marks only what demands action. Nothing competes for your eye.
10+ years designing products across 12 countries taught me one thing: in fintech, clarity is the feature. People don't want a beautiful app. They want to understand their money in one glance.
Swipe through the shots and tell me: dark mode or light mode for a banking app?
Hero for an AI travel planner. Four agents watch tickets, hotels, itinerary and finances in the background.
The call I made: the headline stays short and the proof sits right under it. Instead of stacking more copy, the hero opens into the product itself — a trip in progress, real price drops, savings adding up. You scroll two inches and you already know what it does.
Warm palette on purpose. Travel sells calm, not urgency.
Finance dashboard concept. Balances, spending trends, cards and transfers in one view.
The call I made: only one number gets to be loud. Financial activity is the single card that breaks the dark layout, so the eye lands there first. Everything else sits back in the dark and waits its turn.
Green on near-black does the hierarchy work that size and weight usually have to fight for.
Ai Vou Eu — AI Travel Planner Landing Page (Figma to Framer)
One-page landing for an AI travel planner. Four AI agents track tickets, hotels, itinerary and finances while the user just relaxes.
The call I made: instead of describing the product, I showed it working.
The right side is a live-looking dashboard — trip in progress, real price drops, savings counting up. The product sells itself before the copy has to.
Figma to Framer. No dev handoff.
Studio Responsivo — Design Studio Landing PageLanding page for Studio Responsivo, a digital design studio that ships products from idea to launch with fixed pricing and a set deadline.
Case-led hero, service breakdown, transparent pricing tiers, an instant project estimator, a four-step process and client proof, structured to turn visitors into qualified leads.
Studio Responsivo builds digital structures that convert, not just decorate.
Got a project? Let's build it.
Certgon — Digital Certificate Store UI (filtering 28 near-identical SKUs)
Built this store UI for a Brazilian digital certificate provider (ICP-Brasil e-CPF / e-CNPJ).
The real problem wasn't the visual — it was navigation.
28 products that look almost the same, separated only by person type, storage method, and validity period. Dump them in a grid and the user is lost in three seconds.
The decision that mattered: I made filtering the primary structure, not an afterthought.
Three filter axes on the left (Person Type, Storage, Validity) do the heavy lifting, so each card only has to carry what actually differs — badges, price, and one line of scope.
Most people would've packed every spec into the card. I stripped the card down and let the filter carry the logic.
Result: a catalog of 28 near-identical SKUs that stays scannable.
Figma → Framer. No dev handoff.
When you've got a catalog of near-identical products, do you overload the card or lean on filters? Curious how others solve this.
