Azure DevOps Services vs. Codemagic

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

For companies currently investing in Flutter app deployment, the CD/CI automation that Codemagic brings to the table is a game-changer. Its decision-making process needs to consider all the architecture in place and in a common scenario with other programming frameworks, the initial investments can seem high. In this sense, Flutter will reduce programming staff needs as you can attack multiple target environments and platforms easily, and at the same time the effort to get it working on app stores is now improved thanks to the focus Codemagic gave to support the FLutter community in targeting this solution to ease the process. If you invest in Flutter, you have to invest in Codemagic.

Incentivized

• Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
• Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
• Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.

Incentivized

• Flutter Apps
• Deploy to appstores
• Build test apps
• Easy to scale up once ready
• Has extra seats and team settings, through paid options, to support the prior.

Incentivized

• Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
• Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
• Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
• With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
• If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade

Incentivized

• One more seat available for free accounts, for the first year or trial.
• Improved and simplified secrets management to avoid security leaks.

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

I have used the Slack channel without any problems, and I have gained a lot of feedback from using this tool. I have also been invited to provide reviews for the app before but in an "informal" manner, and using their own channels via Slack.

Incentivized

Was not part of the process.

Incentivized

Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.

Incentivized

The steps to get Codemagic up and running are nothing compared to implementing a Jira solution and after using the CI/CD options it has enabled. For larger organizations that already have Jira, you might gain in the long run from features like automatic issue tracking and focused CI to remediate and test the apps. But if you are looking for true AGILE development, where you have teams that focus on value and need the CD process done easily, then Codemagic is a much better solution for emerging projects and companies to start.

Incentivized

• Increased dev team efficiency through more streamlined development processes and task automation.
• Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
• Better collaboration between the dev team, business analysts, and agile project managers.

Incentivized

• Reduce steps and time to deploy flutter apps
• Cost of build
• Invest in other areas of the architectural process to enhance the products built.

Incentivized