Android Studio vs SourceTree: What are the differences?
Developers describe Android Studio as "Android development environment based on IntelliJ IDEA". Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready. On the other hand, SourceTree is detailed as "A free Git GUI client for Windows and macOS". Use the full capability of Git and Mercurial in the SourceTree desktop app. Manage all your repositories, hosted or local, through SourceTree's simple interface.
Android Studio and SourceTree are primarily classified as "Integrated Development Environment" and "Source Code Management Desktop Apps" tools respectively.
Some of the features offered by Android Studio are:
- Flexible Gradle-based build system.
- Build variants and multiple APK generation.
- Expanded template support for Google Services and various device types.
On the other hand, SourceTree provides the following key features:
- Full-powered DVCS
- Create, clone, commit, push, pull, merge, and more are all just a click away.
- Review your outgoing and incoming changesets, cherry-pick between branches, patch handling, rebase, stash, shelve, and much more.
"Android studio is a great tool, getting better and bet " is the primary reason why developers consider Android Studio over the competitors, whereas "Visual history and branch view" was stated as the key factor in picking SourceTree.
According to the StackShare community, Android Studio has a broader approval, being mentioned in 928 company stacks & 691 developers stacks; compared to SourceTree, which is listed in 618 company stacks and 414 developer stacks.
What is Android Studio?
What is SourceTree?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.
The Expo SDK also provides convenient features like Facebook login,
MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/
As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.
Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.
Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.
After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.
After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.
Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.
GitKraken is the best git client so far. The user interface is very friendly. Everything is easy to do with this tool. A branch tree vizualization is very clear. I've tried SourceTree and I got lost in such many panels. Also performance of SourceTree is not as goot as GitKraken. I like Sublime Merge but it doesn't have so many features as the other tools. I've choosen GitKraken and as bonus I got GitKraken Glo that is the next perfect tool.
Tower appears to be between GitKraken and SourceTree in detail, but gave two scary error dialogs when attempting to merge resulted in a conflict. Doing the same in SourceTree just worked and showed the conflict in its handy file view that's always visible (unlike Tower's mere "Merge branch 'X' into develop" message when the commit is selected).
Both GitKraken and Tower lack the commit hash in their history overview, requiring one to select a commit to see it.
GitKraken appears to be the only Windows 10 Git GUI suitable for night shifts, but like Tower is only free for 30 days, unlike SourceTree.
It is pretty neat and stable. I find very few issues with it.
This software provides a good base or platform on building apps and has great features.
I prefer this software since it gives me more options in building my app and has no restrictions.
mainly use for building and debugging android projects. used it to test builds out of both unity and ionic. used the plugin version back in the day when i was developing the android app at my startup.
Android Mobile Application is partially developed with Android Studio (UI Component only) The core is developed with Xamarin.
PrometheanTV provides SDKs for Android devices and utilizes the Android Studio DE for development and testing purposes.
Android studio is the best platform for app development & screwing around with the code Also very user-friendly
Experience with Android Studio in the context of Android Development. Mostly using Genymotion as main emulator.
Used by various PrometheanTV technical staff to interface and interact with the Git Source Control service.
Since being familiar to git CLI, I nearly never open it again except using it as a diff tool.
Used Source Tree to maintain version / commit / pull request , merge of codes for a team.