The official source of product insight from the Visual Studio Engineering Team
When we started planning the first truly integrated version of Visual Studio (prior to that Visual Studio was predominantly a collection of tools boxed together) we wanted to help developers get started with the new version. To do this we introduce a common start page for Visual Studio.
Figure 1 Visual Studio .NET – Implemented as a set of vertical tabs down the left hand side
The goal of this start page was to provide a location, available when the product first started, for the user to either find out about Visual Studio or to easily get back to what they were working on. We also added some other features to this start page such as the ability to inspect the XML Web Service endpoint you had created and access to community provided online information. Users also had the ability to set their profile from the start page to enable them to shift through key bindings and window layouts. This was because our research at the time showed that over 60% of our customers used multiple Microsoft development tools and each of those had a different binding/layout so we wanted it to be easy for users to make Visual Studio feel comfortable.
Figure 2 For Visual Studio.NET 2003 the start page focused primarily on the MRU
By 2003 we had heard from developers that the most useful things we were showing with Visual Studio.NET was the project and solution Most Recently Used (MRU) list and the online content. For Visual Studio.NET 2003 we removed the tabs that people weren’t using and the new start page focused on the MRU, online information and the user profile.
Rendering the start page in HTML made it easy for people to create their own start pages but that led to some issues. As the start page used the same engine as Internet Explorer, users could find themselves with their anti-virus tooling triggering on the display of the start page. Additionally performance was starting to be a limiting factor and we saw more and more users changing the tools-options setting to turn the start page off so that Visual Studio would load faster.
Figure 3 With Visual Studio 2005 the start page was changed to Win32 and extended to include RSS content
We decided for Visual Studio 2005 and Visual Studio 2008 to implement the start page as a custom Win32 component and to display dynamic content only through RSS to decrease the exposure of the start page to threats. We also moved the profile selection into the first start experience as our customer data was showing that people were still using multiple tools inside the IDE but that were no longer switching profiles as much. All of this made the start page faster but it now cost a lot more for us to modify the start page to present new information or to adopt a more modern look.
Figure 4 Visual Studio 2008 introduced very little change from the previous release
We had introduced the Windows Presentation Foundation with Visual Studio 2008 and were moving many of the visual components for Visual Studio 2010 over to it. It made sense for us to adopt WPF when we renovated the start page in that release. One of the requirements that we needed to address was the growing number of platforms that Visual Studio could target and how we could most efficient provide introductory information about them to users.
Figure 5 By moving to a horizontal tab model the Visual Studio 2010 start page could include much more information
We addressed these requirements by using a multi-tab model that presented the relevant platform information in specific tabs. We also had data showing that developers had moved well away from using Visual Studio as their RSS reader so we turned that off and moved it to a background tab to improve performance. With this renovation we also increased our instrumentation of the start page to help us as we moved forward.
Additionally the move to WPF enabled us to bring back start page customization and the Visual Studio 2010 SDK included a custom template for start page development.
Figure 6 Visual Studio 2012 saw the introduction of video content for Premium and Ultimate
The introduction of the Premium and Ultimate editions and the increased functionality of the tooling they provided led to the creation of a number of “How To” videos that were eventually included on the start page. Based on our telemetry, many of you like these a lot as we’re seeing downloads approaching 950,000 per month.
All of that leads us to where we are today. Visual Studio 2013 RC brings a new look for the start page focused on information that people use. The most popular topics on the Visual Studio 2010 start page were the “What’s new” topics by an order of magnitude over other topics in the Getting Started and tabs. Other tabs had much lower usage but “What’s New” remained a clear leader over other tabs. Customer data also showed that over 30% of our users preferred opening recent projects by going to View-Start Page and then clicking on the MRU over using the File menu commands. Also the number of users who turn the start page off via Tools-Options had now become a small minority of users.
Figure 7 Visual Studio 2013 provides direct access to dynamic video content, announcements and the various Dev Centers
In Visual Studio 2013 we aimed for a cleaner look to the start page that makes the acquisition of information easier. The videos in Premium and Ultimate, for example, use easier to see icons that group related topics. Videos are surfaced through an RSS feed that we can update new videos that could previously only be done as part of a Visual Studio Update. Detailed platform information moved to the platform developer centers where developers were already going for in-depth information. This way you can see the “What’s new” together with all the other supporting platform information and sample code offered at that site.
Figure 8 The "What's New" information can be moved out of the way once you're done with it
From looking at our data we believe that, while the “What’s New” information is used more than any other information, it seems to be less frequently used longer term (it tends to be read only once or twice). However it lives in the most prominent part of the start page’s middle column so there is now an option to relocate it to a less important part of the start page. Lastly, the new start page now uses the system’s default browser instead of the one in Visual Studio. This gives you a higher fidelity experience with the site that you’re viewing.
With this start page we have removed the information that isn’t used, made the videos & announcements dynamic and delivered a generally cleaner look. For the next version of Visual Studio we’d like to hear from you about what you’d like on the start page, for example:
· What information would you like us to display (including non-Microsoft sources)?
· If we made it extensible and customizable would you use it? If so, how?
Let us know what you’d like to see (or what you absolutely don’t want to see there) and also please download the RC of Visual Studio 2013 and try out the new start page. You can let us know by creating a suggestion on User Voice (in the IDE category) for the community to vote on or by commenting on this post. If you find a bug please use the Connect site to let us know.
Tony Goodhew – Program Manager, Visual Studio IDE Services
After the better part of 19 years spent in Visual Studio (and precursor tools) Marketing, Tony decided that he should either make a career of it or try something new. He joined the IDE Services team as a Program Manager in early 2012 and has been working on Visual Studio extensibility and the Visual Studio Industry Partner Program since then. While not known for enjoying pina coladas and getting caught in the rain, his version of paradise would include a cheeseburger.
Since the link points to UserVoice in a generic way, without a section for Start Page suggestions, let me comment here instead.
Mostly I turn off the page now because it's pretty useless to me.
First, ignoring any specific feature, the start page must be responsive and quick and not block switching to any other view while it's retrieving information. Please re-read that 20 times over if you must before proceeding. It's not as much sarcasm as frustration.
Start page, what would *I* like to hook into? How about...
* worklist assignments (either connecting to a program, an outlook task list, or a database table.)
* Issue tracking view (of course this just wouldn't connect to TFS but JIRA, FogBugz and any other major bug tracking software)
* Latest code check-ins both to an overall repository/project, as well as a subarea that I'm focused on.
* An area with the latest pertinent KB articles links to the technologies I work in and care about.
* Links to ASP.Net/MVC videos, channel 9 content, newest Pluralsight videos. (Which I use more than Microsoft videos)
* A simple RSS reader (which honestly could work for a lot of what I am suggesting here.)
* Maybe even a way of playing my favorite MP3 playlists, given that a lot of developers spend a lot of time attached to headphones if they are lucky.
* How about a view of my inbox from the last 3-hours and the meeting coming up in the next 3?
* A little stand-up task pad (what have I done since last time, what do I plan to do, any roadblocks)
* Latest available major downloads in Dev tools, browsers (including the "competition" such as Chrome, Firefox, Safari, Opera)
* A way to search code-snippet repositories.
And rather than making it the start page, how about making it a detachable dashboard or even a standalone application (DevelopView) whose view can be embedded as a start page?
Mostly I'd just like the damn price to come down. I understand Microsoft's desire to monetize Visual Studio, but you are losing the next big platform badly (mobile!) Tools for other platforms are basically free, and don't even point me to the watered down editions. Visual Studio is worth $500 if you are offering the best tools as you do in the Ultimate edition, but you charge $10K for a subscription model I don't want or need.
In case it's not clear, I'm suggesting not putting all of that on one page, but rather creating those widgets and let everyone choose which widgets they want on their start page.
I worry that you base many design decisions on data collected through the "customer experience improvement program". I have never met any professional developer who enables this.