android - Disabling or hiding controls design guideline? -


I have recently tested design guidelines from Android developers and used at least 4 states for interactive UI elements. Recommended to do so.

Default, Disabled, Focus, Pressed

See, Slide 13

On the other side slide 10 says that the right things start to appear.

Now I am trying to figure out when the control is disabled and when to hide them I think that if no control is applicable at this time, then it should not be visible to reduce the UE disorder.

On the other hand, to disable this zoom button, I understand that zooming is no longer possible. Just like though. May be even better to hide.

I'm not sure. Will anyone get any other reference to hide and when only one can help to disable control

Is the Android or mobile application specific due to screen or size specific recommendation?

The acceptable answer to the link given above is very high I want to say that this is a common scenario question Was there. In specific environments, especially the small-screen mobile device, I think the hiding becomes more important. I try to constantly try to hide those things from which I do not use it so that I can find those things faster I should do.

It would be best to hide those elements which will be disabled for a long time and can only disable things that can often be enabled / disabled.

For zooming, I find it frustrating that when such kind of controls disappear. It is often used so I think it is inappropriate to hide it.

"What do you need to pay attention to when you decide for one or the other?" I would say that the user environment, how often it can be used / toggle, how important it is for the application or user, and how closely it relates to other options / elements.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -