|
Size: 380
Comment:
|
Size: 2071
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| iPhone has a fixed menu... Problem statement is the most interesting... WHY use this menu? Just because you are on hardware with no menu key, so should leave it open all the time? Or is it used sometimes on other devices???? | == Problem == There is a need for access to options or controls across the application, but a '''[[Revealable Menu]]''' is already in use, or would be unsuitable due to lack of controls or conflicts with other key interactions. |
| Line 3: | Line 4: |
| == Problem == | |
| Line 6: | Line 6: |
| An always-visible menu or control set is docked to one edge of the viewport. This is often used for media players, cameras and other applications where a key set of controls or options should be visible at all times. Any time there is a need for immediate action or a learning curve must be avoided (discovering a '''[[Revealable Menu]]''') then a '''Fixed Menu''' is a good solution. Note that this pattern is being used only if it happens across the entire OS or an entire application. Controls on a single screen are simply controls. Controlling the weather radar image on one page is just a set of controls. Playback controls for a video player which are the same in all modes, are a '''Fixed Menu'''. |
|
| Line 8: | Line 14: |
| Fixed list... Also with "more" which pops up a vertical list... Often used in concert with a '''[[Revealable Menu]]''', but must be deconflicted. Both are best when placed along the bottom of the viewport. If the closed paradigm for the '''[[Revealable Menu]]''' has visibility, that may need to be changed, the visible tabs minimized in some manner, or the '''Fixed Menu''' may need to float higher up or be attached to a different side of the viewport. |
|
| Line 10: | Line 22: |
| Copy from reveal menu, except for the reveal parts. "More items" needs to be included. Can include play controls, so things like photo taking, or photo/video playback often have fixed menus |
|
| Line 12: | Line 30: |
| Copy from reveal menu, except for the closed parts. Or, refer back to it even??? Docked to an edge. Never scroll Note they CAN disappear... but only for full-screen playback types of items. They re-appear on any interaction, not by a deliberate Menu callback, hence do not at that point become reveal menus. |
|
| Line 15: | Line 39: |
Problem
There is a need for access to options or controls across the application, but a Revealable Menu is already in use, or would be unsuitable due to lack of controls or conflicts with other key interactions.
Solution
An always-visible menu or control set is docked to one edge of the viewport.
This is often used for media players, cameras and other applications where a key set of controls or options should be visible at all times. Any time there is a need for immediate action or a learning curve must be avoided (discovering a Revealable Menu) then a Fixed Menu is a good solution.
Note that this pattern is being used only if it happens across the entire OS or an entire application. Controls on a single screen are simply controls. Controlling the weather radar image on one page is just a set of controls. Playback controls for a video player which are the same in all modes, are a Fixed Menu.
Variations
Fixed list...
Also with "more" which pops up a vertical list...
Often used in concert with a Revealable Menu, but must be deconflicted. Both are best when placed along the bottom of the viewport. If the closed paradigm for the Revealable Menu has visibility, that may need to be changed, the visible tabs minimized in some manner, or the Fixed Menu may need to float higher up or be attached to a different side of the viewport.
Interaction Details
Copy from reveal menu, except for the reveal parts.
"More items" needs to be included.
Can include play controls, so things like photo taking, or photo/video playback often have fixed menus
Presentation Details
Copy from reveal menu, except for the closed parts. Or, refer back to it even???
Docked to an edge. Never scroll
Note they CAN disappear... but only for full-screen playback types of items. They re-appear on any interaction, not by a deliberate Menu callback, hence do not at that point become reveal menus.
Antipatterns