More restrictions, simpler design

The simple rule has mentioned a simple method, SHE: Shrink--> hide--> append, and then arrange the remaining elements organized together. Simplicity means getting the most out of it in the simplest possible way.

First of all, one of the important impulses of writing this article is my new http://www.aliyun.com/zixun/aggregation/9363.html "> Mobile Internet product design Novice in the search for information was too many senior intimidation for a long time, I finally decided to stand up and fight back.

We have seen countless mobile internet predecessors say that the design of mobile internet products is too restrictive for web design and too difficult to make. You see, the screen is so small, when the web side of the mainstream resolution to stay in 1024x768 when the mainstream resolution of the mobile phone is still 240*320 (note I mean mainstream, not to mention iphone4 640*960); we can use the mouse on the Web + Keyboard to smooth browsing and on the phone only the keyboard (touch screen is still gray mainstream bar); When the web design has become too loud to overflow when the phone is still a dream ... okay, that's enough.

But is that the case? I don't think so! I think the design on the phone is simpler than the design on the web.

A smaller screen means that you only need to consider less content design; a single interaction means that you only need to think about simpler information design and more single-threaded process design; more restrictive hardware means you don't have to think about fancy "fake moves" anymore, All you have to do is focus on whether you can help users solve their needs more quickly ...

Generally speaking, the product design of the handset is divided into 2 kinds, from the web end transplant function to the handset end, all starts from the handset end design. These 2 types of designs actually apply the following principles.

First, embrace the constraints, habits in the limited design

This is the right nonsense, and everyone knows that true freedom does not lie in total freedom, and that true freedom lies in the balance between total freedom and restriction. This is particularly true of mobile phone product design. The first thing you have to do to design on the phone is castration, which I once thought was the most important aspect of web design.

The simple rule refers to a method, SHE: Narrowing (sherink)--> hide--> append (embody), and then put these simple elements organized together.

For example, from a web transplant product to a phone end, ① the web already has the function module all lists, the sorting, ② as far as possible cuts, reduces the function which can reduce as far as possible, ③ hides, reduces the irreducible, but is not the essential function hides, ④ considers the handset end user demand and the Web end user demand difference, Then attach some mobile phone-side specific needs and functions to go in; ⑤ organized the above elements in an orderly manner.

This approach is both simple and avoids the loss of an intrinsic sense of value. After such a castration you will find that it is easy to implement these functions in an environment such as a mobile phone, because there are so many unnecessary things that you don't need. In fact, is to use the most core function to meet the relative limitations of the conditions, in the mobile phone product design, the most need to do is to minimize and eliminate unnecessary work. Do what you want, and then do it!

Proper organization makes complex systems seem simpler. For example, the ipod button design goes through one of these processes, in the beginning, the ipod button was designed to be wheeled, and in the third generation the ipod pulled out 4 buttons on the periphery of the turntable and turned it into a row of small buttons, apparently complicating and confusing the ipod's interactions. So in the fourth generation we found that all the buttons were back on the wheel and completely integrated. This is a typical case of simplicity from the beginning to becoming complex and simple.

(Photo source: Tencent Technology)

Second, the Wise know

Over the years it has been on the web, as if product designers felt that if a page they didn't "process" it would seem unprofessional, but it was often more unprofessional. Each design has its core appeal point (central idea) and all the information conveyed, which causes users to be confused and irrelevant to the subject of information is to be avoided. Oh yes, this thing has a professional term called "noise."

The design of the mobile phone needs to be in a fight with the idea of "in case ..., just add it". Do not pay for 20% of the user needs, not because 20% of users lost 80% or more users. The best product experience, I personally think is the most concise way, the most elegant to meet the needs of users.

Three, single-threaded information design

Because of more restrictions, the information on the phone can not be designed as Web Design Unlimited network extension, but must be relatively shallow. Don't start multiple processes on the same page, use clear layouts, exact hints, and more. About this recommendation of onlookers @ Tacit understanding of this ppt.

Well, as you may realize, I did not mention the suitability of more than 12000 kinds of terminals. Yes, this is the real problem, I like you, are very helpless .... However, the user base of each product is certain, perhaps, the problem will be relatively simple after narrowing the scope. Of course, you might think that future iphone machines will become mainstream, but don't forget, that's the future. And, that's the way it is!

Source: http://www.ikent.me/blog/3205