Originally Posted by
econ
I realize the WN terminal experience at SAN is far from the greatest, but apparently this extends to booking through the app as well. Went to price out a ticket earlier and typed in the airport code "SAN", fully expecting to see San Diego appear at the top of the results list.
Well imagine my surprise when "San Diego, CA - SAN" is nowhere to be found and I have to scroll down only to find it almost at the very bottom of the list. Apparently, there are at least 20 other airports that the app feels are closer to matching the search description of "SAN", some of which don't even have all three of those letters included in the entire city + airport name!
We have an opportunity to improve this experience. I believe we have this on our baseline backlog too. I’ll check when I get in on Monday with the team.
How it works today is that the app doesn’t automatically prioritize IATA airport code matches in the filtering algorithm. It’s a basic keyword match. Once an airport name is matched to the input value, it then is pulled into the filter. The odd behavior is that if the airport is within an airport group, we also display the other airports in that group.
A better experience, which I believe we have requested to be improved, is to pull forward exact IATA code matches up to the top of the filter list since they are so commonly used by frequent travelers.
Thanks for sharing and I’ll make sure to follow up with the team.