What are the basic rules for designing a good mobile app?

Now we are talking about developing software for mobile devices and developing software for Web pages, michael Mace, one of the founders of usertesting, a user-based research company, gave a speech (in the past, Apple and palm were responsible for marketing and product planning respectively, this section describes the user survey results of mobile products.

Michael Mace first shared some basic rules. For example, the design principle on the mobile end is not to copy the web version, but to forget what happened on the web page, think about what problems people will encounter on the mobile end and what solutions can you provide.

The specific content is as follows:

First, it lowers the user's threshold. In fact, Michael Mace uses the word "fear ". He said that according to their research results, many users have some fear when they use a mobile product for the first time, mainly from three aspects: whether the account will be stolen by hackers, whether the account will be registered at risk (whether the privacy will be affected), and whether the information entered is not noticed will be synchronized to the social network.

"So from the moment a user opens a software, they need to present something that they trust, such as a choice, especially after your product is linked to a social networking site, A clear description of the use of user data on social networks is needed." At this point, Michael Mace uses any. do, for example, boast that this website is doing well at this point-they have a saying "your tasks will not be linked to your Facebook account in any way. "(if you don't agree, your schedule will not be associated with your Facebook account under any circumstances ).

The second and most important thing is not to confuse users. What puzzles users includes functions that users cannot understand, hidden functions, slow speeds, and insufficient feedback when users are found to be "trapped" by these functions.

Michael Mace believes that there are several reasons for these problems: "products are intended for most people. You cannot expect 80% of the mainstream people to be the same as 20% of the people who understand technology and design. Radical technical enthusiasts will make the product extremely complex, because they are designed to be the same as 20% people ." Another reason is that in product design, interactions such as appearance and sliding are often placed on top of functions.

What should I do?

"Never sacrifice functions for good looks", Said Michael Mace,The most important thing to develop a product is to provide functions to address user needs, followed by aesthetic feelings.

To avoid user confusion: "When you feel that interaction is troublesome, use text instructions to avoid complicated multi-level menus. If you can, try to provide demo in appstore, more importantly, we always need to set up a mechanism to help users and get feedback when they have problems."

Finally, Michael Mace mentioned that when developers perform user testing, they should not only understand the data, the logic behind them, but also the reasons for user behavior, "They accept and love the product, so that users can tell you why they like and dislike it. On this basis, you can think about what else you can improve."

Link: http://www.yixieshi.com/ucd/14070.html

Keywords: Interaction Design | interaction design | mobile product design |