Redesigning the New Project Dialog



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.


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:


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.

Pratik Nadagouda

Program Manager, Visual Studio

Follow Pratik   

Adérito Silva 2019-04-29 14:45:07
Hi! From my own experience, I find it more confusing and time consuming to create new projects with the new dialog concept. I was very happy with the old dialog. I would love to get it back as it was or, at least, something that works in a very similar fashion.Thank you and keep up the good work!
Juri Ryazanov 2019-04-29 15:50:09
I liked old new project dialog more. New one is confusing.
MgSam 2019-04-29 16:24:08
How is lower information density in any way better? This new dialog just ensures that most developers will only ever see the top 5 or so project templates and that the rest of them may as well not even exist. Sure, maybe they'll get to a code window faster, but it significantly reduces the chances of them finding a more relevant template. I appreciate the work you guys put into the product but it just seems like way too many of the features you build are just bike-shedding. Surely your telemetry must tell you that one of the things developers spend by far the most time doing is debugging- and the debugging experience has barely changed in 20 years. You guys need to look at OzCode and bring those sorts of features into the core product. And the C# interactive window should be integrated into debugging- the Immediate Window is a crippled experience in comparison.
Sergey 2019-04-29 18:10:45
I absolutely positvely hate the new dialog. You say your design goal was “Get to code quickly with the minimum necessary scaffolding and help developers configure their application with the right settings”, if so, you missed a mark by a mile. Prior to this new disastorous effort I could get a quick snapshot of all project types, narrow it down and start a new project in no time. Now once the endless scrolling of the list ends, I could hardly remember what was at the top of the list. So I'm gonna ask, what was the point of fixing what wasn't broken in the first place?
Karl Shifflett 2019-04-29 19:10:41
Pratik, please don't be offended, but this dialog is unusable.  Please restore the one from 2017.  Don't spend another minute trying to fix this thing, it's a UX nightmare for customers.  This thing is a huge waste of time.   Just put it out the door, impossible to discover information and besides I don't have 5 minutes every time I need to create a project. Karl
Joseph White 2019-04-29 19:23:25
The new dialog looks like an interesting experiment but it takes ten times as many clicks to create a new project. This does not get me to code quicker! 
Y Zhang 2019-04-29 21:52:17
The new dialog is really bad! It's confusing and I have to click next/back while the dialog in 2017 is just one-page. I hate this dialog so I switch back to 2017. I hope you notice that the new dialog is just an unmitigated failure.
hitesh davey 2019-04-29 22:34:24
VS2017 new project dialog was more than perfect in comparison with 2019 dialog! There was no need to reinvent the wheel. MS could have used their manpower to improve something else but not new project dialog. If you provide an option (2019 simplified style & 2017 advance style); then your telemetry data will show 99% of the developers (except MS emps) switch back to use the old style dialog for sure.
Alexandr Golikov 2019-04-29 23:35:35
I agreed with all above  That new dialog may be have more functionality, but in the same time it's not intuitive and time consuming. Old one was better.
Darren Talbot 2019-04-30 00:16:21
I have to agree with all the other posters.  The new dialog is terrible.  It is just information overload. The screen is so cluttered yet actually contains less information. That is a real skill to pull that off. I do not need the clutter of the Tags and Template Description under each and every template title. It just hurts my head trying to filter out the unnecessary information. It was so much better and quicker with the tree at the left, the template list (Titles only)  in the middle and the description at the right. Also, why does it look like a different application? It looks like a monochrome web page pop up instead of part of a supposedly professional desktop application.  Those combo boxes are really disconcerting too.  Instead of working like combo boxes have worked since their inception, these ones clear as soon as you select something.  I thought it was a bug and kept selecting my choices hoping it would finally "stick". I also dislike the requirement to go "Next" when previously I could access all options on the same page.
Karel Král 2019-04-30 00:36:00
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 2019-04-30 00:37:03
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 2019-04-30 01:41:43
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 2019-04-30 04:41:02
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 2019-04-30 05:43:42
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.
Scott Paist 2019-04-30 08:16:26
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!
Cockram, Darron 2019-04-30 09:02:08
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 2019-04-30 09:31:01
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.
anonymous 2019-04-30 10:43:57
This comment has been deleted.
Dean Jackson 2019-04-30 10:46:33
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
Glenn Watson 2019-04-30 10:49:46
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. 
Jon Davis 2019-04-30 12:31:13
I'm fine with a modal dialogue in response to a user action (File -> New Project, etc) but it is NOT OKAY to shove a modal dialogue in the user's face at launch and after closing a solution. First time I saw this and the menus in the main window weren't responsive I thought VS was glitched and used Task Manager to force VS to exit. As a sanity measure, I have created an extension called VSStart to open the Start Page (File.StartPage command) at VS launch and when a solution is closed. Couple it with Tools -> Options...-> Environment -> Startup -> "Empty environment", and VS 2019 behaves more like VS 2017. Unfortunately I have not managed to get the developer news feed to run, if it's even still baked in there.
Jon Davis 2019-04-30 12:33:28
"If it ain't broke, let's fix it!"
Anthony Cool 2019-04-30 14:24:30
I actually like the new New Project dialog box.  Yeah, it may take a few clicks the very first time you go to use the template you are accustomed to using, but then it's in the recently used pick list after.  So, that basically solves a lot of the complaints here.The one thing that DOES need to happen though is:- Upon app startup, you see a "Continue without code ->" option under the "Get Started" listing.  When I go to close my solution, and the Start screen appears again, the "Continue without code ->" option should still be present as something we can choose from.  It is missing at this point in the UX. - Also, if you are going to show the Start screen after close of solution, close out the main IDE application behind it when it is to appear. - Also, if you choose to leave the main IDE application open after close of solution, ensure the solution's you just closed local git repo information isn't visible or accessible after you've already closed the solution and the Start screen appears atop the main application.  VERY VERY tacky and incomplete looking and feeling.
Peyman M. 2019-04-30 14:46:46
I think speeding up startup with a new dialog was a good decision and Get started items are handy but Create new project should have been first item don't you think? for me Search-first approach is very painful and I'm not comfortable with it at all. That prototype looks very good and mix these the new one with prototype might make it better.
Neal Culiner 2019-04-30 14:57:25
User Research? Really? I absolutely DESPISE the startup screen in both Windows and even more so VS for Mac. Count me in on wanting an option to revert please. 
Jerry Greening 2019-04-30 17:50:23
So far in my expierience with VS22019 I have to agree with several other here and say that the new Project Dialog is the absolute worst and most confusing thing about about VS2019. The old dialog was, for me at least, by far faster in picking a new project type. Now instead of wasting time on the filters or searching through the convoluted an unorganized mess of project type icon with vague descriptions that is contained below it, I find myself just using the recent template list to select what project type I want.
James Alexander 2019-04-30 17:58:50
All the people complaining about the new dialog are likely the same people that get upset when the menu changes at Applebee's. Took a few days to get used to it but now I'm digging it. I especially love that it brings to focus the types of projects I've recently used. One request though, please add project searching to the 'Open Recent' dialog that shows when you start VS 2019. I thought for sure I saw an early build where this was there but it'll hands down be my favorite thing if it makes it in.
anonymous 2019-04-30 18:25:36
This comment has been deleted.
Emran Hussain
Emran Hussain 2019-04-30 18:26:04
The new dialog is a disgrace to the legend of Visual Studio. In a Tree structure, we could easily see what are my options under what platform. Now I need to 'KNOW' what project I need to create. Totally disappointing. As others have already expressed the frustration, I don't have much to add. Please count me to the group who wants the old dialog back.
Likun Zhang 2019-04-30 19:12:59
New dialog boxes are more laborious to use
Soft Works 2019-04-30 20:19:05
I rarely comment on any blog posts. But that dialog is an incredible disaster and one of the worst changes I've ever seen since VS 6.0. This decision making the same mistake as MSDN docs did a few years ago, thinking that a navigational tree would no longer be needed and could be dropped - first completely, later replaced by some crippled "tree" showing only parent nodes but no siblings. A few years later, and now we're back to having tree navigation again - because when reading structured documentation, it's just naturally the right way to visualize the structure and the content's position inside the structure. Similar applies to the "new project" dialog: With the hierarchical structure in previous VS versions, you always had a great overview about what's even available. For example, when you wanted to create some kind of web application, you navigated to the right node in the hierarchy and you could see all options that are available (installed). When using search, you never know - you never can be sure that you have seen all possible options, because you might just haven't entered the right search term. You are talking about the level of confidence that users would have about making the right choice. With the new dialog users will never be confident about their choices because there's always a chance that there could have been a better choice that hasn't been among the search results. I bet, this dialog has made a great appearance in internal presentations where the presenter tells about how they analyzed user behavior and enters selected search terms from which he knows exactly about the results that they are producing. But in practical use - when you don't know what exact search term you would need to enter - it's a totally different situation. With regards to some other comments, I don't think that this is a matter of taste or of different kinds of users like some prefer this and some prefer that. This is just about different approaches: Sometimes a search is the more appropriated method for accessing certain content, but in other situations it is required to access that content by structural navigation. You may have improved search, but taking away the structural way of accessing new project templates was a very wrong decision. Please revert that. It doesn't have to be the 'old' dialog, but it should include the navigational way of accessing project templates like it was possible over the last 2 decades.
Eugene Kuchynski 2019-04-30 22:17:22
Maybe new dialog is worse than old, at least now. But I think this subject doesn't deserve so much noise at all. In the morning, when I launch VS, I just continue to work on yesterday's project. And when rarely it's needed to create new project, both dialogs work well. Instead, when VS is launched, it's interesting to see what's new in the world of development, new technologies, extensions, articles, etc.
Fares Eidi 2019-04-30 22:44:01
I also find the new menu unusable and the worst part of VS 2019  Drastic changes in user experience are risky and users often prefer a way to revert back to ''classic view' Admittedly it is well intentioned and usage of telemetry to drive UI enhancements sounds like a very good idea.... but clearly isn't
f q 2019-05-01 00:13:13
Please bring the old new project dialog back. The new one is wasting our time.
James Walker 2019-05-01 01:03:13
This looks horrendous. Please stop making changes for the sake of it to a product which is relied on for professional work. You claim to have identified a problem (too many top-level categories, although I've never found it so...) and then, rather than trying to solve it, just given up and passed the baton to the user! The new interface seems to pass all responsibility to the user... there's no obvious guidance whatsoever on what templates you have installed, and the bizarre decision to prioritise search is just absurd. If you claim users can't figure out what template to use (unlikely, they're devs after all...) forcing them to search for something they can't identity isn't going to help! Now we have to guess the name of the template we're looking for and push through a two-screen process just to create a new project, instead of clicking a simple Category name and filling in the project name. You've made it harder, more time consuming and more confusing. Please stop redesigning core UI elements that have served perfectly well for years... This isn't a real problem despite what your "telemetry" might claim. Did you actually ask any real users before embarking on this... you can't keep on citing vague "telemetry" benchmarks as the motivator for major change with no option to restore the old UI. This is totally uncalled for and seems to be the result, once again, of a self-styled "UX team" saying "remove everything, making it search-based will make it 'simpler'". We're devs, we need functional, not simple.
monkey noises 2019-05-01 01:11:43
Sorry, but "search first" only works when you "know" what you are looking for. It doesn't aid discoverability, especially when you are not aware of the possible options that are available.....and "show me everything" actually gets one in a worse situation than before, as there is no structure to build a picture of "collections" of project/template types.....just a "list of results" to scroll throught . Thus, this puts a mental load on your memory on having to know/remember the right combination of search terms in order to "find" what you want. To make matters worse you have "simplified" or rather obscured details about certain project classifications. For example, a developer that is focussed on purely WIN32 app development, now has that hidden.....they can't search on keyword "WIN32"'s all lumped under a generic "Windows" classication.....which makes it more difficult to distinguish from other types of "Windows" applications. The same with "ATL" least searching for "ATL" brings back one project in the search results but only by accident due to it being used it in the misses the other possible ATL project template types.  By making this change, and not providing the ability  to "switch" back to the old layout/ have dis-invested developers muscle-memory in project creation....learned over a long period.
Steve Hurst 2019-05-01 02:15:54
Why waste time on this, this is retro step in my book , your efforts should be focussed on much more important areas of productivity gains  such as  refactoring, managing references, renaming projects and folders across solutions. While I am having a rant,  it would make more sense to rebrand the package manager console  I fear that its  solely responsible to manage nuget packages been superseded , for example  I spend more time  running Entity framework commands in a nuget window  which is counter intuitive.  
Джон Шепард
Джон Шепард 2019-05-01 03:35:06
I deleted Studio 2019 preview just because of the that terrible New Project dialog box, it's just awful. This is an unsuccessful experiment, the old dialogue is quite great. Please restore an old version, the new dialog looks like as if it is inserted from a completely different type of user interface (tablet) so, it's really useless on the PC. What's the point if most of developers still use the mouse and keyboard to enter the program code? So, you need to adapt everything in UI to classic input principle.
Oleksiy Gapotchenko 2019-05-01 04:26:31
Sorry to be that guy, but I have to admit that the new dialog is a mess. It -kind of- does the search, but it misses the important aspect - discoverability. Let me try to look at the dialog with the eyes of a beginner: what should I search for? An endless linear list of stuff does not help either as it causes an immediate information overload. Buzz words as a categories do not help either. Developers do not look on things that way. IoT, Cloud, Service meh. Despite my countless attempts to get used to it, I had to turn that dialog off and now I start from a blank VS 2019 and then go to File -> Recent Projects and Solutions route. Welcome back to 1999. On a side note, VS 2019 also killed a Blue theme by making it purple, and thus hardly usable. Judging from the Dark theme choice in the latest blog posts, I think everybody tends to passively agree on that. Even you cannot use the new Blue (aka Purple) theme. Dark is the only sensible choice now. So what do we have in VS2019? Two clearly regressive changes (new dialog and theme). Lot's of unfixed stuff from previous versions. And tons of new bugs that makes it barely usable. Back in the day such versions were called alpha versions. But you say it's a release. Go figure.
Edward Chmiel 2019-05-01 06:45:03
While I will reserve judgement on the UX design until I play with it a lot, I think you are missing the fundamental problem. That problem is non-familiarity with the various types of projects. Example: "Pig Application" and the description "A project for creating a Pig application." That is not at all helpful! Never never NEVER simply restate! In other words, I have no idea what a Pig application is, what its for, or anything. A simple link on the description that leads me to a basic understanding page is what is needed, and badly. How can I experiment if I have no idea what I am experimenting with? Having to go out to the web to find out is time consuming and inhibits experimentation. TIA 
Eric W 2019-05-01 08:48:21
Can't search for something if I don't know what it is. Please give an option to toggle this feature on/off. Also, does this affect the Add Item dialog (from Solution Explorer?)
Mirza, Muhammad Saleem 2019-05-01 18:10:15
New UI remindes me Windows 8 without start button. I'm not sure who is behind new UI but that person is not sincere with Microsoft. Step closer to failure. congratulations!! Please bring back old UI
Enrico Fichtner 2019-05-02 02:14:35
I'm wondering if folks @MS (e.g. Program Manager) ever read the feedback of their customers. If so, this 'New project' dialog should disappear silently ... and most important very soon! I was willing to buy the new version (Professional) but ‘features’ like these upsets me so much – that I rather stick with my 2015 version. Also, a bit ‘off-topic’ … the new icons for ‘Step into’, ‘Step over’ and so on (Debug) have changed how many times over the years? I’m sick and tired to adapt to new icons just because someone felt it looks a bit ‘fresher’ …  
Hitesh Davey 2019-05-02 05:23:28
VS2019 New Project dialog box is a serious usability BUG than a feature. You are expecting the developer to search something which he is not sure about. Can't search for something if I don't know what it is. Please give the option to toggle this feature on/off. There are so many project temples available and they are easily discoverable at a glance in VS2017 version just by clicking on any tree node. In other words, you don't have to search. In VS2019 new project dialog box, how would a developer know if some new templates are available? Kindly note that your MOTIVATION for new project dialog is DE-MOTIVATING rest of the developers at large. So without wasting more time and resources, pl restore the original, more productive & discoverable VS2017 dialog box. This would be a great help indeed!
Jose Vales 2019-05-02 05:45:50
The new dialog concept is much more useless
Scott Lundstrom
Scott Lundstrom 2019-05-02 06:16:34
I will agree with the majoity here. I wish an option would have been provided to still use the previous dialog. The new one feels crowded and confusing. 
Tim Stephansen 2019-05-02 09:04:54
I appreciate the effort in trying to make things easier for developers to use. However, I find the new project dialog to be much more difficult to use than the previous one.
Arpad Stoever 2019-05-02 10:55:41
Maybe it would be helpful to add a save filter oportunity so that users can save one ore even more filter combinations to avoid selecting all the same options over and over again. Or even better - simply add a possibility to create a user defined project type list and I only would need to switch to all project types if I need to add an additional project type to that. That way every user could create his own list of choices that he usually uses. 
Eugene Ivanoff 2019-05-02 11:22:58
I agree with commenters above. The new dialog is a catastrophic usability disaster. Period. Please, at least make this new dialog as option and bring back old dialog.
Allan Nielsen 2019-05-02 15:35:14
I think everyone has voiced their legitimate opinions here and in a few feedback items.  If it HAS to stay, could you at least save my preferences in the combobox like language.  When I work in C# I am letting the dialog know I dont want VB.  The next time will more than likely be the same choice. What is it with microsofts continued investment in the failed "Metro" theme?  I don't get it.
Titus Thobias 2019-05-02 17:24:26
Please remember that Visual Studio is a developer tool. On an average, developers spend few minutes in their entire developer life on creating a new project. Instead of redoing things to help improve that few minutes, that effort can be spent on adding/improving the features that really matter to developers. Thanks!
Bob Noordam 2019-05-02 22:30:36
I have written many UI parts for our internal CRM, and have removed something more then once after a 'great idea (tm)' turned out to be an actual downgrade for the users. This new startup experience and creation dialog is one of those cases. Get rid of it, live and learn.
Giang Nguyen 2019-05-03 04:28:56
Can't wait for the day the developer can choose the new project dialog the way they want it (with new design or old one). Thanks for the efforts aber in my opinion the the new design is very unproductive. At least one should be able to resize the dialog to see more.
Jack Bond 2019-05-03 14:02:13
Wait, someone put thought into this dialog? Ahahhaha. I thought it was written on a toilet seat five minutes before release. Want to speed things up? How about adding the concept of FAVORITES. I do maybe THREE types of projects now. Gee whiz in less than eight seconds I came up with something better than this disaster. Oh, and who the F**K writes a fixed size dialog box in 2019? They should be FIRED, as should as program manager that didn't notice that in the FIRST EFFING ALPHA. Let me be blunt about this, that's probably you Pratik.
Peter Bille Larsen 2019-05-05 06:50:20
The new dialog is not useful for VS. It's a great usability concept, but when creating a project I need to see all the different templates and possiblities. Now I have to guess, which template to use, because they are hidden from start. Old one back => soon as possible.It's like a road map, where all the streets are hidden, you can only find a street by typing its name, and since you don't know the name, you can never use the map.
SuperCocoLoco . 2019-05-06 07:52:12
The new Project Dialog is the absolute worst and most confusing thing about about VS2019. The UX design of the new dialog is, like Sype 8, a completely unuseable and ugly nigthmare. Visual Studio users are desktop users, not tablet or mobile users, but Microsoft are obsesive creating mobile/tablet/cloud UX design for desktop computers, like Windows 8 or Windows 10. Please, get back and restore the old new project Window dialog and the Start Page.
SuperCocoLoco . 2019-05-06 07:52:40
The new Project Dialog is the absolute worst and most confusing thing about about VS2019. The UX design of the new dialog is, like Sype 8, a completely unuseable and ugly nigthmare. Visual Studio users are desktop users, not tablet or mobile users, but Microsoft are obsesive creating mobile/tablet/cloud UX design for desktop computers, like Windows 8 or Windows 10. Please, bring back and restore the old new project Window dialog and the Start Page.
Nitin Sawant 2019-05-08 23:01:26
the new dialog is BS, cant choose the version of when creating project. how do I switch back to old dialog?
Nitin Sawant 2019-05-09 09:17:33
no bueno, You added new dialog OK but why remove the older one? it was good new one is not at all good how do I switch to older version of the dialog? I am not able to select android API level version when creating Xamarin forms application
Chuck Ryan 2019-05-12 11:07:05
Well I finally got around to setting up my laptop and installing VS 2019 16.03 and took a good look at your new dialog. Next I played around with it for a while, trying various filtering options and looking at the list of project templates, closed the dialog and opened Send Feedback to search the feature reuests. I attempted to upvote one and add a comment but it always locked after clicking submit, so I came here. Serious question, is there some kind of contest going on inside the VS dev team to see who can create the most rediculous feature? The dialog is unreadable. The scrolling is so choppy that I cannot follow it with my eyes. The filtering is confusing and many project types seem to be missing from where I would expect to see them. The dialog is fixed size. What were you thinking when you created this? As far as the various responses you are making asking how this can be improved, it cannot, it is total garbage and needs to be disposed of.
Pratik Nadagouda 2019-05-13 09:46:22

