Confessions of an Android developer who uses Apple
As a lifelong Apple user, I expected building Android apps to be a technical challenge. What surprised me was how much of the learning curve came from unlearning years of Apple habits.
I have been an Apple user for as long as I can remember. Every swipe, every settings menu, every tiny interaction, it is all just wired into me at this point. So, when work asked me to start building for Android, I said yes without fully processing what that meant for someone who doesn’t know anything about Android devices and ecosystem.
Three years later, I am still catching myself off guard.
Unlearning a decade of muscle memory
The ecosystem shock did not hit me in some big dramatic moment. It kept going in through embarrassingly small stuff. I remember early on trying to find which Android version was running on my emulator. Simple, routine – something I would need all the time. I opened Settings, looked around, moved between tabs, and got nowhere. Eventually I just searched for it.
That was the moment something clicked. I didn’t just need to learn Android, I needed to unlearn years of instinct.
On my iPhone I almost never use the global Settings search because I already know where everything lives. I built those instincts over a decade without even realising it. On Android, I had none of them, and starting from zero was more disorienting than I expected.
Then there are the three system navigation buttons at the bottom of the screen. Back, Home, Overview. Even three years in and I still hesitate before tapping one of them. iPhone had the physical home button once, and yes, a double press did something different, but that was it, one button, two behaviours, easy. Three separate buttons with three distinct purposes just never fully embedded itself in my brain the way iOS navigation has. I am not sure it ever will.
Building for a device you don't own
The physical device thing has been its own ongoing frustration. My entire experience of Android is through an emulator, which is fine until it is not. Not long ago our QA team flagged a bug. I tested it on the emulator and could not reproduce it, which made me suspect it was a real device issue.
And then I realised, I don’t have an Android device.
None of the test devices were with me either. I had to message a colleague in the office and ask them to check it for me.
Team collaboration is always a good thing, but the underlying reality of not being able to just pick up the device I build for and test something myself is a strange position to be in.
Why people become loyal to their platform
What Android has taught me, unexpectedly, is something about why people get so fiercely attached to their platforms. The platform you grew up with shapes how you expect technology to behave, and those expectations run deep.
Android users navigate all of that naturally, the same way I navigate my iPhone without thinking. Their instincts just point in a different direction. Neither is wrong. They are just shaped by different years of habit.
It made me understand for the first time why people get so attached, almost defensive about their phone of choice. It is not really about specs or features. It is about the fact that one of these things feels like home and the other one does not.
Home Is hard to leave
One moment that genuinely made me smile happened when I had to quickly check something in our iOS codebase. I opened Xcode and it just felt immediately comfortable. Familiar.
I cannot fully explain why because I have not spent significant time in Xcode, but something about being back inside an Apple environment, even a different one, felt like exhaling. Whether that says something about Xcode specifically or just about the Apple ecosystem in general, I honestly could not tell you. Maybe it is psychological. Maybe it just felt like home.
But ask me which phone I would pick, and the answer has not changed. Not even slightly.
iPhone, without hesitation. iPad for the sofa, MacBook for personal use, AirPods in my ears. I am deep in this ecosystem, and I have no desire to leave it.
Building for Android every day has given me genuine respect for the platform and the people who use it. But it hasn’t made me want to switch. If anything, it’s made me realise just how hard that switch really is.
Apple vs Android isn't just a user debate anymore. Explore what Swift's move to Android means for developers.
Looking for something else?
Search over 450 blog posts from our team
Want to hear more?
Subscribe to our monthly digest of blogs to stay in the loop and come with us on our journey to make things better!
