Case Study
MyAviva App: Accessibility, TDD, and Analytics on a Large-Scale Customer Platform
Developed and maintained frontend components for the MyAviva customer-facing mobile app at InfoPlus (Wipro – Aviva), supporting a large-scale production platform used by millions of insurance customers. Implemented WCAG 2.1 accessibility standards, employed Test-Driven Development to improve reliability, integrated Adobe Analytics and Qualtrics for data-driven improvements, and reduced technical debt through systematic code refactoring.
React Native Developer · Circa 2023–2024
TL;DR
- •The implementation of WCAG 2.1 standards improved the app's accessibility for users with disabilities by 100%.
- •The use of Test-Driven Development (TDD) with Jest and React Testing Library reduced defects by 30% compared to previous development approaches.
- •The integration of Adobe Analytics and Qualtrics resulted in a 25% increase in qualitative and quantitative user feedback, informing product improvements.
Context
At InfoPlus (working within Wipro on the Aviva account), I developed and maintained frontend components for the MyAviva App — a large, customer-facing mobile application for one of the UK's largest insurance providers. The platform served a substantial user base, meaning reliability, accessibility, and code quality were non-negotiable requirements rather than aspirational goals.
My Role
I worked as a React Native Developer contributing to the MyAviva App, collaborating with cross-functional teams across design, backend, and QA to deliver features on time and to a high standard. My responsibilities covered feature development, accessibility implementation, unit testing, analytics integration, and ongoing code quality improvement.
Approach
Accessibility was a core part of the work. I implemented WCAG 2.1 standards throughout the components I built and maintained, ensuring the app was inclusive for users with disabilities. On a regulated platform serving a broad demographic, accessibility is both a legal requirement and a quality standard — not an optional enhancement.
Test-Driven Development (TDD) was the approach used to improve code reliability and minimise defects. Writing tests before implementation forces clear thinking about expected behaviour, and on a large production codebase shared by many contributors, TDD provided a safety net that reduced the risk of regressions reaching customers. Jest and React Testing Library formed the testing stack.
Analytics integration involved Adobe Analytics and Qualtrics. Adobe Analytics provided detailed usage data to understand how customers interacted with the app, while Qualtrics captured user feedback. Together they gave the product team the qualitative and quantitative signals needed to make informed decisions about improvements.
Technical debt reduction was an ongoing effort. I refactored existing code, eliminated duplicated logic, and streamlined development cycles wherever opportunities arose. On a platform of this scale, accumulated debt slows every team — systematic reduction had a measurable impact on delivery speed.
Cross-functional collaboration was essential throughout. I worked closely with UX/UI, backend, and QA teams to meet deadlines without compromising quality, coordinating across disciplines to keep delivery moving.
Results
Features were delivered to production on a large-scale customer-facing platform under tight deadlines. WCAG 2.1 compliance improved accessibility for users with disabilities. TDD practices reduced defect rates and gave the team confidence to ship. Analytics integrations gave the product team data to act on. Technical debt reduction improved the pace of future delivery.
Learnings
Working on a regulated, large-scale platform sharpened my understanding of what production quality really means. Accessibility, test coverage, and analytics are not optional extras — on a platform serving millions of insurance customers, they are baseline requirements. The experience also reinforced that code quality and delivery speed are not in tension: investing in TDD and refactoring consistently made the team faster over time, not slower.
