Home
About us
Solutions
Case studies
News
Case study · Banking
NPL field agents app
Two applications for one process.
One application for web and mobile.
Banking group · NPL debt recovery · Progressive Web App · Angular
Diagram of the work: the two original applications and the Progressive Web App that unifies them.
The need
Two applications to maintain for one process.
The bank ran two applications for its debt recovery process: an Android app for the external agents and a web portal for the NPL recovery firms. Because the features partly overlapped, development and maintenance were done twice. Both had security weaknesses and an application structure that was hard to maintain. When the original supplier’s support ended, the system had to be redesigned.
Everything done twice
Features present on both platforms needed separate work for every update and every fix, which doubled the effort of keeping them alive.
Security to bring up to standard
The security weaknesses called for work on the application architecture, and for a more consistent way of meeting the bank’s security requirements.
An architecture hard to maintain
The way the applications were built made both fixes and new features complicated.
The original supplier’s support ending
With the original supplier’s support ending, the bank needed a new solution it could build and maintain.
What we did
From two applications to one PWA.
Add Value built an Angular Progressive Web App that brings together the features of the two previous applications. It is reachable from a browser and from mobile devices, and follows the bank’s own architecture standards and security models.
The project in full
Building one application for web and mobile.
Add Value built an Angular Progressive Web App bringing together the features of the existing Android app and web portal. It is reachable from a browser and from mobile devices, and follows the bank’s architecture standards and security models. The work ran in weekly sprints, with inputs and outputs agreed in advance, interfaces prototyped in Figma and the end users brought in progressively. Front end and back end were built in parallel.
AGENTI NPL is a new application base for third-party debt recovery. The features of the previous solutions were rationalised and the back end re-engineered, reusing existing logic and components where possible. The structure was prepared for the system to keep growing.
The method
A development process built on weekly sprints.
The project ran in weekly sprints, with the technical teams, architecture and end users working together throughout. Each cycle agreed the work, checked the result and gathered what was needed for the next one.
Planning
Inputs and outputs agreed
Before each sprint the inputs, the expected outputs and the scope are agreed, so the work fits into weekly cycles.
Interface
Interfaces prototyped
The interfaces are built in Figma and shared with the end users, to gather comments and validate the screens before development starts.
Build
Front end and back end built in parallel
Front end and back end are built in parallel. The back end was re-engineered, reusing existing logic and components where possible.
Check
Users involved during development
The end users take part in the checks through the sprints, which surfaces feedback and any drift before final testing.
The result
One application, ready to grow.
The project replaced the two previous applications with one Progressive Web App, which stopped the duplicated development and maintenance. The new architecture gives a base that is easier to maintain and extend, on which to carry over the remaining features and add new signing methods.
One application to build, maintain and update
Browser and mobile access through a single application
An architecture following the bank’s own standards and security models
A base ready for the remaining features and for new signing methods
A development process built on weekly sprints and continuous validation
The project also kept the technical teams, architecture and end users working together, through weekly sprints and progressive checks.
Inside the project
One application, three audiences.
The new application answers the people involved in the process: the external agents, the recovery firms, and the bank’s IT and security functions.
One application for web and mobile
The external agents used to have a dedicated Android app. With the new Progressive Web App they reach the same application from mobile devices and from a browser, with no separate platform.
- One Progressive Web App for web and mobile
- Interfaces checked through Figma prototypes
- New signing methods on the roadmap
Features for third-party debt recovery
The new application brings together what the NPL recovery firms and the external agents used. It starts from third-party debt recovery, rationalising the functions that were split between the web portal and the Android app.
- Both applications’ features analysed and rationalised
- The remaining features carried over progressively
- One application for everyone involved in the process
Aligned to the architecture and security standards
The Progressive Web App was built to the architecture standards and security models the bank already uses, and fits into the existing technology estate.
- The bank’s own security models applied
- The weaknesses of the previous applications resolved
- Back end re-engineered to be easier to maintain
Technologies and areas
Keep reading
Other stories
Insurance · Software
Regression testing
An automated testing service running since 2019, first with UFT and then with Playwright, to check that new features do not break the existing ones.
+3,700 automated tests
The full caseBanking · Software
Exchange Digital Corporate
The Corporate Banking flow backbone was rebuilt and run in parallel with the old system, handling around 1.5 million flows a day.
from 10 minutes to under 1
The full caseInsurance · Software
API Management middleware
A custom .NET API Manager with a two-way orchestrator and ELK monitoring, for near real-time policy issuing, 24/7.
+20% performance
The full caseInsurance · Software
Life AM
Running and maintaining the life insurance software: corrective and evolutionary work, plus the one-off requests.
97% SLAs met
The full caseIndustrial · Data
From on-premise to ROSA
The OpenShift environment migrated to Red Hat OpenShift Service on AWS, with automated pipelines, Infrastructure as Code and health checks on the critical components.
migrated in about 3 months
The full caseBanking · Software
Corporate Remote Banking
A multi-bank, multi-company platform with a modern interface and a microservices back-end, built for a technology provider to financial institutions.
0 outages
The full caseBanking · Data
Data migration machine
Automates diagnostics, normalisation and transfer of the data needed to migrate NPL portfolios and support later acquisitions.
~350 transformations · 10 verticals
The full case