IOS Human-Computer Interaction Interface Development Guide (1)

We have introduced the iPhone application interface design guide. We will introduce a chapter in the iPhone application interface design guide-Apple iOS application Human-Computer Interaction Interface Development Guide.

User Interface principles

 

Good human-machine interfaces comply with the user's thinking and actions, rather than the performance of devices. A user interface that lacks attractiveness, complexity, or logic will make the original outstanding applications uninteresting. Conversely,

A beautiful, intuitive, and fascinating interface can enhance the functions of the application and inspire positive emotions in the user's mind.

◆Overall beauty

The beauty of the whole is not simply how beautiful the application interface is, but whether the appearance and functions of the application are perfectly combined. For example, an application used to handle actual work usually simplifies the decorative UI elements and places them in the background, and gives the important position to the task itself, so it only provides standard controls and actions. The purpose and features of this app are simple and unified. On the contrary, if a similar app provides an odd and fancy interface, users may not be able to understand it or understand it as a contradiction and absurd.

◆Consistency

The consistency on the Interface ensures that the user can learn from the previous knowledge and experience of using the app. Applications that achieve consistency are not simply plagiarized with others. Specifically, it makes full use of the experience advantages brought about by standardization and model.

To determine whether an application complies with the consistency principle, consider the following:

◆ Does the app comply with IOS standards? Are the built-in controls, views, and icons correctly used? Is it reliably integrated with the features of devices?

◆ Does the application maintain consistency? Is the font style and terminology uniform? Does the same icon mean the same thing? Can users predict system response when performing the same operation in different scenarios? Does the custom UI have consistent appearances and behaviors from start to end?

◆ Is the current application consistent with the previous version? Are the terms and definitions of each version consistent? Basically, has it never changed?

◆Direct operation

When users can directly manipulate objects on the screen, instead of using controls, they are more likely to immerse themselves in the work task itself and understand the operation results. The multi-touch technology allows iOS users to experience the convenience of direct operations. Through gesture operations, users can have more closeness and control over the interface, because they no longer need to touch objects through intermediary media, such as the mouse.

In an iOS application, you can directly perform the following operations:

◆ Rotating or moving devices are used to affect objects on the screen.

◆ Use gestures to operate objects on the screen

◆ The operation results are displayed to users in a visible and rapid manner.

◆Feedback

Feedback is a response to users' operations, making them confident that their requests are being processed. Users want to receive immediate feedback when operating the control. If the operation process is long, they need to constantly update the operation progress.

The built-in application can respond to each user's operation behavior. For example, the list item is highlighted on time at the user's point. After several seconds of operation, a control is provided to display the process progress. If appropriate, additional text can be added.

A subtle animation can be used as a clearly stated feedback to clearly present the operation results. For example, adding an animation for a new row in the list can help you track the change process.

Sound can also provide useful feedback, but this should not be the primary or only feedback mechanism, because in some places, users may not be able to hear the sound, or they close the sound.

◆Metaphor

When objects and operations in an application are mapped from the real world, you can quickly learn how to use the application.

A typical example of software metaphor is folders: In the real world, people place things in folders, so in a computer, Put files in folders can be quickly understood.

An appropriate metaphor does not need to be constrained by the limitations of the real world in terms of use or experience. For example, users can put as many files as possible into computer folders, which is impossible in reality.

IOS provides a huge display space for metaphor. IOS supports multiple image formats and gestures. The user actually interacts with objects on the screen. In many cases, the operations are the same as those in reality. In iOS, metaphor includes:

◆ Press the iPod playback control key.

◆ Drag, flip, and slide objects in the game

◆ Slide bidirectional Switch

◆ Flip a photo

◆ Click the slide selector to select

In general, as long as the ing is not successful, metaphor can play a very good effect. If the folder on the computer needs to be organized into a virtual cabinet, it will become useless!

◆Allow users to control

Allows users to trigger and control operations rather than programs. Although the program can give operation suggestions or warn against dangerous operations, it is not true if the user is completely deprived of the right to handle errors. A good app can give users sufficient permissions and help users avoid dangerous consequences. This requires a balance.

Familiar and predictable controls and behaviors can enhance users' control over apps. In addition, users can easily understand and remember the simple and direct operations.

The user wants to have enough opportunities to cancel the operation before it is processed. In addition, they hope to have the opportunity to perform a devastating operation to achieve their goal. Finally, they want to stop the ongoing operations.