What?! Do not TRY again?

Just a couple of weeks ago, I spent a week in Shanghai (China) for work. It was the second time in my life that I actually went to Shanghai and no doubt that it is really a nice place! This city is so amazing that it brings me various thoughts. I am really amazed at how Social Media is being utilized to the fullest until the extent where you are able to “get a queue number” and “order your meals” through the same social app. For this, I would have them covered in the next post or so.

When I was on my way to the Airport heading home, I was on the Uber and wanting to know which Terminal should I be heading for, I encounter the following error while surfing the Pudong International Airport website on my mobile.

2016-08-19 12.21.19

Notice the message shown above? It stated “Query error, please do not try again!”. Base on the experience that I had as a Software Engineer, I can derive that the whole purpose of such message is that there are probably an error retrieving data from the database or there are error displaying the data.

All-in-all, there was an error!

Error handling has exists for ages and why on earth it is so difficult to have some text or message that is much more friendly for end-users? By telling user not to try again, it just turn people off. Especially for users like me whom is relying on the website for important information for my flights details. Sometimes I ponder whether websites exists to provide information and services to users?

Well, there are nice message that could just gives assurance to users:

Oops! We met into some issue and hang on there while we are fixing it!

However, do not use this as a default one and expects users to be repeatedly seeing this! On top of that, once this message is being displayed, the backend system should also capture it as part of the System Error Logs and trigger the Web-Administrator.

Just my 2 cents worth.

Cheers,
/M

By | 2016-08-29T22:24:17+00:00 August 29th, 2016|Best Practices, Development, My Thoughts|0 Comments

About the Author:

Leave a Reply