Give different financial journeys one coherent product language.
Lead UX/UI & visual designer
Product UX · Rebrand · Responsive UI
Design case study
Original AUXO interface · Selected from the published case
The original identity extends from a moving mark to a dimensional token presentation. These are brand explorations from the published case.
A newcomer, an active governor and an existing holder do not arrive with the same question. The product transition needed to serve those different intentions while becoming recognizable as AUXO.
I led UX/UI and visual design through the PieDAO-to-AUXO evolution, covering user groups, journeys, information architecture, interface patterns and the brand family.
Evolve an existing financial product while keeping its participation routes and terminology understandable.
Inside the original workFive audience groups, a sitemap, wallet-access and recovery flows, an end-to-end journey, a component library and desktop/mobile application views.
The original research board connects each group to a problem, a feature set and a route through the product. That distinction matters: learning, holding and governing are different jobs.
Wants to learn and invest, but does not yet understand the vocabulary or the first step.
Give learning its own route. The original map calls for an explanatory landing page, basic knowledge, documentation and a first-purchase walkthrough.
Already holds DOUGH and wants to understand the DAO, its advantages and how to take a more active role.
Connect product education with participation: governance benefits, governing tools, documentation and the treasury appear together in the audience map.
Needs to track investments, stay aware of relevant changes and participate in governance and the community.
Prioritize a direct route to the portfolio and governance. The source also calls out investment tools, community and retention ideas.
Owns products and wants to follow investments and changes, without necessarily being active in governance.
Make the portfolio useful on its own. Product explanations and news support ongoing ownership without requiring the person to become a governor.
Knows the crypto market and wants detailed information, confidence in the team and a clear reason to invest.
Support deeper evaluation. The audience board names investment and governance tools, liquidity, portfolio information and exclusive advantages.
Summarized from the original audience board. PieDAO, DOUGH and PIEs are the product names used at this stage of the work.
A closer reading of the original work: the problem each choice addresses and the value it is intended to create.
The research distinguishes newcomers, potential governors, active governors, product holders and investors.
Connect each route to a different job: learn, inspect a position, evaluate participation or govern.
Make navigation respond to intent instead of assuming everyone understands the system.
The original wallet flow branches for the wrong network, missing wallets and failed access.
Map network switching, installation, rechecking and an explicit reporting or exit route.
Give a blocked participant a next step that can be reflected in interface states.
The architecture retains legacy PieDAO/DOUGH concepts while the new interface introduces AUXO.
Carry the product relationships into shared navigation, summaries, cards and action patterns.
Give returning users a coherent structure as the product expression changes.
The library covers inputs, buttons, charts, financial cards and related AUXO/ARV/PRV identities.
Define the system around reusable behavior as well as visual style, then apply it on desktop and mobile.
Support a recognizable experience across financial tasks and screen sizes.
The original documents move from product structure to access, actions and recovery. These details show how I approached the experience before the final interface.
The sitemap separates learning, product exploration and governance. It also maps what lives inside each area: indices, exchange, deposits and withdrawals, farms, the portfolio and staking.
Why this mattersA holder looking for a position and a newcomer looking for an explanation need different routes through the same product.
The flow considers more than a successful connection. It asks whether a wallet exists, whether the network is correct and what should happen when access fails.
The UX decisionTreat access as a recoverable sequence, with states that can be carried into implementation.
The end-to-end map separates “discover and learn” from “invest and govern.” Public explanations lead into product detail, while wallet access sits at the point where someone chooses to act.
Landing page, learning resources and product information.
Understand the product, staking or governance before connecting.
Move into the dashboard, product actions and governance tools.
These are original planning artifacts, shown without redrawing. They document the design process; they do not establish that every mapped branch shipped or that a particular conversion improvement was measured.
A closer look at the application and the patterns that hold its different tasks together.
A compact overview combines holdings, strategy information, allocation and a detailed asset table.
The staking workflow exposes product context, a reward explanation, amount control and the current position.
Rewards summaries, history and a bar chart connect present state with performance over time.
The complete originals behind this case study. Open a board to inspect the source presentation.
A connected product and identity system spanning research artifacts, architecture, components, desktop, mobile and marketing expression.
A strong brand can help recognition, but product terminology still needs explanation. Visual consistency should support the financial information rather than compete with it.
Original research and design artifacts establish the work. Platform scale is not a measured result of the redesign.
These explanations and presentation layouts are newly prepared from the available original artifacts. The validation tasks are proposals, not research already completed.
Screens and process artifacts come from the original published project. Product amounts shown inside the designs are interface content, not claims about current assets or business performance.
Practical AI, right where the work happens.