New answers tagged html5
Just to answer the question with a question: Are there contexts where auto-focusing doesn't make sense? I think there are. If a device has JS, you can make certain assumptions about the kind of user interface that device offers and therefore, you can make a reasonable guess as to their accessibility requirements and what would be the best user experience ...
The joy stick would give it that nice old school arcade look, but maybe basing the game off of an Accelerometer could be an option as well. This would mean controlling the movements by tilting your mobile device. Here's an article from 2012 http://www.webdigi.co.uk/blog/2012/using-an-ios-device-to-control-a-game-on-your-browser/ There are limitations, but ...
Generally you should look at the use of confirmation dialogs as a last resort. They break the flow of the task for users that understand the system. The dialogs are often confused by users or not read at all. First decide if something significant will happen. If so, determine if undo function can be developed.
I don't think alert/confirm dialogs are bad, in mobile web or other contexts. When the user has to confirm an important operation, like deleting something, he will be pleased to have the opportunity to cancel this operation. But when you speak about form validation or signing out it's odd to ask confirmation for these things. Is signing out permanent? Can I ...
Take a look at this UX/Design guideline from Google about Confirming and Acknowledging: https://developer.android.com/design/patterns/confirming-acknowledging.html Although the guideline is for mobile applications, the principle and flowchart highlighted in the guideline can help you and your team decide when and when not to use alerts and confirm dialog.
Top 50 recent answers are included