A summary of design & development activity and KPIs for the OpCo product team in January 2025.
Staff update
I’m sorry to say that I will be moving on to a new opportunity. My last day at Balancer OpCo will be the 21st of Feb. Alberto will be stepping up to lead the frontend team. I will do all I can to support him in this transition. I know Alberto will be a fantastic team lead and I can leave knowing that the team and the app are in good hands.
Coincidentally, Anastas, our other frontend developer is also leaving, with the same end date as myself, the 21st of Feb. As a result, we have kicked off a hiring process so that Alberto can rebuild the team. He is looking to hire 1-2 new senior frontend developers as soon as possible.
Development
Our primary focus in January was to monitor and fix any issues that came up from the launch of v3 in December. We also took this time between major features to work on DX improvements and high-priority refactors in our backlog.
106 PRs were merged on the frontend monorepo in January. For a more detailed breakdown of work done, browse our merged PRs.
Design
Below is a high-level list of design activity in January:
- Main focus was UI/UX for the new zen-themed LBP experience. These designs have been reviewed and is now ready for implementation.
- Includes LBP simulation and creation
- Updates across the site, especially on the pool detail page with new sections and charts. Includes states for pre, during and post LBP.
- Mobile experience
- Launch of new hooks
- Promo banners for the new hooks coming soon: MEV Capture and StableSurge.
- Minor updates to support these hooks, like adding MEV captured into APR popovers.
- veBAL improvements
- New designs for veBAL voting previews and handling edge cases, like enabling the user to vote on more than 8 gauges at a time.
- Testing the new work-in-progess implementation + suggesting fixes
- Gyroscope improvements
- UI design of a new Liquidity Profile chart which shows when concentrated liquidity pools are in range vs out of range. Plus warnings in Add Liquidity flow if the pool is out of range.
KPIs
NPS
Our NPS score from submissions in January was 70.
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.”.
The above image shows how our NPS score has changed over the last 3 months. As can be seen in the trend chart, in January, our NPS score recovered to a norm of approximately 60 after an unexpected drop in December. We put the drop in December down to the launch of v3 and the influx of new visitors that came to the app for the first time.
We have fixed an issue we had with the NPS score feedback form which was preventing us from receiving written feedback with the score. Now that this has been fixed we should be able to gain a better understanding of the feedback submissions we are getting.
Error-free transaction flow rate
Regarding the error-free transaction flow rate that we reported for the v2 app, we are still working on our Sentry error-tracking integration to clean up the data so that the number we report is accurate and relatable to the previously reported figures.
An intermediate transaction flow KPI is the ratio of transactions triggered vs successful that we track via our analytics events. For January we had:
- 27,967 transaction triggered events
- 25,965 successful transaction events
That gives us a 92.8% transaction submission success rate.
We have seen a slight decrease in this rate since we launched v3 in December. This is due to increased edge-case failures in v3 pool transaction flows. We are working through these issues and I’d expect the rate to increase back to ~95% over the next few months.