[black_puppydog]

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.

[weinzierl]

"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.

[black_puppydog]

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.

[weinzierl]

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.