Adam Williams
Established Member
To be fair, you could quite easily have the original retailer encrypt the photo per railcard and store each railcard's photo decryption key in the railcard barcode.If it's encrypted then the decryption key needs to be somewhere. If it's known by rail staff, then it just takes one bent staff member to leak it. It can't be online because there isn't consistent coverage on trains. And if it's stored on the device it's as good as useless if the device is lost.
I think calling them "non-excuses" is cynical and unreasonable. These are massive practical challenges, costs, and risks for the railway to deal with, for the very low payoff of allowing Railcard holders, who already have multiple ways to store and display their Railcards, a different way of low to no additional convenience.
I think my own view is somewhere in the middle here. @Watershed does have a point in that the priority would not really appear to be customer convenience / user experience in this area, at present. Do passengers really want to download another app for everything? I'm inclined to think that allowing them to be stored in a wallet doesn't present insurmountable challenges, but you'd need to handle the whole concept very carefully. If you wanted truly offline validation support, you'd need to take steps to ensure passengers who had just purchased a railcard were not penalised.
Agreed.if the railway's technology fails to deliver the photo at time of scanning, then it should give the benefit of the doubt
To be honest, I agree with @Bletchleyite here. You could just store photo URLs in the barcode. If the guard has no mobile coverage then the passenger just gets the benefit of the doubt and the photos displayed on the pass/device are relied upon instead, otherwise you fetch the images and display them. We're getting to the point now where coverage and WiFi isn't as bad as it once was.