Flutter by Google vs. Microsoft Visual Studio

Flutter is well known for native app development, if you have android studio installed on your system, you can quickly start using it. This might not be the best choice for you if you do not wish to learn a new language, i.e. Dart and you do not know it already.

Incentivized

It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.

• It is powered by Google, so a great technical community is backing it.
• The development of native apps is an easy process using Flutter.
• As it is an open-source tool, we can use it without paying anything.
• It provides nice UI options.

Incentivized

• Rock solid intellisense. For C# and VB.Net code, the intellisense provided by Visual Studio is hands down the best. If you find that you have a hard time remembering parameters of functions, or what object names were, the intellisense will rescue you and help me be an efficient developer.
• Super fast and simple to use debugger for C# and VB. Everything in the debugger is handed to you on a silver platter. When you stop on a break point, it immediately shows you the local variables, the call stack, and even your current memory usage. Setting up watch variables is super simple and you can even make breakpoints conditional so it will only stop on certain conditions.
• Hides the tedious tasks. There are quite a few things like publishing, creating click once deployments, and adding/removing settings in the project files that can be really time consuming when trying to do it by hand (such as if you don't have access to Visual Studio and you need to make changes). Visual Studio hides all the tedium from you by making nice point and click interfaces to get things done quickly.

Incentivized

• Occasionally updates to the Flutter SDK result in wide-sweeping changes that seem to not be thoroughly tested and considered. Flutter sometimes evolves too fast for its own good.
• While the 3rd-party Flutter package ecosystem is vast and rich, 1st-party support for basic things (audio/video playback, battery information, Bluetooth services, etc.) are lacking. You are occasionally forced to rely on an open-source package for use-cases that other platforms have native support for.
• Documentation, particularly around testing, is lacking. While there are some great docs, like the Dart Style Guide, many Flutter-focused support documents are lacking in quality and real-world usability.
• Flutter allows you to architect an app however you want. While this is a great feature, it also adds complexity and leads to the current state of Flutter's state management, where there are 50+ options on how to organize your app, with very little official guidance or recommendations from the Flutter team. For a beginner, this can create decision paralysis.

Incentivized

• Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
• Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.

Incentivized

VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.

Incentivized

The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.

Incentivized

Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.

Incentivized

I have experience with react and React Native. I would say that the idea behind all those frameworks are quite similar. However, I found the javascript-based frameworks a bit more accessible as you could utilise your javascript knowledge. Here, Flutter works with its own language. This has advantages and disadvantages sometimes. I found the community around javascript frameworks bigger and therefore sometimes more helpful. However, Flutter does a good job here as well. I think the main argument for Flutter is its usability for less experienced developers. If you do not have knowledge in javascript or other programming languages then I think it is much easier to start with Flutter than with another framework like react. I think the package that you get form scratch is better than in the other frameworks were you have to set up and learn a lot more before you can start.

Incentivized

I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.

• The rapid development capabilities of Flutter allow us to build apps we could not have previously considered commercially viable, opening new revenue streams.
• Free and open licensing made adoption very easy (ie. free/low cost!).
• In comparison to Qt, our time spent arguing with build tools and perfecting development environments has decreased substantially.

Incentivized

• Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
• Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
• When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.

Incentivized