whoa! Chrome crash! - UX challenge of presenting a catastrophic failure
A kind of California style, cool and casual way to tell the user that something truly bad has happened to the Google Chrome browser.
why ask?
Although this is a "mere browser" and not the OS (there is still a difference, right?) - this does not seem so much different or better than Microsoft's prompting the user when the dotnet platform exhausts memory.
Such an error seems unrecoverable - like a catastrophic failure, there is no choice to be made - so why ask?
The user really does not have much choice - so why prompt? and why should the user need to decide what to do with your bug?
Comments
Post a Comment