[rhygar]

The whole thing has "designed by an engineer" all over it. From hidden UI that reveals itself by clicking/hovering on various elements, to the entire process being limited to one screen which various pop-out elements and transformations. There is little consistency in the design, and poor or no usage of contrast to separate information visually.

When clicking the large blue button to the right of a flight, several rows of return flights drop down below that. The only visual distinction between these specific sub-rows and the other departing flights below is a thin blue/gray border on the sides.

Going from A to B is called an "Outbound flight", while going from B to A is called a "Return flight". Copy is very important in UI design. It should be outbound/inbound or depart/return, not some mix of different terminology.

Durations are always "-- Xh -->". What is the point of the arrow if it is always pointing to the right? Why is the duration a lighter shade than the rest of the text?

The left column is a Gawker/Gizmodo style static column that locks in place when scrolling down. The Google search results page doesn't do that.

These are basics, and a company the size of Google with as many employees as it has should be able to get these things right.

[waqf]

Outbound/return is standard terminology all over the travel industry. Including in UK and US, and for trains and for planes: I'm surprised you're not familiar with it.

"Depart" means something different: it refers to the beginning of each leg of the journey. Its opposite is "arrive". So you might have an outbound leg which departs from LAX and arrives in SFO, and then a return leg which departs from SFO and arrives in LAX.

[rhygar]

Hipmunk.com says depart/return and Iflyswa.com says departing/returning. Your claim is 0/2 so far.

[whatusername]

I went to go and prove you wrong (I personally use outbound/return).

But webjet (Departing/Returning) and skyscanner (Depart/Return) seem to back you up.