Friends who have used Google's Chrome browser know that the "http://" section is removed from the browser's address bar, and that each user responds differently to the change. For example, when you copy the Address bar URL from a Chrome browser, you automatically add the "http://" section to the front, but sometimes it's not like the "http://" section.
There is no "http://" part of the seemingly not a big problem, but the question is whether the retention or remove the "http://" part. This leads to the thinking of this article, for the design of a lot of things and "http://" similar, some dispensable things in the design of how to deal with.
Here's my point: Design is a choice. The key is to figure out what's most important and selectively remove irrelevant content, and all the content you remove doesn't affect the design itself, because it's not important for design! like "http://," maybe what we're thinking about is not about the user, Many users may not care if "http://" exists, as you may not have seen in the Chrome browser when you read this article. "http://" is not the same.
For Google, he chose to use a cleaner, simpler address bar when designing a Chrome browser. Designers in the design also because of the choice of retention and cancellation content.
But for many designers will want to put the user's needs in the first place, whether this requirement is desirable or undesirable, as long as the demand is due to meet. Doing so can lead to complications and expansion of the design. Because as a designer is not to meet the user, we are to think for the user, have the choice of the user most needed content embodied in the design.
Article Source: Tutu Web Design Forum reproduced Please indicate the source link.