Originally Posted by
CPRich
Perhaps you recommend it because:
You need to parse the airports asynchronously. I typed in "PIT ORD LAX OGG LIH SFO PIT" for an upcoming trip and it returned "no airport found". It took me a while to figure out that I had to type "PIT", wait for the AJAX(?) call to return a list where I could select the PIT airport, then type in ORD, wait again, select, type in LAX, wait, etc. ACK!
Also, I'm apparently flying Einstein Air, as my flight takes 0:00h
And put in statute miles. Very few folks in the US speak nautical miles or km.
And put a close button on the splash/welcome screen.
Good start, but keep working on it.
the behavior of the search bar makes it a site i won't return to. why should i have to wait for your slow lookup function to identify my airport code and make me select it? i type in LGA MCO and hit calculate before the site can return an error to me and then do nothing. this is a total usability killer.