3 ms·
> Also, users can experiment with your UI/UX, so the camera example doesn't apply. That's a pretty user-hostile stance. People have things to do, figuring out
by awj 13y ago
> Also, users can experiment with your UI/UX, so the camera example doesn't apply.
That's a pretty user-hostile stance. People have things to do, figuring out which hieroglyph on their camera app does what they want is probably low on the list. I can experiment, yes, but I'd really prefer not to.
- meerita 13y agoPart of the learning curve is to know what each action do. In the case of the camera, it is normal that there are "switches". In user interfaces where the common actions are delete, move, forward the things are different: not much experimentation is allowed, if you delete, you delete and rarely you see an "undo your mistake", but in a camera UI, the actions are 95% of the time harmless to the user and they are done mostly to operate in preview mode (like when you zoom, or activate white balances, etc.) I believe fervently, and no offense to the author, that it is wrong to recall the example of the camera. Especially since Android people will surely be tested this and a thousand other things with real people knowing how crazy-paranoids in Google were with even, link colors in apps.