Soft media: I just recommended "Win8 Summary: Discussion on Windows 8 Ribbon Design". It seems that everyone's enthusiasm is not very high. Is the article too long? It is a bit boring to read, but if you contact the recent Windows 8 series news, there will be another experience; Xiao Bian still recommends reading it with peace of mind, you will get something. Below, the design discussion about the Metro style of Win8 is coming again. Friends, are you really reluctant to read such summative articles?
This article is still from the Building Windows 8 blog, the president of Microsoft Windows, Steven Sinofsky (Seven Sinowski).
Metro Style
The debate around Metro is undoubtedly due to the posting order of blog posts. We are not sure whether we should introduce more abstract concepts or more specific concepts at the outset. Since 6 million people have watched a video presentation about the Windows 8 user experience (this is a fairly in-depth presentation), we believe that readers have a general understanding of the user experience. It now appears that this assumption may not be very realistic. We also learned that even if we have a lot of background information, it is still difficult for people to get a complete understanding before actually contacting the software. Before actually using the product, people tend to have a good or bad impression. For this example, I am pretty sure that the dissatisfied people account for the majority.
in many of the comments, people will focus on focus on the Metro, and I want to set forth a graphical user interface elements, namely Aero comparison with the Metro. We have seen a clear definition of the two, people think that Aero is outdated, and Metro is in the ascendant. As a result, there is a strong desire for an existing Windows experience to be reinvented or redesigned in Metro style. Most of these comments focus on the "old" or "new" style or appearance. Often, these details of the visual style are determined later in the engineering process, but we mistakenly believe that this is well known. If this is stated in advance, the debate on this issue will be greatly reduced.
result of many discussions ultimately depends on the perception of Metro gave rise. As mentioned in the previous blog post, when we look at the Metro style of Windows 8, we see far more than a single color visual effect and fewer controls (less commands). What we are seeing is a brand new platform that revolutionizes Windows. For Windows 8, Metro style means a new type of application that automatically adapts to and optimizes for the current (most popular) platform. This is an important topic that we will explore on BUILD. You can watch video #1 to learn how Metro style apps work. On BUILD, we'll discuss the features of these applications and the tools and languages they need to develop them. We're talking about a powerful platform that provides comprehensive support for all types of applications, including media, social, gaming, and office applications. We believe that the platform still has huge potential to be discovered. Another concern
this topic desktop. The concept of the desktop varies from person to person. For some people, the desktop is where the important documents are stored (the most important folder). For some people, it is the explorer window (application) used to manage files. For some people, it's a metaphor, even Windows itself (toolbar/workspace, menus, MDI/SDI, etc.). For some people, the desktop is an "always running" application, and their Windows experience is limited to opening files or starting menu items (for example, some people spend most of their time using Outlook, Word, Photoshop, AutoCAD, or other Business application). For users who primarily browse the web, the concept of the desktop is even optional. "Open market" approach
interface is always unique elements of Win8. We have followed the way people use and adapt to the Windows API to bring a unique experience to the market. In any environment, the only "desktop" experience cannot be determined. Of course, in the past there have been criticisms that "Aero" cannot achieve uniformity or consistency, even in Windows.
A desktop-like application in Windows 8, you can choose whether or not to use it, or to what extent. Some people think that accessing the desktop feels "very awkward." In my opinion, if you accept a diversity or experience for a specific task or purpose, this is no more awkward than switching between any other application. Today's websites (and mobile applications) no longer pursue consistency across different carriers or applications, and browser shells rarely take steps to prevent abrupt effects when switching between tabs (or applications). Our platform is compatible with applications with palettes or toolbars, full screens/windows/MDIs, built-in controls, or custom controls. The mechanism to achieve this diversity is part of the inheritance of the desktop. Some people want higher uniformity or stricter regulation. I was involved in building early Windows tools, so I know that we have tried this. Even on the best-in-class platforms, developers will strive to differentiate and build user experiences for specific purposes, and the experience will be separated from versatility. Versatility is a solution used to deal with complexity, but nowadays, we are surrounded by different types of digital experiences, and we are accustomed to it (as if with the advancement of technology, people gradually adapt to various Print format and video format). The question we need to solve today is whether these designs can work in the context in which they are targeted.
Such diversity gives us reason to believe that access to the desktop from the Metro style will be very smooth - as smooth as now switch between applications or websites. We'll orchestrate at the top level to ensure a seamless transition, so you'll see that many of the original mechanisms will still work, such as switching between applications, application snapshots, and even switching between applications using ALT+TAB And the desktop itself. The animation will still work. Copy/paste will still work. Even bridging between "legal" control panel applications will work.
As I said, there are a lot of content on the subject for discussion. I would like to talk about the specifics of some of the feedback and introduce you to some of the things that happened to me and to other members of the team as I read these feedbacks. I think we need to do more in product demonstrations, and we may have misrepresented some information prematurely, but we have learned these lessons and are constantly improving our work.