Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The DB Navigator is so terrible that I try to book the German leg of my international travels from one of the other countries apps whenever possible.

> For a counter example look at the French SNCF Connect app. It is not perfect but it is a pretty workable solution.

I am extremely surprised that you would write this. The SNCF Connect app has a lot of problems. Just for starters, it can't cope with any journey with more than 2 changes. SNCF shut down there international ticket sales computer system - because it was too old. They no longer sell any international tickets, unless it's on a train actually run by SNCF.

The DB App has train services for the whole of Europe. It can plan a journey from Oslo to Sofia if required.



"They no longer sell any international tickets, unless it's on a train actually run by SNCF."

I booked ICE trains run by Deutsche Bahn via SNCF successfully in the past, the last time three days ago. I had them even send me Deutsche Bahn paper tickets for no additional cost. (Not because I wanted them in paper, but because DB insists on their app or paper if it is not an international train)

"The DB App has train services for the whole of Europe. It can plan a journey from Oslo to Sofia if required."

You can plan that in DB Navigator just fine, but have you ever managed to successfully book such a journey. I admit that my attempts were always in the east-west direction, but I can confidently say that the DB Navigator app bails at the last step of the funnel for these journeys every time, when I can book the same trains via SNCF Connect just fine.

What I love about SNCF connect is that it shows me exactly if a train has free seats and is bookable in the inital step, where DB-Navigator lets me happily compose a whole itinerary only to tell me in the last step before payment one of the trains is booked out. Then I have start the whole process from the beginning, manually steering DB-Navigator to avoid the trains I now know are booked out but DB-Navigator still pretends were available.


I agree that the booking experience of the DB-SNCF cooperation trains sucks from the DB end, but the underlying blame arguably lies with SNCF which insists on compulsory reservations which is against the philosophy of trains in Germany. On the other hand, in my experience DB offers cheaper tickets for these cooperation trains, most of the time.

But these trains are a special case; in other cases DB is clearly far more pleasant.


This is not primarily a problem of the cooperation trains, I have the same situation with trains within Germany. DB-Navigator only tells you if a train is bookable right at the end, right before payment. Before that, it might show "there is high demand", but this is rather useless, especially when you have a school kid and want to book a train a the beginning or end of school holidays, when every train is in high demand. Your only chance with DB-Navigator is to play the whack-a-mole game where you run all the steps repeatedly until the very last step until you find a train you actually can book.

In the SNCF app I have this information right away, that is what makes the difference for me.


So much this. I often use DB navigator to plan trips within france. As soon as you're not going to or from Paris, the sncf offer and app are just terrible. Often, sncf-connect will refuse to offer me TER-only (regional train) trips, because one of the legs can also be done by TGV. Basically impossible to plan this kind of thing with the SNCF apps.

But even the basic UX is terrible. The most blatant example of this is the choice to make the first text input on the search the target station. If you do limit yourself to a single text input as the entry point to the search, I see the intuition. but the result is that they are the only transit search mask I know where I have to first type where I'm going, and then where I'm coming from. I hate it.


"But even the basic UX is terrible. The most blatant example of this is the choice to make the first text input on the search the target station."

This is just your preference and not terrible UX. In fact I find this the more intuitive way.


It might be more intuitive if this was the first travel app every developed. But I don't personally any other transit UI that uses this pattern, and that makes using the sncf search "the weird one" and not in a good way.


Google maps and Apple maps all work like SNCF. The first thing you enter is your destination and then you can optionally change the point of departure if it is not your current or default location.

I would say this is a pretty familiar and useful pattern in general: Necessary and mandatory info first, optional data which has sensible defaults later.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: