A summary of design & development activity and KPIs for the OpCo product team in December 2024.
Development
Our primary focus in December was the final preparation for the v3 launch on the 11th of December. This mainly involved QA testing, fixes, small improvements and getting the landing page ready for launch.
On the 11th of December, we launched v3 UI support alongside the ecosystem-wide launch of v3. It was a great success and everything went as smoothly as possible from a frontend perspective. I want to take the opportunity to give kudos to Alberto who generally led the v3 development effort, in particular all the work around supporting v3 pools for adds, removes and swaps.
In the second half of December, most of our team was on paid leave for the Christmas holidays.
108 PRs were merged on the frontend monorepo in December. For a more detailed breakdown of work done, browse our merged PRs.
Design
Below is a high-level list of design activity in October:
- UI/UX explorations of new app header section
- Incorporates high level value proposition of the app and protocol stats above any promo banners.
- UI/UX of new third party protocol promotion section under the main Pool List table that aligns with the styles of the new landing page.
- UI/UX improvements to the upcoming new veBAL experience.
KPIs
NPS
Our NPS score from submissions in December was 46.
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 above, in December, our NPS score dropped from above 60 for the first time. We put this down to the launch of v3 and the influx of new visitors that came to the app for the first time.
Sone things to consider when trying to understand this score:
- We only had 15 submissions in December, so even a couple of negative submissions can have a big impact on the score.
- We have an issue where our new UI component library blocks users from providing written feedback in the widget, this needs to be investigated and an alternative solution put in place when we have the capacity. This UX issue may actually cause users to provider a lower score.
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 December we had:
- 32,876 transaction triggered events
- 30,629 successful transaction events
That gives us a 93.1% transaction submission success rate.