That is a amazing!!! I had no idea developer meant "interested user".
> Make sure developer options are enabled. If they're not, go to Settings > About phone, then tap on Build number several times to enable it
> Go to Settings > Developer options, and scroll down to Window animation scale, Transition animation scale, and Animator duration scale.
> Tap on each of the animation options and turn them off.
https://lifehacker.com/disable-animations-on-android-to-impr...
I thought the Google Nexus 5 phone would be getting updates often...but I guess not.
It's really good!
Are you talking about this: https://www.cnet.com/how-to/speed-up-your-android-by-adjusti... ?
I set mine to "0.5", and everything's much snappier, but they still play so I still get some feedback.
HKEY_CURRENT_USER\Control Panel\Desktop\MenuShowDelay
An example of the way I use workspaces:
- one workspace for terminal, browser with documentation and some text editor
- second workspace for a full-blown IDE, another browser window with documentation and the developed application
It's funny that there are easy solutions to the cut scene problem. If user skips the cut scene there could be a little message that if you press some key the cut scene will replay. And/or give the list of all cut scenes to the point somewhere in the menu. But most of the time cut scenes are there to bring the cinematic experience and are easy and lazy thing to do...
I'm not opposed to animation, I'm opposed to animation that makes the phone unresponsive and not listen to input, or delays the display of information for more than 200-300ms. Unfortunately the "Reduce Motion" only seems to be for some very minor things.
I disable most if not all of the animations on my android phone and windows desktops for that very reason. The animations make for great tech demos but also makes everything feel so much slower when trying to get things done.
I've tried many from this list https://apple.stackexchange.com/questions/14001/how-to-turn-...
but it seems that most of commands doesn't actually make any affect
But when their timing is tight, and the whole thing happens in under, say, half a second, you get the benefits of that context association and it still feels really cool and high-tech. People jsut set their animations too slow. (Seriously, nothing should ever take longer than 500ms)
Now, if that wasn't depressing enough - the Nielsen research is from early 90's. In the intervening 25 years, the users have certainly not become any less impatient.
0: https://www.nngroup.com/articles/response-times-3-important-...
They could start with 500ms and subtract 100ms from each UI activity after each time it is used until the delay is 0ms.
The user would learn the interactions on the screen first and then not be bothered by the animations later. As a bonus the user might actually thing the program "speeded up after a 'break-in' period".
For example, it was a common piece of advice that if clicking a button opens up a dialog box, there should be a brief animation showing the box expanding from the direction of the button, so the user would associate the clicking of the button with the appearance of the box and understand where it came from. This does actually improve usability the first few times it happens, but over hundreds of iterations these tiny delays really slow down the overall experience of using the interface.