Haywain
Veteran Member
- Joined
- 3 Feb 2013
- Messages
- 15,357
From bitter experience I would say that is quite optimistic.I'm sure it'd take about 2 months to commission a change to be made officially here
From bitter experience I would say that is quite optimistic.I'm sure it'd take about 2 months to commission a change to be made officially here
I'm sure the LNER App should support purchases until more or less departure time.Given that one of the great advantages of online purchases is being able to make last minute decision it does seem odd that too many rail ticketing apps do not support purchases right up to the time of the given journey.
Assuming there's a team still actively working on the product I'd probably guess at least a month for it to grab the attention of a product owner, at least a couple of weeks to agree that it's s candidate for the small changes workflow, another week or so to write up the ticket, 3 weeks waiting for design input, at least a week waiting for the next backlog review, probably at least a fortnight waiting for higher priority small changes, a week to do it, another week to test, and a fortnight for beta testing and deployment. Essentially 3 months at best, with a high chance of it not making the top of the backlog for 6 months in the middle.From bitter experience I would say that is quite optimistic.
Plenty of threads on this forum complaining about ticket machines, but also plenty complaining about lack of knowledge and lack of enthusiasm to help in ticket offices too. Plenty of reasonably standard tickets that Sheffield ticket office won’t sell you for example.They’d have sold you the correct ticket, something an app appears unable to do.
See no issue with this if it can be suitably self funded without additional money from the tax payer or without additional increases to fares.A good argument for manning stations from start to close of service then!
I'm amazed at how quickly you were able to write the extension. Good work.The underlying booking engine does support :15, :30 and :45 minute specifiers, so spent ten minutes writing a WebExtension to expose these:
View attachment 147365
I'm sure it'd take about 2 months to commission a change to be made officially here
If there's any interest I'll chuck it on the Chrome Web Store, but the extension is attached..
Generally true, but for this specific case, the LNER app does 15-minute periods anyway (but you do lose the ability to fulfil to Ticket on Departure when eTickets are available).Worth noting, for those that might not be aware, extensions don't work in Chrome on Android phones. I assume it's the same in iOS too.
The Kiwi Browser Android app, which is based on Chromium, does support extensions but as they aren't usually designed for mobiles, they don't always work.
It does but I noted the opening poster didn't want to use an app.Generally true, but for this specific case, the LNER app does 15-minute periods anyway (but you do lose the ability to fulfil to Ticket on Departure when eTickets are available).
I can't see anywhere that the OP has said that.It does but I noted the opening poster didn't want to use an app.
I didn’t, but on that point, when I’m in a hurry it makes sense for me to be able to quickly go to a website I’m familiar with.I can't see anywhere that the OP has said that.
Fair enough but I find the app very user friendly.I didn’t, but on that point, when I’m in a hurry it makes sense for me to be able to quickly go to a website I’m familiar with.
Not if I don’t already have it on my phone.It's hard to see why most people wanting to buy a last minute online ticket would use a website rather than an app. Apps are most people's default, especially when using a phone, not a laptop.
It's not a criticism. It is saying that it is perhaps understandable if LNER and other TOC think that the main interest of their customers is in using apps on their phones, not websites, and so prioritise their development.Not if I don’t already have it on my phone.
A lot of posts here criticising other people’s media habits or choice of where they get tickets from; no need for people to tell others to do things a different way, let’s just make sure all of the advertised ways are actually effective?
I know, but I'm just saying whether or not (and for what reason) I choose to use the app or the website isn't really relevant when both should be enabled so one can purchase available tickets.It's not a criticism. It is saying that it is perhaps understandable if LNER and other TOC think that the main interest of their customers is in using apps on their phones, not websites, and so prioritise their developmeny.
Help me understand. I'm genuinely trying to figure out what advantage there is in using the website over the app?I know, but I'm just saying whether or not (and for what reason) I choose to use the app or the website isn't really relevant when both should be enabled so one can purchase available tickets.
For one thing, I don't want wasted storage or a clogged home screen for a service I'll barely use.Help me understand. I'm genuinely trying to figure out what advantage there is in using the website over the app?
For one thing, I don't want wasted storage or a clogged home screen for a service I'll barely use.
It did. The problem was just that getting the search results for right away was impossible. You had to search for a future time selected manually (not even defaulted to the next available time, abd if you searched for a time 14 minutes in the future you got an error message and it still didn't change your search) and then press back, adding friction. It's slower on my device than the trainline app is and it doesn't seem to remember my recent locations so searching would always take longer. However after being promoted by someone in this thread I've just checked for updates on the app and lo and behold it does now offer a "now" search option by default in the app. What a pleasant surprise.I'm sure the LNER App should support purchases until more or less departure time.
If this was the case then they wouldn't work so hard to bully people into using the app rather than the website. LNER's main trick is to only let you book reward tickets through the app, although of course pushing you into seatfrog is similar. In development terms it's generally a lot easier to provide a website than an app, it will work across a wider range of devices and generally solves accessibility problems more gracefully.It's not a criticism. It is saying that it is perhaps understandable if LNER and other TOC think that the main interest of their customers is in using apps on their phones, not websites, and so prioritise their development.
'Bully'? That is an extraordinary word to use. It is very normal for businesses to steer and incentivise customers to use one option rather than thevother, but that is a very long way from bullying.If this was the case then they wouldn't work so hard to bully people into using the app rather than the website. LNER's main trick is to only let you book reward tickets through the app, although of course pushing you into seatfrog is similar. In development terms it's generally a lot easier to provide a website than an app, it will work across a wider range of devices and generally solves accessibility problems more gracefully.
The main reasons for companies to push apps in preference to web are that they want to prevent you from using adblockers or blocking cookies, or that somebody has wasted a lot of money on a mobile development agency and would rather double down than admit their mistake.
The main reasons for companies to push apps in preference to web are that they want to prevent you from using adblockers or blocking cookies, or that somebody has wasted a lot of money on a mobile development agency and would rather double down than admit their mistake.
The storage such apps use is next to nothing. I just checked my LNER app. After multiple uses, it take up 57mb on my phone compared to, for example, Facebook which takes up 885mb.For one thing, I don't want wasted storage or a clogged home screen for a service I'll barely use.
It was this post below but I was misremembering @TT-ONR-NRN, said.I can't see anywhere that the OP has said that.
Because I dislike TfW's website, GWR outrageously force you to download their app, Trainsplit is my preferred option but sometimes long winded and not ideal for when in a hurry, etc. It's simply a booking engine I know well as (apart from this) don't normally have problems with getting a ticket quickly.
But if one builds a responsively designed Web site, it shouldn't matter if one is on a mobile or desktop, as the site will adapt. So offering 15 minutes on a desktop site would replicate on the mobile site.It's not a criticism. It is saying that it is perhaps understandable if LNER and other TOC think that the main interest of their customers is in using apps on their phones, not websites, and so prioritise their development.