Differences between revisions 3 and 4
Revision 3 as of 2010-11-01 22:27:03
Size: 475
Editor: shoobe01
Comment:
Revision 4 as of 2010-11-01 22:37:02
Size: 2286
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
principles:
- easy to get to brightness: if no notification strip or interactive annunicator row, then suggest variations off the volume pop-up (e.g. sideways is brightness)
- Easy to disable auto-bright
- Function to add user-adjustment to auto-bright; doesn't disable, just changes it for now... ideally, remember this and factor it in over time based on bright sensors
- Sensors will continue to be on front; among other things, probably best for checking light where the user us; Calibrate sensors not to neutral gray, but to people's faces at typical distances.
- Do not use large steps. Do it seamlessly. Prefer to use the native adjustment, e.g. 100 or 256 steps. But do not cut back to 16 or below. People can see the steps, so need more than that.
- Display brightness numerically. Users may become accustomed to one, or at least will have a point of reference when upgrading, discussing with care, etc. Some people prefer numbers and words to graphic interfaces.
- Consider use of direct input, so the user does not have to slide or scroll to a desired brightness; especially if hard to see, allowing typing a new value may be quicker for some users.
- Allow max bright and min bright from control panels. Down to 1 (or 1 of 256 or whatever) % is what we mean by min bright.
- Brightness adjustments must adjust live, so user can tell how bright they want it (do not set then change brightness) ...
- ... but must be simulated so they can fix it if they need to. Or adjust even if they cannot see the screen now. Make the screen 100% bright, with the adjustment sliders and instructions simulated 50% bright and very high contrast. Then have the rest of the screen able to simulate (with color changes to the pixels themselves or opacity to a black overlay...) the adjusted to value.

Problem

Solution

principles: - easy to get to brightness: if no notification strip or interactive annunicator row, then suggest variations off the volume pop-up (e.g. sideways is brightness) - Easy to disable auto-bright - Function to add user-adjustment to auto-bright; doesn't disable, just changes it for now... ideally, remember this and factor it in over time based on bright sensors - Sensors will continue to be on front; among other things, probably best for checking light where the user us; Calibrate sensors not to neutral gray, but to people's faces at typical distances. - Do not use large steps. Do it seamlessly. Prefer to use the native adjustment, e.g. 100 or 256 steps. But do not cut back to 16 or below. People can see the steps, so need more than that. - Display brightness numerically. Users may become accustomed to one, or at least will have a point of reference when upgrading, discussing with care, etc. Some people prefer numbers and words to graphic interfaces. - Consider use of direct input, so the user does not have to slide or scroll to a desired brightness; especially if hard to see, allowing typing a new value may be quicker for some users. - Allow max bright and min bright from control panels. Down to 1 (or 1 of 256 or whatever) % is what we mean by min bright. - Brightness adjustments must adjust live, so user can tell how bright they want it (do not set then change brightness) ... - ... but must be simulated so they can fix it if they need to. Or adjust even if they cannot see the screen now. Make the screen 100% bright, with the adjustment sliders and instructions simulated 50% bright and very high contrast. Then have the rest of the screen able to simulate (with color changes to the pixels themselves or opacity to a black overlay...) the adjusted to value.

Variations

Interaction Details

Presentation Details

Antipatterns

Examples

DISCUSS: This article at Gizmodo is pretty darned good, and point out that the issues with current devices are not whiny, or individually-perceived, but truly bad. - SSH

Display Brightness Controls (last edited 2011-08-01 00:09:18 by shoobe01)