Automatic logout - good or not?
When an updat is rolled out across a system or across a site there is an expected down time. However when we are dealing with the world wide web there is no 3am at the same time everywhere - so what are you options?
Online there is either a site message such as, “We are currently creating a better online experience for you and updating oru service. We will be back in a few moments - sorry for the inconvenience” or there is what I just experienced - a forced log and lock out until the update has been rolled across the services server you are currently hitting.
Hotmail, yes that good old bastion has been of some focus of recent days. I am sailing the Greek islands and am using a iPhone to keep up with the world. The mobile hotmail experience is bad enough ( no iphone beauty like gmail or pop support unless you pay ), but when you are mid session and you get the message - “sorry we have to log you out as we are currently doing site maintenance” it can be frustrating.
What is the best option in your opinion. What is the best roll out of upgrades for sites that have millions of users spread internationally with no determined usage times? Is it 3am country by country so local servers get updated piecemeal? OR do you take your whole service off line for one simultaneous update, hoping that there isnt a glitch and a roll back has to incur.
Think loss of advertising dollars, loss of user interation and engagement, think - user irritation.
Love your thoughts!
Filed under: General News, UX & Usability on July 17th, 2008