When we first worked with IMS, their apps were broadly stable. Their internal development team had already invested heavily in maintaining and testing the platform. The challenge wasn’t poor engineering standards. It was that their existing testing approach couldn’t fully replicate real-world mobile behaviour at scale.
In sectors like insurance and telematics, strong testing is crucial. The data generated through an app like IMS influences pricing decisions, claims assessments, driver risk analysis and, in some cases, legal disputes. If organisations can’t fully trust the quality and consistency of that data across devices and operating conditions, confidence in the wider platform starts to weaken too.
A large proportion of their testing had been carried out through emulators, supported by manual testing. That’s a common setup, but emulator testing can only go so far when you’re validating telematics performance across large numbers of physical devices and operating conditions.
In IMS’s case, tracking accuracy varied across devices, background behaviours became inconsistent in certain scenarios, and Android fragmentation created uncertainty around edge-case performance.
To address this, we introduced our Mobile Assurance Programme, or MAP.
Rather than slowing releases down with excessive testing layers, MAP creates structured, repeatable validation processes around real-world mobile behaviour. For IMS, that started with understanding which devices their customers were actually using and building testing environments around those conditions.
We then ran controlled comparative tests across multiple devices simultaneously, recreating identical journeys and behaviours to identify inconsistencies in how telematics data was being captured and interpreted.
Once the optimal setup had been established, we created structured testing scripts and workflows that IMS could continue using internally. We also integrated reporting directly into their existing development workflows so issues could be prioritised and resolved quickly.
Within the first three months of working together, we identified 93 easily fixable issues that previous testing approaches had missed.
Addressing those issues gave IMS significantly more confidence in the reliability of the telematics data their apps were generating. That allowed the business to continue evolving the platform as a scalable alternative to traditional telematics hardware, while also improving areas like battery management, long-term maintenance and app store compliance.
In our experience, this is where many app-owning businesses struggle. The issue often isn’t that the app is visibly failing. It’s that teams no longer have complete confidence in how the platform behaves across real-world conditions, devices and operating system changes.
That uncertainty makes it harder to evolve products confidently over time.
What businesses usually need at that point isn’t a complete rebuild. They need clearer visibility into how their existing systems are performing, where reliability risks exist, and what practical improvements can strengthen confidence without disrupting the wider operation.
If that sounds familiar, book a discovery call with Indiespring to explore how your app is performing. We’ll validate how it works in real-world conditions, and reveal where your hidden reliability risks exist for a clearer path forward.