OpCo Product Team - May 2024 Update

A summary of design & development activity and KPIs for the OpCo product team in May 2024.

The V3 (Zen) UI is currently in beta testing. If you are interested in testing our new UI please reach out to gareth@balancer.finance.


In May our primary goal was to get the app ready for testing and kick off a beta testing program within the Balancer ecosystem. We launched this beta program on the 27th of May and it has been a huge success so far.

Again, in May as in April, our focus has been on preparing the V3 (Zen) app for production. This focus essentially comes down to ensuring that all the transaction flows work as expected and the UI reflects changes to the user’s positions as they perform those actions, e.g. add, remove, stake, unstake, etc.

Some more significant changes/improvements to the app were:

  • A min TVL filter for pools.
  • Migration to the wagmi v2 package.
  • Addable pool token helper functionality.
  • Pool detail page redesign.
  • A refactor of how we handle transaction steps.
  • Fixed mainnet claiming.

We have also continued to maintain v2 and support changes there where required.


Below is a high-level list of design activity in May:

  • User testing
    • 3 formal user testing sessions
    • Design iterations based on feedback trends
  • UX/UI and copywriting for v3 app
    • Improved yield breakdown popovers which better explain where pool yield comes from.
    • Design system for partner pool pages, allowing some theme and image customization (not live yet)
    • Improvements to the Pool Detail page, like a new design to include recent transactions (not live yet)
    • Addable tokens in Add Liquidity flow: UX improvements
    • Pool warnings on Pool Page
    • Explorations around a price impact visualization
    • Frontend development for v3 app
    • Featured pool section: Reduced the height of the module by replacing the two row layout with a single row.
    • Select a token module in the swap flow: various UI improvements
    • Yield breakdown tooltip: Layout adjustments and new tooltips.
    • Updated pool risks: New section on CLPs
  • Marketing
    • Wireframes and work-in-progress copy for the new landing pages


= 1 - (‘fatal’ errors / total successful txs)

Where ‘fatal’ is a label applied to errors recorded in a transaction flow, and total successful txs are recorded via analytics events.


  • Ad blockers prevent error recording and analytics.
  • Some % errors are user/wallet-controlled errors we haven’t excluded yet.
  • Total fatal errors: ~6,856 (prev. 6,184)
  • Total successful txs: ~99,406 (prev. 89,112)

This KPI has increased slightly since last reported in April at 93.0%. We have not completed any work to fix issues in v2 in April so this can only be attributed to changed network or user conditions.

Note that our primary focus is on the v3 (Zen) app development. When critical errors come up that can be fixed we will do this ASAP. The errors we are seeing that prevent us from reaching 100% error-free rate are often non-trivial to replicate and fix.

Avg. time on site (30d): 2:03 (+0.13s)

Note, that the Average Time on Site metric can be influenced by market conditions. For instance, we observe an increase in time spent on the site when the market is on the rise.

Taken from this article about what makes a good NPS score: “If your NPS is higher than 30, that would indicate that your company is doing great and has far more happy customers than unhappy ones.”.

As can be seen in the general trend chart above, the NPS score has remained fairly constant at around the 50-60 level which is very good.