Android Studio is an official Android development integrated development environment (IDE) for mobile application development in the Android operating system developed by Google. Android Studio is based on Jetbrains'
N/A
Azure DevOps
Score 8.1 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Android Studio
Azure DevOps
Editions & Modules
No answers on this topic
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
Android Studio
Azure DevOps
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Android Studio
Azure DevOps
Considered Both Products
Android Studio
No answer on this topic
Azure DevOps
Verified User
Engineer
Chose Azure DevOps
Our company is already using a lot of Azure services and it makes more sense to start using Azure DevOps Services (formerly VSTS) when we needed a CI/CD tool. We tested different features of Azure DevOps Services (formerly VSTS) and found out that the build and release …
Android Studio is a great mobile development IDE. I have found it is the best for both Android and Flutter development. It is created by JetBrains, so any developer used to their products, such as IntelliJ IDEA, will find themselves right at home with this IDE. It is very intuitive so it is a good choice for people needing to learn an IDE quickly.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
Android Studio needs a very high amount of RAM and a high-end processor to run smoothly, which can't be affordable for everyone.
Updates in Gradle files can sometimes come up with a hectic improvement in whole code, which can lead us to improve some code and consume precious time.
Multitasking is very difficult in Android Studio due to its heavy consumption of resources.
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
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.
Android Studio is very useful for developers to write the code of Android apps. It provides auto implementation, suggestions, and removes boilerplate codes, which helps developers write clear and optimized code. Number of third party and Jetbrains plugins available to improve the speed of development and help the developer.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
Overall support for Android Studio is quite good. As the project is maintained by Google itself, frequent updates are usually made to Android Studio to keep the IDE update and bug-free. Many community forums are also available to help developers across the world if they face any issue.
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.
Android Studio is the best possible offering to make android based apps. It's a product by Google and the official integrated development environment for android app development. That's why it is able to offer the easiest to learn and simplest coding environment to developers. But it needs higher performance and is at times slower as compared to Flutter, etc. So that's the only drawback, but overall it's better than most tools for app development.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
Positive Impact: No license fee, saves a lot of money upfront.
Positive Impact: Faster project delivery, because errors are cached quickly while typing code allowing to fix the code at the same time, and this eliminates the need of fixing bugs which saves time. Saves 20% of my time.
Negative Impact: Not works well on low end laptops with RAM less than 16GB.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.
