The laws of simplicity in high-tech.

Everything should be stated as simply as possible, but not simpler. (Albert Einstein).

Very often, the Internet startups simplicity and convenience are declared as a competitive advantage. We will try to understand what all the same sum, this is the ease of. I will rely on the work of John Maeda, MIT professor.
So, imagine my project and try to apply the principles set out in this and subsequent posts.
The first and most important rule - a reduction of. Initially, when the service comes up with an idea in my head prevails, he quickly acquires more details, possibilities of development, additional functionality and so on and so forth. Provide a service in 3-5 years is good and useful for the formation of a vision and strategy. But starting to develop the first version, it is useful to simplify everything you head and share. It is a law to reduce.

1. 
   Remove all unnecessary. To understand what is useless, try to remove all the general. Try to turn each feature and try to keep only the things without which the service is generally loses its foundation and meaning. All that is in doubt - is clearly unnecessary. By creating a product with many features - you are creating everything and nothing all at the same time for all. On the market there are many examples of products that are able to do a great many things, most of them have been unsuccessful. From a marketing perspective it is easy to explain. People buy your product because of the well-defined objective function and they should immediately understand that this is central to your. That is what you are offering and. At the same time you save the people from the horror of the excessive complexity of the product. The same concerns and the size. It is because of this law, all striving for miniaturization of the product. Small and compact things cause less fear and doubt, and when we find that they know how much it is admired.
   


2. 
   Hide the rest of. Ever notice how close the sockets on the TV set of buttons? . Functions that are necessary, but not used continuously, it is necessary to mask. This relieves stress on the complexity, but a source of satisfaction from the fact that the functions are all the same when they are needed. For example, mp3 players. There are only a few buttons, and the menu and the possibility of much larger, and all can be accessed using a small number of buttons. For software this is done by using the drop-down menu ( optional extra), which appear only when the user is necessary.
   


3. 
   Embodiment (conservation quality). How much would you have not removed the functions and how many would not cut, you should keep a sense of product quality. This can be done using the PR material (eg, due to the mirror surface of the iPod, he seems to hover in the air), functions, and m. Dr.. The quality of public relations in different ways. Werth with diamonds, which is the other with titanium coating, and what you can do with software? . You should focus on that central function ON was performed at the highest level. If you can not make money, create a feeling (from PR to design and usability, all can go to the course ).
   

So, these are the first advice: reduce, mask, embodied. Remove all unnecessary and needed to leave, making it a mega -thing either in fact or by feelings.