Apple iPhone

The flight app has so far worked well on CT.
That’s history now.
With the new free floating destination field, it has been misbehaving.
I typed BLR for Bengaluru and the orange error reads “pl pick a destination different from your origin”.
Huh?
aaasaaaaaaaaaaarrrrrrgh.!.^*???#??????

~dv

dv – We tried replicating this error at our end and the only way you get this error is when your source and destination are same.

I use this app at an average of one ticket purchase a month.
You should credit me with a higher degree of responsibility than what you have suggested.

This error is easily repeated. I repeated it even now. Only it showed a new error (more sophisticated verbiage) but means the same …

Just so you know, my environment is: Apple iPhone running Safari. Firmware ver: 1.0.2

I will probably do a video and send you a Youtube link. Bekar weekend project but will give me something to do.

G’night.

dv—look forward to the video ;)

We’re not currently optimised for the iPhone. Prior to our international search, our site happened to work well with the iPhone. Anyway, we’ll see what we can do to help things along.

Thanks for raising this to our attention.

Thank you for the revelation.

I will now drop my video project & do something more useful; it was mainly to kick Nikhil in the shin for his presumptive statement (no offence meant but you know how one feels).

As a suggestion, you should solve this problem by accepting an input into the blank box (on the RHS) with the IATA 3-letter airport code. BLR for Bangalooru (which is btw an obnoxious spelling … where did you get that from?) and PNQ for Pune (or “Poona, IN Lohegaon blah blah” as you call it).

That way, it will work for such devices/browsers that do not have the ability to let you use the funny script you are currently using to prompt the user with.

This new International search release is a bit of a let down and I have had to buy 3 tickets (so far) off makemytrip.

Cheers,
dv

dv—thanks for the feedback, that’s a great suggestion.

Could you post some more details on why you feel the international search is a let down? Is it just the iPhone issue? All your feedback will go a long way in helping us improve things. Look forward to hearing your feedback.

Hi Hrush, as the guy says, being able to enter the IATA airport code is a safe fallback to your context sensitive international search that tries to find city matches.

Yup, we’ll take care of that.