A summary of design & development activity and KPIs for the OpCo product team in August 2024.
Development
We launched CoW AMM support on August 8th. The launch was a huge success for the ecosystem.
The first week in August was a sprint to prepare the UI for the CoW AMM launch. Following that there has been additional work to make improvements and fix bugs.
Following the CoW work we have kicked off the veBAL migration project. That is, we are redesigning and implementing the veBAL functionality in the new UI. veBAL is a very large feature so this is likely to take some time and be implemented in stages, e.g. veBAL management, cross-chain syncing and voting.
In addition, we worked on many smaller improvements and bug fixes, such as:
- Improvements to Safe app support.
- Improved error handling.
- Pool activity table.
- Fixes for forced proportional adds (to be completed).
- Fixes for pools that support nested actions (to be completed).
Finally, we spent some time preparing the v2 app and API for deprecation.
Design
Below is a high-level list of design activity in August:
- UI/UX design
- Designed the much-requested table view for the Pool Activity chart section (live)
- Started a new workstream for the zen veBAL experience, including research and initial designs (not live)
- Initial designs for a swap route visualization, using a Sankey chart style (not live)
- Designed and created a ticket to Aura as an option to display when the user taps the ‘Stake’ button on the Pool Details page (not live)
- Designed and created a ticket to add token colors for the Pool composition charts (not live)
- Frontend development for web app
- CoW theming and cleans up, including new promotional banner
- Smarter Nav bar which appears on upwards scroll
- Smooth fade-in animation on pools list table rows while scrolling downwards
- Removed layout shift jank when using filters on the Pools List table
- UI improvements to the Portfolio page, including loading animation sequence
- UI improvements for the new table view for the Pool Activity section
KPIs
KPIs will be reported again once we have fully transitioned to the new app and have the appropriate data in place.
We have started receiving NPS scores and they are looking very promising, but until we start directing all traffic from the old app to the new app and have at least 3 months worth of data this score can be misleading.
Regarding the error-free transaction flow rate that we used to report 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. This is a slightly complex task because we are tracking errors in transaction flows in a different way than we were before.