The app may have been live for years. Different teams have shaped it over time. Some architectural decisions were made in a different commercial climate. It performs well most of the time and, from the outside, everything appears steady. Revenue flows. Users rely on it. Delivery continues.
The truth is, you need clarity before you can do anything - whether your team is big or small. A “problem app” usually gets labelled as a technical issue. Legacy code, fragile infrastructure, missing documentation... sometimes all of these things are at play, sometimes it's just one issue.
Operators are being asked to do more with less. Costs are rising, and passenger expectations are becoming shaped by seamless digital experiences in other sectors. Regulatory requirements continue to evolve, and frankly most of the internal teams we’ve spoken to are feeling stretched.
“With older application frameworks using lots of plugins, an SDK update can have a significant impact on app stability, how do we manage this?"
In reality, small weaknesses at the bus door shape revenue, cost and behaviour every day. When validation is slow, unclear or easy to bypass, the impact doesn’t show up as a single failure. It shows up as a thousand small compromises.
We all know the pain of a poor app review, and it’s a heavy one. Rectifying the problem can cost time, stall releases, drain internal resources, damage user trust, and (as if that wasn’t enough) risk revenue.
