Adding the “Strategies Inside” Block
Problem
Strategies are aggregated products where yield is formed from multiple underlying strategies. Previously, users only saw the overall APY and didn’t understand which assets and protocols contributed. Users could not assess the reliability, transparency, or mechanics of a strategy, which created distrust and made decision-making difficult.
Task
Add a “Strategies Inside” block to the strategy interface to show which protocols are included in the yield-generating strategy, with the option to explore each in detail.
Result
The new block improved understanding of aggregated strategies, increased user engagement and trust, and allowed users to compare strategies not only by total yield but also by composition and underlying logic.
Strategy Updates
Problem
The platform regularly updated strategies: new protocols appeared, and yield conditions changed. Users had no way to see these changes directly in the interface, reducing transparency and engagement. To understand updates, they had to check the blog or external sources.
Task
Design a compact, unobtrusive updates block integrated into the strategy interface.
Result
Developed a compact updates block embedded in the strategy interface, giving users a clear simple way to track changes.
Once the wireframes were approved, I began developing the UI, incorporating designer feedback throughout the process, and created all screen variations for both desktop and mobile devices.
After the competitive analysis, I created wireframes for the future blog and iterated on them based on feedback from the lead designer and analyst. We explored different ways to display the article catalog—using backgrounds, icons, and varying tag hierarchies—and ultimately chose a simplified version.
Workflow
Started with a call with the lead designer to clarify requirements and context.
Problem
The blog was hosted on an external platform, which limited analytics, separated it from the main product, and reduced user engagement. The team decided to migrate it to the company website to gain control over content and establish a unified style.
Solution
Design a blog integrated into the main product structure.
Result
The new blog increased time on site by 18.7% and page depth by 9.3%.
Created a UI kit documenting component behavior, which sped up the design handoff and reduced developer questions and revisions.
Created a UI kit documenting component behavior, which sped up the design handoff and reduced developer questions and revisions.
My Role
Designed the interface under the lead designer’s guidance, conducted competitive analysis, participated in design reviews, prepared components for development handoff, and collaborated closely with the team.
Rivo
Smart contract wallet and DeFi strategy aggregator
Strategy Updates
Problem
The platform regularly updated strategies: new protocols appeared, and yield conditions changed. Users had no way to see these changes directly in the interface, reducing transparency and engagement. To understand updates, they had to check the blog or external sources.
Task
Design a compact, unobtrusive updates block integrated into the strategy interface.
Result
Developed a compact updates block embedded in the strategy interface, giving users a clear and simple way to track changes.
Adding the “Strategies Inside” Block
Problem
Strategies are aggregated products where yield is formed from multiple underlying strategies. Previously, users only saw the overall APY and didn’t understand which assets and protocols contributed. Users could not assess the reliability, transparency, or mechanics of a strategy, which created distrust and made decision-making difficult.
Task
Add a “Strategies Inside” block to the strategy interface to show which protocols are included in the yield-generating strategy, with the option to explore each in detail.
Result
The new block improved understanding of aggregated strategies, increased user engagement and trust, and allowed users to compare strategies not only by total yield but also by composition and underlying logic.
Once the wireframes were approved, I began developing the UI, incorporating designer feedback throughout the process, and created all screen variations for both desktop and mobile devices.
After the competitive analysis, I created wireframes for the future blog and iterated on them based on feedback from the lead designer and analyst. We explored different ways to display the article catalog—using backgrounds, icons, and varying tag hierarchies—and ultimately chose a simplified version.
Workflow
Started with a call with the lead designer to clarify requirements and context.
Problem
The blog was hosted on an external platform, which limited analytics, separated it from the main product, and reduced user engagement. The team decided to migrate it to the company website to gain control over content and establish a unified style.
Solution
Design a blog integrated into the main product structure.
Result
The new blog increased time on site by 18.7% and page depth by 9.3%.
Created a UI kit documenting component behavior, which sped up the design handoff and reduced developer questions and revisions.
Created a UI kit documenting component behavior, which sped up the design handoff and reduced developer questions and revisions.
My Role
Designed the interface under the lead designer’s guidance, conducted competitive analysis, participated in design reviews, prepared components for development handoff, and collaborated closely with the team.
Rivo
Smart contract wallet and DeFi strategy aggregator