Human-Computer Interface
The first question is what the definition of haptic feedback and why it is needed. The second is to define the various types of human memory and the impact of the same on the human/computer interface. The third is to describe the potential outcomes of not using consistency in the human/computer interface. The fourth question is to summarize the steps of the user-centric design process. Finally, the role of human motion in the design of the human/computer interface shall be articulated. All of the questions above will be answered using no less than four scholarly resources.
Haptic Feedback
Haptic feedback is when a computer or system provides feedback that is something other than visual in nature when something occurs. One of the more pervasive examples of this in motion in a modern context is the slight vibration that a smartphone gives when a button on the phone is pressed. Rather than just, or sometimes instead of depending on the features and configuration, a phone will noticeably vibrate when a button is pressed so as to provide feedback that that the input was received. The "back" button on the Galaxy S4 (and many other phones) would be a good example of a real-world iteration of haptic feedback (MobileBurn, 2014).
That all being said, haptic feedback is sometimes just a feedback/preference sort of thing but sometimes it is very necessary as it is a non-visual means to provide feedback and this can matter greatly if the user of a phone or other device with haptic feedback enabled is blind. Other times, it is simply something to enhance the experience. Vibration feedback on game controllers would be an example of this. Haptic feedback is often referred to as "haptics" and the two terms are interchangeable (MobileBurn, 2014).
As for the different types of memory, there are basically five different...
Those four types are procedural memory, emotional memory, semantic/episodic memory and procedural memory. Computers that are designed to interact with humans on any level, which is all computers directly or indirectly, are designed to resemble and become human interface devices, or HID's for short. These devices take on many different forms such as microphones, keyboards, touchscreens and biometric scanners. All of these input devices have one or more purposes that allow a person to interact with, input information into and extract information from a computer. Humans must harness their memory to interface with and harness computers and the computer is designed, in a much more procedural and static form, obviously, to interact with the person or persons interacting with it at any given time.
As far as how lack of consistency can hurt the human/computer interface, the implications and bad outcomes are not all that hard to see. A computer must output the same result for the same situation at all times. If it is not, then something is obviously wrong as either the system is not configured properly or it is malfunctioning on a software and/or hardware level. Humans have to do their part as well as changing up how a thing is done can throw off a system although any good software should have contingencies built in for normal variances in the use and wielding of a program. In the end, computers are much more rigid and predictable than humans, but this is not a hard and fast rule all of the time. The use of things motion, haptics and other human to computer interface properties is not an exact science and imperfections can abound for a number of reasons. Indeed, the initial hard drives and computers in general were crawling slow as compared to those of today and motion-based or even haptic technology was next to none (if not zero) in the early days. However,…
