"Using the mentality of designing Windows software for OS X applications will inevitably fail;
Using the mentality of designing Windows software for iPhone applications will inevitably fail"
The flash of the designer and design team can certainly lead to the birth of a good software, but this flash may bring more uncontrollable content, affecting the overall quality and experience of the software. Therefore, Apple strictly controls the standard process in the management of software product design processes, and tries its best to avoid the impact of these flashes of flexibility on the software. From a rational, quantitative, and interpretable perspective, to standardize the user experience and quality of software.
If you use an apple-specific experience standard to measure the software experience and quality, it is "making users feel very elegant when using the software ".
In general, the iPhone user interface design is divided into four parts:
Platform example: understanding users' usage scenarios and usage habits
Software Product Definition: Define the functional objectives of the software
Design and prototype
Software polishing and Improvement
Coding
The time spent in the design process is definitely not the most. It is usually between step 3 and step 4.
"We make tools and tools make us"
As a product designer, a necessary purpose is to make a standard product and be responsible to users. Users have never been as familiar with designing products because of low quality as you think. The reality is that if the product designer is careful enough to design and polish the product, there will be enough serious users to use and recognize the same product together, thus forming a normal virtuous circle. Duan Mu does not agree with the practices of domestic brain products. If they are not responsible for users, they are not responsible for themselves.
The purpose of software design is to clarify what difficulties should be solved rather than a large set of functions, and provide a specific solution for users.
Define the three basic elements of an application: The difference between the application and other applications, the problems to be solved, and the user base.
What matters is not what we do, but what we can do.