It would, for a national operator, make significant sense to have a central development team that can handle things like this - I've seen the SBB app and the difference between it, and UK apps, is like night and day. I'd give my right arm for systems of SBB's quality some days!
(One more for the GBR list...!) Unfortunately, with the fragmented nature of the UK rail and the "plan to the next election" approach of government, there's no business case for each business having a team of developers building different systems to do the same job (which ends up having its own issues, like business intelligence shortfalls because the people who work on it end up being enthusiastic amateurs like me).
It still is at least three of those things!
I agree that it's not ideal, but at what point do we draw a line? If EMR operated it directly, they might well have chosen the same hours. There comes a point at which the cost of providing the service outweighs the benefit - every member of staff you employ adds c.£50k to the bill, and while an 18-hours-a-day, 7-days-a-week service like SNCF would be ideal, that comes at the expense of something else to fund the 4 members of staff, one manager, and any property costs that come with it, per operator. It's a typical business balancing act that GBR should be in an ideal position to fix, really (with my most optimistic hat on). Worth noting that Heathrow lost property 0900-1600, Monday to Saturday. Gatwick too is 0900-1600, Monday to Friday - and these are arguably far more 24-hour operations that St Pancras.
Whilst that is an example of excellent service, there's rather a significant difference between the tube and heavy rail that means something like this is a lot easier to do on the tube even today.