1644: Contemplating My Now Not-So-New Phone

Avid readers (hah) will recall that a while back I jumped ship from iOS to Android when I upgraded my phone. My long-in-the-tooth (relatively speaking, anyway) iPhone 4S was replaced by an HTC One M8, a phone which had received some positive reviews from people I knew and trusted, so I decided to take a chance and give it a shot. It was a good time to do so, since I’d been becoming increasingly disillusioned with many of the apps available on smartphones generally, and as such I wasn’t feeling particularly “invested” in the iOS ecosystem — in other words, there weren’t very many apps that I felt particularly attached to.

So, a little down the line, how am I finding it now the inevitable “honeymoon period” is over?

Well, I’m still really liking it, and the one peeve I had with it — the fact it seemed somewhat prone to random restarts and reboots while I was in the middle of doing things — appears to have worked itself out, and hasn’t happened for a long time now. (Watch it start doing it again now I’ve written this.)

As I noted in my earlier posts, I’m not a hugely adventurous smartphone user these days. There are relatively few things I actually want to do with my phone, but most of them are beyond what a simple feature phone offers — or, in the case of facilities that feature phones do offer, smartphones inevitably do them all somewhat better.

Here’s the limit of what I use my phone for: Email. Texting. Phone calls (only when there is no other option). Calendar. Music and podcasts. Google Hangouts. Twitter. Web browsing. Very occasionally Facebook and Google+, though I don’t use either network very much any more. And, if there is nothing else to do during an extended visit to the toilet, playing a simple, toilet-friendly game like Threes.

That’s about it. There’s probably more I could do with it but I don’t really feel the need to right now, since the stock apps and the few additional ones I’ve installed cover most of the things that I want to do with it on a daily basis. I can communicate with it, I can browse the Web with it, I can take snapshots with the camera if necessary and I can read information on a screen that’s noticeably bigger than that offered by Apple’s iOS devices.

I’ve been particularly impressed by Google Play Music, which provides a number of helpful services, chief among which is something similar to Apple’s iTunes Match service, only it actually, you know, works. For those unfamiliar, iTunes Match (and Google Play Music) is a facility whereby you can upload tracks from your personal music library or “match” existing songs with iTunes/Google’s online libraries, then stream or download them to any compatible device. In effect, this allows you to take your entire music library with you wherever you go, rather than being limited by the storage space available on your phone — though the streaming side of things is, of course, dependent on you having a good wireless Internet connection either via the mobile phone networks or Wi-Fi.

Where Google Play Music differs from iTunes Match is that it’s a lot clearer in presenting its information. With iTunes Match, it was almost impossible to tell which songs you had downloaded to your phone — and consequently available when no Internet connection was around — and which would require streaming. Attempting to download songs often resulted in failure for no apparent reason — and with Apple’s phobia of error messages, there was no way of discovering what was causing the problem. Google Play Music, meanwhile, while having a somewhat clunky interface in a few places — it’d be great to have just a plain list of albums, playlists, songs and that sort of thing rather than the overly graphical, space-wasting interface it has — but at least presents this sort of information clearly. It’s obvious when you’ve downloaded something or if you’d be streaming it when you clicked Play, and, importantly, it’s easy to remove things from your phone once you’ve downloaded them — something which iTunes Match made seemingly impossible to do manually for some inexplicable reason.

So that’s been great, and the other apps I’ve been using regularly all seem to work pretty well, too. All in all I’m sure I’m using this phone to a fraction of its full potential, but it’s doing everything I want it to and it’s doing it well, with my only real criticism of the device as a whole being that the volume control buttons are in a stupid place and are much too easy to press accidentally while simply holding it normally.

1582: My Phone’s Not Called “Mate”

So, an update on how I’m doing with my new phone after several days of fiddling around with it. (Said new phone, if you missed my post from the other day, is an HTC One M8 — my first Android phone, though not my first Android device.)

I’m really liking it! Like, way more than I thought I would. There are flaws, certainly — the phone has frozen and rebooted itself while I was in the middle of doing something rather more times than I would have preferred it to in the last few days — but on the whole, it’s been a great experience so far and I dare say that I am actually starting to prefer it to iOS.

Don’t get me wrong, I’m not going to suddenly become an Android fanboy, largely because I find Android fanboys to be some of the most insufferable fanboys on the entire Internet. Nor do I feel that iOS is now “bad” because of the time I’ve spent with Android. But there are clear and discrete markets for both, and they both do their own thing extremely well.

iOS, like most of Apple’s other products these days, is designed to be accessible, simple and straightforward. I hesitate to say “designed for stupid people” but it’s certainly designed in such a manner that stupid people can’t break it easily. It doesn’t blind you with unnecessary information — if there’s something it can do quietly in the background without telling you what’s going on, it will. This is great for people who panic when they see technical messages they don’t understand; however, on the flip side, it’s less than ideal for computer-literate people who like to know what their device is up to — and if it’s up to something it shouldn’t be (or not up to something it should be).

There are two features on iOS where this is painfully apparent, and as I count myself in the more “computer literate” camp they’d been becoming increasingly frustrating to me.

First up is Photo Stream, a feature whereby you take a photo with the phone’s camera and it gets automatically backed up to your iCloud account and synced to any other devices you’ve also logged into iCloud with. This is, in theory at least, extremely useful for backing up images and just for transferring them from one device to another — from phone to computer, say — without having to faff around with long-winded sync processes or additional hardware. And, a good 90% of the time, it was great. The trouble was, for that remaining 10% of the time it would just not work, and it certainly wasn’t going to tell you why. I eventually managed to figure out that if Photo Stream wasn’t syncing it was generally for one of two reasons (the battery being below 20% or you not being connected to Wi-Fi) but the phone certainly didn’t tell me that.

