A number of sites use email, which can be a pain (though on iPhone, toggling between apps is easy). More generally, 2FA can be a pain - especially when integrating between an app and my iPhone (especially PingID, Authenticator and Outlook - but that's a special circle of hell for corporate implementation of tech!)
Alas, the Tesco shopping list functionality doesn't work on the scan-as-you-shop handsets if you use the barcode saved to Google Wallet!
Well yes, but sometimes having a manual with an index is better than having to type in random phrases that you think just might be relevant. If you don't know what is possible then how do you search for it on the off-chance?
I find that I type in random words that might be relevant, and then hone in on those depending on the way that the manual is set up.
I see your point but a manual explaining everything you can do with a smartphone would be enormous.
My 74 year old mum does not know what Apple Wallet is. A manual will not tell her that becuase she would need to know what Apple Wallet was to bother reading the section about how to store passes and tickets.
My 81 year old Mum does as she needed to use it for a concert. Press the side button twice was much easier to explain as how to find the ticket.
Well yes, that's how she found out. And also she asked me of course.
I was answering the point about supermarket checkouts.
It would be very helpful if railcards could be added to Wallet but, slightly surprisingly, there does not seem to be a ready way to do that.
I have had expired cards stored in my Wallet which say after their expiry date that they cannot be used, and have no functionality, so it is hard to see why the same could not apply for railcards
Surely the answer to that is for the ticket inspectors to scan the code on the railcard.
Digital railcards include a QR code (or QR-type equivalent). Does this not enable validity to be checked alongside scanning a ticket rather than just visual inspection?
You'd think so, wouldn't you
Yes it does and they are.
Not much use if you don't know what is possible.
Are you sure about that?
You're not going to know what is possible in 2026 by way of a manual unless you read hundreds of pages from front to back. But you will come across the concept that tickets can be stored on your phone quite naturally, like when sites ask you if you want to do that. And for most people I think that would prompt them to look up the answer if they didn't know.
I think a lot of this has to do with how people of different generations parse information. I find it very easy to discover reliable answers by using search engines. Likewise, many older people perhaps might like to know everything about a product before using it. "I will adapt to this piece of technology" mindset. Someone of my age will expect devices to adapt to my needs "I will use it in an intuitive way and anything that does not seem intuitive, I will Google and find the answer in 30 seconds".
I don't really think anyone has done any such thing in the thread. But equally it seems a bit strange to criticise a technology for not being able to do X Y or Z having never taken even 30 seconds to explore whether it does in fact do that.
Fair enough, but I am not the only one to feel some have.
A lot of truth in that.
DORIS shows what the barcode is.
Last I checked with TTK, that scan doesn't actually go anywhere and there's no way to put anything in the eTVD for the railcard's ticket number either.
Maybe not but it tells you what details should be on the Railcard rather than what is
I don't think this is true now. Apple provides APIs to live update passes; Eurostar uses them amongst others.
Yeah this is the issue. If you're concerned about repudiating a credential you need to have some way of consulting a trusted source. The fact the client has presented a signed token that's valid doesn't mean it can be trusted!
A behaviour that is at the heart of some of the issues reported here, and which is driven by a security model that presumes distrust unless otherwise satisfied.
