Redesigning the New Project Dialog

Pratik

Last week, we released Visual Studio 2019 version 16.1 Preview 2. If you have the latest update – awesome and thank you. If not, you can download it from the link above. Or, if you already have the Preview, just click the notification bell inside Visual Studio to update. This post discusses one of the most visible interface changes we’ve made in Visual Studio 2019 – the New Project Dialog.

Motivation

In Visual Studio 2019, one of our main objectives was to help you (both new and experienced developers) get to your code faster. You can read more about this journey in the blog post that discussed the new start window. One of the most common ways to start coding in Visual Studio is to create a new project.

The dialog hadn’t changed much since 2010, and the interaction model between folders and items has been in place since Visual Studio .NET back in 2002. We hadn’t put much time into the New Project Dialog because we believed it largely served its purpose. Until recently, we didn’t have the telemetry in place to be able to analyze how this dialog was used. Our initial hypothesis was that most of you interacted with the dialog rarely. And instead you spend much more time modifying projects you had previously created. After a bit of user research and analysis, we found that the latter holds true. But we were quite mistaken about the former. Many of you use the dialog to create new projects to try out new things or add on functionality to existing solutions a lot more often than we thought.

User research

We then dove deeper into the data, particularly looking at the usage patterns from new users of Visual Studio. We found that there was a surprisingly large drop-off in usage after launching Visual Studio to opening a project to start coding. That led us to the hypothesis that the New Project Dialog might be somehow inhibiting success with the tool. So, we expanded our user research and gathered that this dialog was presenting you with too many concepts, choices, and decisions. The process of getting started with your code wasn’t straightforward enough. The hierarchy of the nodes wasn’t consistent. When you installed several workloads you would see too many languages and technologies presented at the top level. Further down into the second and third level of nodes, the taxonomy became quite unmanageable with differences in naming conventions of categories.

When we asked participants in our usability studies to search for code scaffolding to get started with certain types of projects. We saw them click around through the top level nodes, and not click through the hierarchy. Sometimes they completely ignored the structure on the left and focused just on the default list of templates in front of them. What surprised us was that even for experienced developers, some of the options weren’t intuitive. Most couldn’t pinpoint the link to ‘Open Visual Studio Installer’ when the templates they were looking for weren’t available. They glazed over the search box without interacting with it. They seemed to completely ignore the recent templates list. And when they finally selected a template, they lacked confidence in their choice.

In addition, we learned that most of you think about your app type first but there are some who think about languages first when finding templates to start coding. It became clear that this mixed structure wasn’t intuitive for either use case. The barrier to the first actions within Visual Studio was too high. And this was a problem that small UI tweaks weren’t going to solve.

Design principles

During the design and development of Visual Studio 2019, we looked at usage across different areas of the project creation process and honed down on a core design goal –

“Get to code quickly with the minimum necessary scaffolding and help developers configure their application with the right settings”

Remove unnecessary choices

There were several options in the dialog box that we sought to remove as a way of simplifying the set of decisions you had to make. We first cleared out the rarely used toggles to sort templates and change icon size. The checkbox to create a git repository provided little value when creating a project. Our research told us that the right step for git init was either before project creation when you create the local folder or after project creation when you know you want to move ahead with the project. You can now do this in one click through the ‘Add to Source Control’ button in the bottom right of the status bar.

The last option to go was the ability to view and download online extension templates through the dialog. You can also do this through the Manage Extensions dialog in the Extensions menu. So, we eliminated the duplicate behavior to reduce cognitive load while looking for templates. After all that, our design looked something like this:

Search-first

But through design studies we found that this still wouldn’t lead to success. The node structure was still too convoluted to be understandable in early usage. We initially wanted to flatten the tree so that there was less digging and clicking to do. But we soon realized that with the overabundance of supported project types, it was an exercise in futility coming up with a single taxonomy that supported every single template. So, we decided to fundamentally shift the way users could discover templates. The search box had low usage in the old dialog box because its position made it a secondary function. But search is a prominent discoverability mechanism across the industry. So, we wanted to improve the way Visual Studio utilized search to help find what you need.

Our early studies saw participants gravitating towards the search box when we changed its position. But there was still a slight hesitation before typing something in – “what do I search for?”. This led to the realization that search cannot be a catch all, and there needs to be a little more guidance. We took the values we knew from the old dialog’s node structure and saw that they roughly fell into three categories – ‘languages’, ‘platforms’, and the more vague ‘project types’. So we introduced filters and tags as secondary mechanisms to support search. Browsing through the tags in the template list will help you discover the different capabilities of Visual Studio based on the tool-sets installed in your instance. Setting filters will allow you to narrow down the list to your preferred choices when starting with a new project.

One decision at a time

We also broke up the process into two separate screens. There is a single decision point on the first screen – select a template. And all the interface elements direct you to make that choice. The second screen is all about providing details about the project type you’ve selected. You can modify the values here or move through the project configuration screen without changing anything since all the recommended defaults are set for you. Some of the more complex project templates then open a third screen which has custom options specific to that project type.

Looking at the template list itself, we made a point to sort this list by our most recommended project templates for the workloads you have installed. So, the template that you should select if you aren’t exactly sure what to do would be the one placed higher in the list. We found that most of you don’t use more than 10 different types of templates, so we’ve made the recent templates list even more prominent than it was in Visual Studio 2017, so that you can get to your most common templates without having to search for them.