iTunes Match, the service that allows you “cloud” access to your full iTunes music library from any device, is the same way. A few weeks back, my iPhone simply started refusing to download certain iTunes tracks to itself, which made loading it up with tunes to take on a long trip to be troublesome at best, completely impossible at worst. Again, there was no means of getting feedback on what was going wrong and why some tracks would download but others wouldn’t; it simply wouldn’t do it. Infuriating. But I can sort of understand why Apple chose not to put frightening error messages in there — so as not to scare off the casual, less computer-literate people.

Android’s big selling point is its customisability, and to be fair I haven’t explored that a great deal with my new device just yet — I’ve been largely happy with the stock options so far. It comes preloaded with a standard app launcher and a special “car mode” with big buttons and quick access to music, navigation and other useful features you might need while driving, but I know the option is there for further customisation. I also like how you can have things installed on the device but not visible on the home screen.

What I’ve really liked so far is the notifications system. I can clear all my notifications with a simple tap on a button, or I can also take action on a lot of them right from the notifications feed — reply to a tweet, archive an email, all manner of other things. It took a little adjusting to the fact that the phone doesn’t display messages on the home screen like the iPhone does, but having used it for a few days now, it’s actually quite nice to have the peace and be able to review notifications at your leisure rather than when your phone thinks you should.

Plus there’s the sound. I’m not normally a fan of playing music out of a mobile phone, but the M8 has some surprisingly competent speakers. They’re never going to rival a proper setup, of course, but they’re loud, reasonably beefy considering their size, and they make listening to music or podcasts without headphones while doing other things — housework, for example, or, more relevantly to now, packing — eminently practical. Combine with Google Music’s much better, more stable implementation of “cloud music” than iTunes Match offers along with the ability to put an extra SD card in there for storage and you have a device that is a kick-ass media player as well as a solid communication device, too.

So I’m liking it a lot so far, and I’m certainly not missing my iPhone, which I gave to O2 for recycling in exchange for a little over a hundred quid — not to be sniffed at for minimum effort. Whether or not I’ll stick with Android in the long term remains to be seen, but frankly it’s looking quite positive right now.

1579: “Android?”

I took a bold step and did something very brave today. I… I…

I switched from iOS to Android.

Okay, “very brave” might be understatement of the century, but despite being curious about Google’s mobile OS, I’ve resisted the temptation to ditch the iPhone series to date, largely because I felt that I was too invested in the iOS ecosystem to make breaking free practical.

I pondered this recently, though, and realised that I actually wasn’t all that dependent on the iOS ecosystem at all. I run my mail, contacts and calendars through Google, I socialise through Facebook, Twitter and Google+, I take notes in Evernote and… well, that’s about it, to be frank; I’m not an especially adventurous mobile user these days, largely because I feel that 95% of apps released these days are superfluous, pointless crap that no-one needs.

And so it is that I find myself with an HTC One “Don’t Call Me Mate” M8 Android handset. It’s a rather larger handset than the iPhone 4S I was using before, and it’s larger than Andie’s iPhone 5S, too. I once thought that large phones were worthy of mockery, but having been using the HTC for a day I’m already feeling the benefit of the larger screen size. It’s not a huge amount bigger than an iPhone, but it’s a significant enough difference that things don’t feel nearly as cramped.

Bringing mail, contacts and calendars across was straightforward and easy because I was using Google. The one thing I was a little concerned about was being able to manage my music — something that I have, to date, relied on iTunes for. It turns out that Google’s Google Music service has seemingly been designed for this exact situation, allowing you the ability to upload up to 20,000 tracks directly from your iTunes library to then be available for streaming or caching from anywhere. You can listen to them via the Chrome-based web player, or on your Android phone. There’s even an optional Spotify-like subscription service where you can stream music you don’t own, so as of today I’ve cancelled my Spotify Premium account and gone with Google instead.

There are things to adjust with on the new phone. Not having notifications on the lock screen is very odd having had them for several generations of iOS hardware, but this is more than made up for by the fact you can dismiss all notifications at once from the notification centre. I haven’t delved particularly into the customisation side of things yet, but I understand with a bit of fiddling and tweaking it’s possible to rectify this behaviour if it really bothers me.

There are a few things I really like. The fact that if you download an app and discover it’s shit, you can delete it and automatically receive a refund if you do so within 15 minutes of purchasing. The way apps work together, sharing information much more easily than on iOS. The way the on-screen keyboard does a fake “haptic feedback” thing where it vibrates very slightly every time you press a key. The camera on this particular device is supposed to be very good, too, but I haven’t really tried it as yet.

So far I’m very happy with the new device so far, particularly as the tariff I’ve moved to post-upgrade is, for once, actually a better deal than the one I was on previously. I’m paying the same and getting more cellular data allowance plus “4G” speeds where they’re available, so the overall experience should be superior. I’m looking forward to exploring what it’s capable of further; it’s a pleasant and fun change, and wasn’t riddled with nearly as many difficulties as I was expecting.

But don’t worry. I’m not going to become one of those douchebags who comments on every article about a new iOS app/game and just says “Android?” like a brainwashed parrot. iOS is still great at what it does, and if you claim to be a lover of tech, you should be interested and curious in all the alternatives out there rather than swearing blind corporate allegiance to one company purely because they make the handset you currently own.

But that’s probably a discussion for another day. I’m going to go and lie in bed and fiddle with my phone for a bit now. Or possibly just play Nanaca Crash on it.