diff --git a/site/components/macro-view/images/ios11-iphone.jpg b/site/components/macro-view/images/ios11-iphone.jpg new file mode 100644 index 0000000..596c340 Binary files /dev/null and b/site/components/macro-view/images/ios11-iphone.jpg differ diff --git a/site/components/macro-view/images/ios11-macro.jpg b/site/components/macro-view/images/ios11-macro.jpg new file mode 100644 index 0000000..650f01f Binary files /dev/null and b/site/components/macro-view/images/ios11-macro.jpg differ diff --git a/site/components/macro-view/images/ios11-quit-app.gif b/site/components/macro-view/images/ios11-quit-app.gif new file mode 100644 index 0000000..e273015 Binary files /dev/null and b/site/components/macro-view/images/ios11-quit-app.gif differ diff --git a/site/components/macro-view/images/state-diagram.jpg b/site/components/macro-view/images/state-diagram.jpg new file mode 100644 index 0000000..5241fd1 Binary files /dev/null and b/site/components/macro-view/images/state-diagram.jpg differ diff --git a/site/components/macro-view/index.html b/site/components/macro-view/index.html index cc01860..3f4888f 100644 --- a/site/components/macro-view/index.html +++ b/site/components/macro-view/index.html @@ -5,274 +5,428 @@ - name: Anson Adams github: ansonadams - name: Khiem Lu - github: khiemlu96 + github: khiemlu96 + - name: Danico Pidlaoan + github: danicobryan ---
A macro view arranges an entire, often complex, information system into a single view for the purpose of “contrast, comparison, [or] choice.”1
-A macro view describes not a single component, but a visual design technique. The appearance of a macro view can only be extrapolated from the design principles it emphasizes. Therefore, the variation of its appearance is only limited to the designer’s imagination. Most notably, a macro view is most effective when enough details are present that the user absorb the information in its full complexity and subtlety. Macro views are consequentially information-dense; information systems are usually complex and screen space is limited.
+ -Overall, The appearance of a macro view across any platform may differ in design, but conveniently displays information for the user to easily switch between tasks. Data is pulled apart and organized in a way that the user can easily access, compare, and select.
+A macro view describes not a single component, but a visual design technique. The appearance of a macro view can only be extrapolated from the design principles it emphasizes. Therefore, the variation of its appearance is only limited to the designer’s imagination. Most notably, a macro view is most effective when enough details are present that the user absorb the information in its full complexity and subtlety. Macro views are consequentially information-dense; information systems are usually complex and screen space is limited.
-Overall, The appearance of a macro view across any platform may differ in design, but conveniently displays information for the user to easily switch between tasks. Data is pulled apart and organized in a way that the user can easily access, compare, and select.
-When a user calls the macro viewing function, the system instantly organizes and separates all the displayed information from one another. Typically throughout various systems, windows/applications are physically pulled apart from each other and viewed at a macro level.
+However, it is possible to narrow one’s focus on a particular subsection of the view. For this, the user can zoom
or perform an action accomplishing a narrowing or broadening of focus. To accomplish a zoom
, a user could select
progressively smaller areas of the data and the display could zoom
on the selections. Although, this is only one imagined implementation of events when there are far more possible control schemes.
Under “Platform-Specific Instances” we can see how different systems apply macro viewing.
+When a user calls the macro viewing function, the system instantly organizes and separates all the displayed information from one another. Typically throughout various systems, windows/applications are physically pulled apart from each other and viewed at a macro level.
-However, it is possible to narrow one’s focus on a particular subsection of the view. For this, the user can zoom
or perform an action accomplishing a narrowing or broadening of focus. To accomplish a zoom
, a user could select
progressively smaller areas of the data and the display could zoom
on the selections. Although, this is only one imagined implementation of events when there are far more possible control schemes.
Under “Platform-Specific Instances” we can see how different systems apply macro viewing.
- +Learnability is crucial to the effective use of a macro view. A macro view displays a necessarily complex dataset. Therefore, if a design isn’t thoughtfully organized and clear, the sheer amount of information will overwhelm the user. A macro view’s quality can be best measured by its learnability because at its core, a macro view must present large amounts of information in an easily understandable manner. However, if you were to ask a person who has never used the system before to display the macro view, there is a high chance the user would not be able to figure it out on his or her own. Reasons for this can be due to the vast amount of functions on the particular system or the confusion of what macro viewing does.
+Efficiency could be considered important if a macro view is used frequently. Being able to quickly and easily call the macro view can exponentially increase a user’s total efficiency in executing a task on the system. The user would be able to swiftly switch, select, and compare different data. For instance, a macro view could be used as a root page in an application. Efficiency could also be key for operators who need to work with large amounts of data in small amounts of time, such as air traffic control operators or, as Tufte notes in Envisioning Information, high speed train managers.
+Errors are more application-specific. A user could have committed an error if they did not understand the macro view’s representation of the data. For example, they could misconstrue one variable as another on a graph. More importantly, it could be the macro view itself that causes errors due to confusing design or poor organization of data. Overall, a system’s failure to clearly depict a macro view by organizing data in an efficient manner can result in errors.
+Memorability and satisfaction play less of a critical role. A poorly designed macro view would require high memorability because the user would have to partially relearn it each time they reencountered it. If accessing macro view is highly efficient and learnable, the user should be able to remember how to access it once again. Problems may occur in memorability if the physical function of accessing the macro view is extremely similar to another function. Satisfaction has little to do with macro views because they attempt to communicate data. Satisfaction would also derive from the learnability of the macro view, since a macro view that is difficult and confusing to learn will surely frustrate users.
+Learnability is crucial to the effective use of a macro view. A macro view displays a necessarily complex dataset. Therefore, if a design isn’t thoughtfully organized and clear, the sheer amount of information will overwhelm the user. A macro view’s quality can be best measured by its learnability because at its core, a macro view must present large amounts of information in an easily understandable manner. However, if you were to ask a person who has never used the system before to display the macro view, there is a high chance the user would not be able to figure it out on his or her own. Reasons for this can be due to the vast amount of functions on the particular system or the confusion of what macro viewing does.
-Efficiency could be considered important if a macro view is used frequently. Being able to quickly and easily call the macro view can exponentially increase a user’s total efficiency in executing a task on the system. The user would be able to swiftly switch, select, and compare different data. For instance, a macro view could be used as a root page in an application. Efficiency could also be key for operators who need to work with large amounts of data in small amounts of time, such as air traffic control operators or, as Tufte notes in Envisioning Information, high speed train managers.
-Errors are more application-specific. A user could have committed an error if they did not understand the macro view’s representation of the data. For example, they could misconstrue one variable as another on a graph. More importantly, it could be the macro view itself that causes errors due to confusing design or poor organization of data. Overall, a system’s failure to clearly depict a macro view by organizing data in an efficient manner can result in errors.
-Memorability and satisfaction play less of a critical role. A poorly designed macro view would require high memorability because the user would have to partially relearn it each time they reencountered it. If accessing macro view is highly efficient and learnable, the user should be able to remember how to access it once again. Problems may occur in memorability if the physical function of accessing the macro view is extremely similar to another function. Satisfaction has little to do with macro views because they attempt to communicate data. Satisfaction would also derive from the learnability of the macro view, since a macro view that is difficult and confusing to learn will surely frustrate users.
-A macro view is highly effective when it captures an information system fully and completely. Tufte argues that detail in macro views have two primary benefits. Detail complements the human ability to read complex visual data and also enriches comparative tasks, the main purpose of using macro views. He summarizes that “to clarify, add detail.”1
+Macro views can either retain or hide detail. Edward Tufte describes a particular form of macro view, which he calls a “macro / micro reading” of an information set. Tufte’s macro view not only retains the data’s details, but relishes in them since “detail cumulates into larger coherent structures.“ In this case, a macro view is “rich with data” and “can report immense detail” if properly organized.1
-A macro view cannot work without an intelligently designed presentation of the designer’s mental model and or data. This is due to the inherent complexity of the presented information. A commonly overlooked distinction that Tufte notes is that “the quantity of detail is an issue completely separate from the difficulty of reading.”1 Macro views must be properly designed so that they take advantage of the available details. Else, they will simply be plain, unreadable graphs of massive amounts data.
+Overall, macro viewing would not work if design and structure were not explicit. It is key for every priority metric and can determine whether a user would like to use macro viewing or not.
+A macro view could also hide subtleties and conglomerate data into larger chunks. However, this has the potential to undermine the core strengths of a macro view. One instance of this would be the iPhone’s default calendar application: in the single day view, users can chart their scheduled events across a list of individual hours. When they zoom out to the month view, hourly information is reduced to a binary “has” or “does not have” an event or multiple events on a given day.
-Further variation can be broken down into how a macro view is implemented.
-Macro viewing allows a user to swiftly switch between tasks and efficiently view and organize data. Should a macro view be excellently designed, the user will be empowered in their experience of the data or system. The presentation will be so clear that they will control the flow of information, rather than the “editors, designers, or decorators” of the view.1
+The Time Machine history window on a Mac could possibly be considered a macro view in that it displays many backups at once on a single screen. However, the view could be considered ineffectual because the backups are displayed on top of each other, making visual comparison impossible. Furthermore, the entire system directory is displayed for each backup rather than highlighting the changes between states like in GitHub’s commit history.
-Macro views can either retain or hide detail. Edward Tufte describes a particular form of macro view, which he calls a “macro / micro reading” of an information set. Tufte’s macro view not only retains the data’s details, but relishes in them since “detail cumulates into larger coherent structures.“ In this case, a macro view is “rich with data” and “can report immense detail” if properly organized.1
+The DiskUsage application for the Android phone is an excellent example of a macro view. Differently sized rectangles correspond to the relative memory usage of different types of files, resulting in an instantly clear, navigable graph. For a complete macro / micro view, the rectangles could be broken down into further subsections until individual file specificity is achieved.
-A macro view could also hide subtleties and conglomerate data into larger chunks. However, this has the potential to undermine the core strengths of a macro view. One instance of this would be the iPhone’s default calendar application: in the single day view, users can chart their scheduled events across a list of individual hours. When they zoom out to the month view, hourly information is reduced to a binary “has” or “does not have” an event or multiple events on a given day.
+Further variation can be broken down into how a macro view is implemented.
+A macro view is highly effective when it captures an information system fully and completely. Tufte argues that detail in macro views have two primary benefits. Detail complements the human ability to read complex visual data and also enriches comparative tasks, the main purpose of using macro views. He summarizes that “to clarify, add detail.”1
-The Time Machine history window on a Mac could possibly be considered a macro view in that it displays many backups at once on a single screen. However, the view could be considered ineffectual because the backups are displayed on top of each other, making visual comparison impossible. Furthermore, the entire system directory is displayed for each backup rather than highlighting the changes between states like in GitHub’s commit history.
+A macro view cannot work without an intelligently designed presentation of the designer’s mental model and or data. This is due to the inherent complexity of the presented information. A commonly overlooked distinction that Tufte notes is that “the quantity of detail is an issue completely separate from the difficulty of reading.”1 Macro views must be properly designed so that they take advantage of the available details. Else, they will simply be plain, unreadable graphs of massive amounts data.
-The DiskUsage application for the Android phone is an excellent example of a macro view. Differently sized rectangles correspond to the relative memory usage of different types of files, resulting in an instantly clear, navigable graph. For a complete macro / micro view, the rectangles could be broken down into further subsections until individual file specificity is achieved.
+Overall, macro viewing would not work if design and structure were not explicit. It is key for every priority metric and can determine whether a user would like to use macro viewing or not.
-Macro viewing allows a user to swiftly switch between tasks and efficiently view and organize data. Should a macro view be excellently designed, the user will be empowered in their experience of the data or system. The presentation will be so clear that they will control the flow of information, rather than the “editors, designers, or decorators” of the view.1
+Mac OS X’s Mission Control feature exhibits a well-designed macro view. According to the Mission Control panel in the Mac System Preferences, “Mission Control gives you an overview of all your open windows, thumbnails of your full-screen applications, and Dashboard, all arranged in a unified view.”3
-Mac OS X’s Mission Control feature exhibits a well-designed macro view. According to the Mission Control panel in the Mac System Preferences, “Mission Control gives you an overview of all your open windows, thumbnails of your full-screen applications, and Dashboard, all arranged in a unified view.”3
+To access the Mission Control view, a Mac user must simply swipe up with three or more fingers. The following then occurs:
-To access the Mission Control view, a Mac user must simply swipe up with three or more fingers. The following then occurs:
+While in the Mission Control macro view, users can:
-While in the Mission Control macro view, users can:
+Mission Control is highly learnable for two primary reasons. First, the controls are simple: swipe up. They are also intuitive, employing direct object manipulation when users drag windows from one desktop to another. Additionally, the layout is effortlessly understandable. Different components belong exclusively to different areas of the screen. Open application windows are separated by empty space, making the layout faster to read.
-Windows are also annotated, so errors are rendered nearly impossible. However, an error could occur if the user opts to group windows of the same application. Then, windows could potentially be hidden and not selectable by the user.
-The view is also extremely efficient. The windows animate from their original position to organized position. The animation is slow enough for the user to track the movement, but not slow enough for the user to have to wait.
-Mission Control is highly learnable for two primary reasons. First, the controls are simple: swipe up. They are also intuitive, employing direct object manipulation when users drag windows from one desktop to another. Additionally, the layout is effortlessly understandable. Different components belong exclusively to different areas of the screen. Open application windows are separated by empty space, making the layout faster to read.
+The simplicity of design makes Mission Control controls highly memorable. The only gesture that seems arbitrary is swiping up to activate mission control. Considering the other controls (click to select, drag to move) are so logical, perhaps a zooming out gesture would have been more consistent. Ease of use leads to high satisfaction. The layout is aesthetically pleasing, animates smoothly, and is ultimately an extremely productive tool.
-Windows are also annotated, so errors are rendered nearly impossible. However, an error could occur if the user opts to group windows of the same application. Then, windows could potentially be hidden and not selectable by the user.
+The view is also extremely efficient. The windows animate from their original position to organized position. The animation is slow enough for the user to track the movement, but not slow enough for the user to have to wait.
-The simplicity of design makes Mission Control controls highly memorable. The only gesture that seems arbitrary is swiping up to activate mission control. Considering the other controls (click to select, drag to move) are so logical, perhaps a zooming out gesture would have been more consistent. Ease of use leads to high satisfaction. The layout is aesthetically pleasing, animates smoothly, and is ultimately an extremely productive tool.
-Task View is a useful Windows 10 function that displays a macro view of the desktop in order to organize and view open applications simultaneously.
-Task View is a useful Windows 10 function that displays a macro view of the desktop in order to organize and view open applications simultaneously.
+To access the Task View, a Windows 10 user must simply hit the Windows Key + Tab. The following then occurs:
-To access the Task View, a Windows 10 user must simply hit the Windows Key + Tab. The following then occurs:
-The appearance of a macro view on Windows 10 looks like a zoomed out desktop in which open windows are pulled apart and labeled at the top. On the bottom of the screen, there are also multiple desktops that the user can switch between if they have more than one desktop open. Essentially, all the applications currently open are viewable at once for the user to easily switch between tasks.
+The appearance of a macro view on Windows 10 looks like a zoomed out desktop in which open windows are pulled apart and labeled at the top. On the bottom of the screen, there are also multiple desktops that the user can switch between if they have more than one desktop open. Essentially, all the applications currently open are viewable at once for the user to easily switch between tasks.
-Windows Flip: Allows the user to switch between running applications. It does not display the windows in the same organized manner as the Task View, but allows for a quicker way to switch between windows.
+While in Task View, users can:
-Task View and Snap: Allows the user to select a window to take half the screen while the other half displays the Task View of the desktop.
+selecting
which desktop to move the window to. While in Task View, users can:
+selecting
which desktop to move the window to. Windows Flip: Allows the user to switch between running applications. It does not display the windows in the same organized manner as the Task View, but allows for a quicker way to switch between windows.
- +Task View and Snap: Allows the user to select a window to take half the screen while the other half displays the Task View of the desktop.
- +Efficiency: Accessing Task View is efficient through keyboard shortcuts embedded on a machine running Windows 10. The desktop organizes the running applications in a clean and smooth manner that allows for easy access of open windows. The functions within Task View are also simple and intuitive.
-Efficiency: Accessing Task View is efficient through keyboard shortcuts embedded on a machine running Windows 10. The desktop organizes the running applications in a clean and smooth manner that allows for easy access of open windows. The functions within Task View are also simple and intuitive.
+Memorability: The main problem with memorability may be remembering the keyboard shortcut. Although there is only one keyboard shortcut to accessing the Task View (Windows key + Tab), users may be confused with all of the other functions that involve the Windows key. However, if accessed a couple of times, the user should be able to familiarize themselves with the shortcut. On the other hand, memorability with the functions inside Task View should be easy due to the simple, clear-cut design. Being able to select, move, or delete certain desktops or applications are clearly shown.
-Memorability: The main problem with memorability may be remembering the keyboard shortcut. Although there is only one keyboard shortcut to accessing the Task View (Windows key + Tab), users may be confused with all of the other functions that involve the Windows key. However, if accessed a couple of times, the user should be able to familiarize themselves with the shortcut. On the other hand, memorability with the functions inside Task View should be easy due to the simple, clear-cut design. Being able to select, move, or delete certain desktops or applications are clearly shown.
+Learnability: Task View may be easy to access, but can be confusing to learn without any help or guidance. If you were to ask a new Windows 10 user to open up the Task View, it would be hard for them to figure it out with all the other functions on a computer. However, similar to memorability, learning to use the functions within task view should be relatively quick for a new user due to the clear design and minimal excess functions.
-Learnability: Task View may be easy to access, but can be confusing to learn without any help or guidance. If you were to ask a new Windows 10 user to open up the Task View, it would be hard for them to figure it out with all the other functions on a computer. However, similar to memorability, learning to use the functions within task view should be relatively quick for a new user due to the clear design and minimal excess functions.
+Errors: Errors can occur if a different keyboard shortcut is mistaken to be Task View. Other than that, the simplicity of the functions within Task View should not cause any remarkable errors.
-Errors: Errors can occur if a different keyboard shortcut is mistaken to be Task View. Other than that, the simplicity of the functions within Task View should not cause any remarkable errors.
+Satisfaction: User satisfaction in Task View is dependent on design, and Windows 10 does a great job displaying the macro view of the desktop. Task View is easy to access and understand making it highly satisfying.
-Satisfaction: User satisfaction in Task View is dependent on design, and Windows 10 does a great job displaying the macro view of the desktop. Task View is easy to access and understand making it highly satisfying.
+ +The new iOS 11 update that was released in October 2017 brought a new user interface with the + ability to diplay running applications in a macro view. The new macro view implementation + is a combination of Mac OSX's Mission Control feature that displays the windows of running applications + and the new Control Center interface, which displays controls such as Wifi, volume and music + controls, flashlight, camera, and more.
+ + ++
To access App Switcher View, users can: +
Swipe
up with four fingers.Double-click
the home button.While in App Switcher View, users can: +
Scroll
to the right to view the rest of the applications.Swipe
up on any application to quit and stop running the application.Click
on any application window to visit the application.
+ Click
on Control Center buttons like Wifi, music control buttons, night shift, camera, and more.To exit App Switcher View, users can: +
Double-click
the home buttonHere is a demo of iOS App Switcher in action on the iPad, featuring how to activate the macro view + and different controls and events the user can implement while in the view.
+ +Note: The most recent version of iOS 11 implements a swipe up
+ function to exit out of an application rather than the hold
and
+ exit
controls.
The only noticable variant of iOS 11's App Switcher interface is on the iPhone. + As opposed to the iPad, the iPhone UI cannot comofrtably display the applications so that + they do not overlap given the width of the screen, so the current or most recently used + application covers the rest of the applications, and the user must scroll to the right + to view the rest of the applications.
+Functionality remains the same in that the user must still swipe
up to exit
+ out of an application and the applications are sorted from right to left by most recently used.
+ The interface is also different in that the Doc and Control Center is not visible.
Efficiency: Accessing and using App Switcher is very easy and efficient. Controls are minimal: + accessing App Switcher only requires a double click of the home button or a swipe with four + fingers. Scrolling to the right to view more apps and swiping up to exit an app is effortless + to most users because of the simplicity and intuitiveness of the interface.
+Memorability: The only issue that may fall under memorability might be + the user forgetting what the controls are to access App Switcher, since there are no specific + instructions or buttons on a mobile's interface. However, since the controls are very simple, + usually users would be able to remember controls after the third time. Something that may contribute + to lack of memorabiity might include different functions in iOS, ie. some gestures include holding + down on a component or button to delete or exit out of something, whereas App Switch requires a + swipe up with one finger, which can end up confusing a user.
+Learnability: Drawing off the points mentioned in memorability, App Switcher is + very learnable due to its simplicity. However, since there are no instructions or buttons, it may take + a user a few times to get the hang of it.
+Errors: To enter App Switcher view, the user can swipe up with four fingers or + double click the Home button. However, to exit the view, the user can only double click the home + button to exit, not use four fingers. One error that may occur is if the user attempts to swipe down with four fingers + in order to exit out of App Switcher view. Additional errors that may arise, since the interface + is motion controlled, can include the user accidentally exiting out of an app while trying to scroll + or accidentally clicking on and visiting an app while trying to scroll or exit.
+Satisfaction: User satisfaction is dependent on the user's personal preferences and + comfortability with an iOS mobile device. However, since the macro view is easy to access, easy to + control, and easy to learn, satisfaction rates would most likely be relatively high. +
iOS 11 App Switcher correlates very well to the Key Characteristics of a Macro View. App Switcher + leverages detail by presenting the reader with a full range of details of what apps are running + on the device as well as any controls they may need to use in Control Center. The arrangement and + structure is very well organized and thought out, as there is no overlap of application windows + and the interface conveys what the user needs to do to carry out any actions. Finally, iOS 11 + Macro View allows users to see a wide range of what is running on the system and empowers the user + with the knowledge and control of everything taking place in the system. +