Windows Phone vs. Android - Part 1

I've only been using Android for one day, so this is just a preliminary comparison. In all honesty, while it may not be where I end up, first impressions are critical. So here they are.

As suspected, the app condition and platform functionality in Android is better than Windows Phone. Frankly, I knew the app thing would be the case, and I was suspecting the platform functionality to be better as well. There are simply more apps and more premium apps on Android than Windows Phone. Feature-wise, I'm running the Android N Beta on a Nexus 6P and some of that functionality is not technically officially in Android. But I chose this device specifically so that I could have some of those features even if they are in beta and may not stick around.

That being said, it isn't all sunshine and rainbows. Overall performance is worse. And app stability is worse. Gone are the days of the sort of lag where it feels like the screen isn't moving with your finger, but lag rendering is still very apparent in many places. Including the Play Store. Before you jump on me for this complaint, you need to consider that my last device was an HTC One M8, running Windows 10 mobile.

I think that is pertinent for so many reasons it isn't funny. It is also running a beta OS. And where the Nexus 6P is pretty much guaranteed to be an officially supported Android N device, the One M8 doesn't look like it will be an officially supported Windows 10 Mobile device. The Nexus 6P has more RAM, a superior GPU, and, arguably a better CPU with more cores. On paper the Nexus 6P should kick the shit out of the One M8. And, with the M8 effectively trapped on an early internal build of an operating system that Microsoft feels it shouldn't be running, it should be even further handicapped.

The reality however is that Windows Phone and even Windows 10 just run better on mobile devices. The 6P isn't bad enough to complain about. But coming from the other phone it was obvious. And the performance was even better on the One M8 before I jumped to W10M. And I'll note, I noticed the performance lag even BEFORE I updated the Android N.

App stability is another item. I've really only had one app fail. And only since upgrading to Android N. It's Groove Music, and I suspect either MS or Google will fix the issue eventually. Reality is though, I never had an app THAT broken on Windows Phone. If an API broke compatibility the app ceased to be available. Not ideal either, but it impacts perception to have an app you just can't make work.

Offline maps isn't something I used much. But I did use it. And I'm surprised it isn't there. Thankfully I switched to a plan with unlimited internet. If I ever need navigation I won't be screwed. But it isn't the OS affording me that. I can download a map for offline use up to 30 days. But the process is convoluted. I just went and downloaded Here Maps instead on Google. But I don't think that gets me navigation.

Contacts was another pain point. For some reason Android can pull contacts from Google, Facebook, Exchange, etc... but not from Outlook. On Windows Phone, all of those worked. This is just a one time pain, but also one which seems contrived.

I know that was more complaints than positives. But, the goal really was to highlight the things I felt were missing. That is typically what people notice most in the first few days of use with a new OS. And I did say that there were no deal breakers. Android is capable, and for the moment I'm happy with it. The takeaway should really be that at the moment I feel Android is better, but that doesn't make it perfect.

Comments

Popular Posts