Thanks for all the feedback folks. We totally hear and understand how the dialog doesn't work for your use cases. Designing something new is an iterative process. We are actively reviewing suggestions and working on improvements in the experience. We want these to target the functional usability issues that you all have brought up. Here's a list of suggestion tickets on Developer Community related to the new project dialog. Each of them has a design concept that proposes a solution to the usability issue. We'd really appreciate if you engage with the suggestions through your votes and comments. Thank you!

Problem: Too many clicks to use filters

1. You can see the active filter value within the combo boxes for language, platform and project type dropdowns. Clicking on it will display the dropdown and allow you to change the filter. You can clear all filters at once by the 'Clear filters' button on the top right.

Problem: Can't see enough templates

2. You can toggle an option that removes the descriptions from the template list so you can see a condensed list view with just title and tags.

3. You can resize the dialog by dragging the edges in order to see more templates in the list. By horizontally dragging, you can expand the recent templates list to show the top tags for platform and project type along with language.

Problem: Filters don't show relevant results

4. In the default filter dropdown, you first see the categories of tags for templates you have installed above a line. Below the line, you can see other available options that you can click on to install the templates and toolsets required for them.

Problem: Hard to find newly installed templates

5. After installing new templates through a Visual Studio component or extension, you open the new project dialog and see the new templates are floated to the top of the list with a 'NEW' label on the template itself and the filter dropdowns that have new templates. 

6. You can toggle an option that sorts the template list by 'installed date', 'alphanumerical', or the default (popularity)

Problem: Recent templates list filled with unwanted templates

7. You can pin templates from the recent templates list or from the main list onto the recent list through a single click star. You can also reorder and remove recent templates from the list.

Problem: Difficult to browse through templates

8. You can see all the filters in a single view which overlays the template list by clicking on the 'Filters' button.

Problem: Zero results on searching

9. You can optionally see other suggested results below your main results list that are related but outside of your search and filter constraints. These can also include available templates from other VS components not installed or the online marketplace.