Looking forward

This is the first iteration of a new design paradigm we’re trying to adopt for Visual Studio. We’ve been measuring adoption and engagement since the launch of Visual Studio 2019 earlier this month and we’re happy to see a significant increase in success rate through the get to code journey. But at the same time, we acknowledge that the evolution of the experience isn’t over just yet. We’re continuing to listen to your feedback and learning from you to ensure success. We’re on the path to make improvements to search and filtering as they are now the key functionality to finding the right templates. In addition, we recently built in the ability to add tags to your own custom templates. If you’re a template author, find out more on how to update your templates in this blog post. We released this functionality as the result of your direct feedback, and we thank you for it. But we are looking to do better and could use more of your help. Please continue to share your feedback through the Visual Studio Developer Community.

119 comments

Comments are closed. Login to edit/delete your existing comments

  • Karel Král

    I am developing 10 years in VS and I am really angry about the new dialog. I know what type of project I want to create but I cannot find it! It takes me 10x more time to find a project I want to create.

  • Kurt Pruenner

    I’m sorry, but the usability of the New Project dialog took a monumental nosedive with this “search first” mess – if you had just kept the tree/list structure and added the ability to filter that via the new fields it would have been helpful, but this? This is just plain unusable to get to what you want.

  • Weijie JIN

    Hello, sorry but to be honest, it’s mess. You discarded the “category” concept of that screen. In previous screen, I can also search project template if I like. I have to say this change is very bad design and decision, waste of time, just like other “invented requirement”.

  • Andy Weston

    I agree with other posters that the new UI misses the mark by a lot and is much less useful for me.  I sent my Feedback immediately.
    More intriguing to me though is how can all of the research, thinking and hard work that went into this change be so far off from what people actually want? Were people really asking for this change? or was it just a cool design project for the team?  Developers do this all the time as well, we add some fancy new feature that we think is cool but in reality, doesn’t solve any particular problem that a real user was actually having.

  • Mike Diack

    I have already raised many of the following points with Nick Uhlenhuth, because John Montgomery did NOT address this feedback on his blog posts about 2019. I’m currently waiting for feedback from Nick…1) Once again, the posts below confirm – this is change for change’s sake – noone below was asking for these changes, and for those of us who’ve used VS for years, this means we now have to relearn stuff – that’s NOT a timesaving…2) Why oh why oh why, have you “fixed the VS 2019” project creator, when there are regressions in the VS 2017 wizard (Update 8 and later – yes that’s right they are steps backward), that cause the VS 2017 wizard to generate non compileable code. Go and look at it in the VS 2017 bug list – it’ll be marked closed because some Microsoft idiot thinks that just because a regression has been introduced in teh stable build, it’s fine to leave the regression unfixed, just as long as it’s been fixed in a completely new version of the tool (VS2019).If I sound angry, I am. VS 2017 has been abandoned with major breakage, much of which got introduced in Update 8 and 9 as REGRESSIONS (i.e. new bugs that weren’t present in UPDATE 7 and earlier), and the bugs closed as fixed, just because they’re fixed in 2019. Look into my emails with Nick. Look at the bugs being closed on VS 2017 with NO fix in VS 2017 for compiler crashes, broken preprocessors, wizards that create uncompilable code etc.

    • Nick UhlenhuthMicrosoft employee

      Hi Mike, sorry to hear about your experience with the compiler regressions in VS 2017. We will be porting compiler fixes to a 15.9 update soon. We are also looking into the Wizard issue that you mentioned, and while we don’t have an ETA yet, it is something we are investigating closely.

  • Scott Paist

    I think the new dialog is an improvement. I type what I’m looking for into the search box and the template I want is listed. “console”, “winforms”, “wpf”, “asp”, “report”. All there. Keep up the good work on 2019!

    • Matt Downing

      Lol, yes, all you have to do is research on the internet all the available templates, then e.g. type 8 simple key strokes for “winforms” for the one you want.  So much easier than one mouse click on a prepopulated tree.

  • Cockram, Darron

    I’d echo the comments about the new dialog being a backwards step in usability. There was nothing wrong with the start page and I would much prefer to at least have the option of using it rather than having the modal dialog foisted on me.
    Given the majority of the messages here (and on other forums I’ve seen) are of a similar mind that it is a retrograde step are there any plans to address the concerns?

  • Bruce Davidson

    Can we have a way to opt out please. I find the new dialog gets in the way and is very distracting. Perhaps people who dont know how to start their project may find it usefull.

  • Dean Jackson

    I also think that the 2017 version (and going back to 2012 and longer) was much better.  There was even a “recent” section at the top left that already had the recently-used templates, and even better, the last-used template was already hilighted/selected when opening the dialog.  The treeview of languages, and categories under each language is much better.  Also, why would you need to go to the next screen of the dialog just to provide the project name and location on disk, when the older dialog already has that on the same screen ?

  • Glenn Watson

    I am in the group where I am not a fan. 

    It has some good elements where it shows more relevant information with the project type nodes. 
    I think a big issue is you’re trying to show still hierarchical information without a tree which makes it harder to navigate. Having a series of combobox filters to try and manipulate just is confusing and also much slower.