XCode vs Android Studio: Which is worse?
Updated: Jul 17, 2022
What makes me eligible to review!
I have been in the industry for more than 11+ years now. I started my career with BlackBerry (BB) Development. I feel old already!
Eclipse was our best friend back then for mobile development. I did my internship working on the famous Zagat app for BlackBerry. It was overall a great learning experience.
For my full-time job I switched to a start up named Spinlet which I hope is still going strong. I worked as BlackBerry developer in the beginning but switched to iOS development eventually.
My iOS experience was nothing but exciting in those initial years. Eventually I started my own firm Royale Cheese with a friend that provides mobile design & development.
After around 4 years of iOS development I found my way into Android development. I have got a fair share of experience with Android development as well, around 3 years to be precise.
We have since then been working on full stack. That’s when I realised how horrible the mobile development tools are.
Enough with the chit chat. Here’s an honest review of the mobile development tools and technologies.
It used to be a good tool in the past. But it has become terrible lately. Here is a list of all the issues even after 15 years:
Auto-completion: Firstly, who in the right mind would set Esc as the suggestions key. Secondly, the autocompletion doesn’t work many a times or gives weird suggestions that are out of context.
Build Times: It takes a lot of time to create an archive or to run on a device for the first time. It’s best to setup a CI/CD to archive and upload builds.
Signing & Deployment: With the latest version’s it’s getting easier. But, it’s still confusing with the signing certificates and the provision profiles for someone who is a beginner.
Memory Hog: Somehow XCode keeps on hogging memory. For every new device on which the build needs to run it occupies 3 GB. Archives take a huge chunk and so as the simulators. Overall it occupies around 50GB if I don’t clean up regularly.
Updates: Each update is around 10-12GB even the minor upgrades. What’s worse is it requires more than 40GB of free space to get installed. Last but not the least, XCode takes around 12GB of the space.
Design: Initially to design UI there was struts & springs, then came the Autolayout and now the SwiftUI. It is worrisome that the methodology keeps on changing.
Cocoapods: is getting worse day by day because it’s repo is getting so big. Secondly, it increases the build times by a lot.
Camera: Possibly due to hardware limitations camera was not supported in simulators. But, now it’s been a while. If the location can be simulated why not the Camera?
I haven’t got the chance to use it in the early days. But from what I have been seeing it wouldn’t have been pretty. Here are some of the frustrating issues:
Fragmentation: I feel this might be on top of every ones list. Supporting the staggering amount of devices to support might just overwhelm anyone.
Gradle: Oh My God! Gradle takes forever to run builds. There are optimisation’s which can help alleviate the problem, but it still remains the problem.
RAM Hogger: With emulators and IDE running together, the combo requires around 10-12GB of RAM. That’s way more than what their official documentation says: 4GB.
Signing Keys: You lose your signing keys and you can’t upload to the same app again. You will have to create a new app and get the reviews and downloads again. There is some improvement in this area recently.
IDE: I always felt Java based IDE’s to be clumsy. That includes IntelliJ (on which Android Studio is based), Eclipse or NetBeans. It’s responsiveness is not like other tools like XCode or VS Code.
XCode vs Android Studio Review
Even though it might feel Android has less issues it does have some serious issues. Fragmentation and Gradle might alone be enough to make Android look bad.
Personally I prefer to work in XCode compared to Android since I own a Mac and probably I am more used to it.
Overall both platforms have a huge user base. But, I feel that these tools still have a long way to go.
Jot down your frustrations in the comments below.
Read some of my articles here: