Visual Studio 11: New Shades of Grey Have Developers Seeing Red
As part of the recent Visual Studio 11 Beta announcement, Microsoft released details and images of the newly redesigned user interface that will be a part of VS11. Presenting a new interface based on a gray-scale palette that also incorporates a redesign of the familiar toolbar icons used in previous versions of Visual Studio, the new look has quickly generated intense controversy.
Monty Hammontree, Director of User Experience in Microsoft's Developer Tools Division, provided an introduction to the new VS11 on his blog. The new style bears little resemblance to VS 2010, the Metro interface coming in Windows 8, or the ribbon-style toolbars utilized by Microsoft Office. Hammontree explained that his team identified three main hurdles to developer efficiency:
- Coping with tool overload
- Comprehending and navigating complex codebases and related artifacts
- Dealing with large numbers of documents
These items hurdles were based on research conducted both inside and outside Microsoft. Interestingly, Hammontree references a paper of an outside study that uses Eclipse as one example of the problems his team is trying to solve. While the palette and graphical design changes are only part of the solution devised by his team, they are the area generating the most controversy amongst the developer community. Hammontree explains the rationale behind the color reduction as follows:
Allowing for the use of color within content to take center stage is increasing in importance as developers target Metro style clients such as Xbox, Windows Phone 7, and Windows 8. In targeting these platforms developers are creating user experiences that involve the use of bolder and more vibrant colors. These color palettes showcase much more effectively in a more monochromatic tool setting.
Despite the research and well-intentioned explanation provided by Hammontree, developers have been quick to voice their opinion of the upcoming changes. Over 600 developers to date have provided their feedback to date-- to put this in perspective, a cursory review of the Visual Studio blog shows that the typical post receives a number of comments in the low double-digits. The Visual Studio section on Microsoft's User Voice website has seen an entry related to the color-change enter the top ten in popularity after only 4 days.
To Microsoft's credit, they have provided an updated message asking for developers to continue providing feedback and state they are reading all comments- both good and bad. Developers interested in the new appearance should make sure that they provide their feedback to Microsoft as they explore the VS11 Beta that is launching Wednesday, February 29.
use of color within content to take center stage
Not consistent with the rest of Windows
Re: Not consistent with the rest of Windows
Developers Designing Experiences in VS?
I have yet to come across *developers* *designing* anything in VS or "creating experiences". After 14 years in the industry I haven't seen any shift in the production workflow: designers designing something in Adobe tools (Illustrator, Fireworks, Photoshop) and handing off design assets for development. And user experiences are not created in a development tool. It's as if he believes that designers and developers are the same person and that VS will be the sole tool to use in that production workflow.
There are a few UX individuals who understand code and development and excel using something like Blend (which is already monochromatic and supports Hammontree's statement). But there is already a tool like that to focus on designers - let that be the tool. Developers dragging and dropping from a toolbox aren't really designing. Nor are they designing anything if they are developing towards a comp. As a designer and developer myself, I don't want an development IDE muddied with concerns around design. Let tools be focused on the task at hand. I'll continue to use my Adobe tools, pull them into Blend to fine tune the translation of design assets to XAML and deal with animations and state transitions and all beauty that is in Blend. Then I'll use VS for code development.
Re: Not consistent with the rest of Windows
In the blog post, the Visual Studio team says that the choices being made are "thoughtful reductions" to the problem of tool overload. If tool overload is a problem in Visual Studio, then it's an outright nightmare in the Office products. But you don't see the Office team doing "thoughtful reductions". (maybe they should)
If there is a UI best practice that Microsoft believes in, then it seems logical to me that it would be applied everywhere and different UX engineers on different teams wouldn't be allowed to come up with their own choices in isolation.
And if Visual Studio 2016 comes out and the glyphs are gone and replaced by the ribbon, because CEO Sinofsky says so, I won't be surprised.
Just got working with VS11 Beta
VS now looks like an old 3270 terminal but it seems easier on the eyes - less fatiguing. I don't miss color that much although I had thought that I would.
I think the key is "multiple themes". Today there are only gray and black but in future color themes may be added.
Does colour really matter
Re: Developers Designing Experiences in VS?
Bringing more design ability into Visual Studio would be very welcome. I find tools like Illustrator and Photoshop to be overly confusing, especially when it comes to simple things like making an image with a transparent background. It was much easier inside Blend. But I would be jumping for joy if they ever added that ability to VS. I would never need to use Blend.
I envy you thou. You must have created some very pleasant looking software. Currently, I'm mostly making enterprise software at my company, so I just copy the look of SharePoint. Since that is what our intranet is based on. Easy enough.
Keith Adams Dec 06, 2013