Referral links

Unlike other ads on this page, the two links below are to services I use - if you're looking for a new SIM or broadband connection I can personally recommend them, and these are specific referral links that I can get bonuses from if you sign up, so please use them :-)

Get a free giffgaff Sim Broadband from £5.99 a month with an included wireless router when you sign up to Plusnet - terms apply

Saturday, 22 February 2014

Android - if I'm honest, it's a bit disappointing ... 10 reasons

[Short link to this article if you need it - http://goo.gl/ixqxJy - or retweet me]

Another old article - drafted nearly a year ago now but it's time to post it! There is a separate companion article about problems with the device, but this one is about the OS.

DISCLAIMER 1: This is written from a perspective of someone who's bought their first Android device.
DISCLAIMER 2: I bought the tablet because I don't have a laptop, so some of these are issues in using it as an alternative to a laptop to highlight the limitations of doing so.

Now that I've got both of those things out of the way, I'll continue. I bought a Nexus10 because I not longer have a laptop in the house. I figured the stuff I'd do on a laptop would be more practically served by a tablet. For me the disadvantage of any sensibly priced laptop on the market has always been the screen resolution - it's all very well saying you have a 15" screen, but why do  they headlines never list the screen resolution? It's a shame it's taken Apple's "retina" marketing machine to move things forward though. So 2560x1600 for £319? I'll have some of that please ... And I've got an external keyboard for more comfortably writing blog entries and the like. The Surface would have been tempting at the same price point and resolution, but it wasn't good enough in the first generation when I was looking.



So what's the problem? Honestly, there are several. And I'm surprised at quite how many. I'll point out that none of these are related to the specific device (I'll save those for elsewhere) but are just about Android (initially 4.2.x, now 4.4) generally from the perspective of someone using it in lieu of a laptop.

Let's get started:
  1. When you first power it on (or after a factory reset) it won't do anything until it's connected to wifi and registered itself.  If the wifi authentication requires you to type a username/password over an HTTPS connection it will fail (without a useful error) because - as far as I can tell - the clock is set to well before the SSL certificate was valid. So you're stuck until you find a wifi with another auth method.
  2. Partially related to the first point, my second attempt was to connect through the AdHoc wifi network access point provided by my Nokia N9. Except that Android can't connect to AdHoc wifi networks, so that failed. And means I can't use the tablet on the network out and about as I was planning to without pulling some tricks. (Pre-4.4, this Android app lets you tether over BlueTooth although it doesn't work with all apps e.g. web browsers...)
  3. The task switcher bears very little relevance to anything in terms of what's actually live and running. It might as well be a "recently started apps" list. In many cases it's really inconvenient as you lose status because an app restarts when you go back to it, and that effect is even obvious in the standard applications like web browser windows.
  4. A controversial one - lack of flash support in the browser. Now you can find it manually and bolt it on by allowing unapproved software (although only with Firefox/Dolphin) that's miles from ideal. I know there are reasons again Flash but as per this thread and again in this thread (which I posted after discovering they've removed APIs in Android 4.4 that Flash requires - here's an unofficial fixed version).  But I don't buy those reasons and I think the devices are worse off for not having it. It was a differentiating factor Android had and was useful for compatibility reasons. Deprecate it if you like, but I like having it there - and in my experience the UX is often better than a poorly-rewritten-for-many-OSs mobile app. But as I said in that first thread, I'm not entirely convinced the reasons for removing it weren't just political or pressure from media providers ... Music streaming services are an example where you're charged more on "mobile OSs", and bypassing that using the desktop flash version makes it harder to justify. It forces an alternate experience on mobile devices when it's not always necessary.
  5. Related to the previous point on flash and desktop/mobile differences, if I'm using YouTube I'm subject to the limitations put on "mobile" devices i.e. some videos are not playable. Which I believe is the same restriction that stops all YouTube videos playing via set-top boxes/BluRay players etc. When I bought a Sony BluRay player I liked the fact it had YouTube support - but the limitations soon had me building a "real" PVR to attach to the TV instead. On Android you can get the message "The content owner has not made this available on mobile devices". The Puffin browser's Flash support lets me get around that (EDIT: As does Dolphin with the Flash plugin if you set it to identify with a Desktop User-Agent instead of Android) but it's ridiculous that I have to do it. 
  6. Again on multimedia - video streaming apps such as BBC iPlayer, 4OD etc, don't seem to continue to play when in the background. I don't expect to see the video when it's in the background, but the audio could easily continue. That's the experience I'd get on a laptop, why not on a tablet? Maybe I'm switching away to tweet during a broadcast, or while adverts are on (I have no problems with adverts and don't use AdBlock). I just don't want to have everything pause by default as though I can only handle one thing at a time (Sadly the same is true if you bolt on Flash into an Android browser - it will pause when not in the foreground).
  7. The facebook app looks suspiciously similar to touch.facebook.com - I wish they'd make a bit more effort with the app since there doesn't seem to be such a huge advantage of it other than integrating it into the Gallery's "Share" options and the like. And despite what Zuckerberg might claim, HTML5 is quick enough for the purpose. Just ask Sencha.
  8. UMS (USB Mass Storage) has been removed in favour of MTP/PTP for the built-in storage.  The reason for this is that there is no longer a separate FAT block device that can be exported. Fine if you're on Windows which supports MTP. Less fine if on Linux which doesn't always have support for it (out of the box before anyone suggests otherwise!). The reasons are technically sound but a use case I have is being able to put music/video on my device and plug it into my car, or someone's SmartTV, and play it back. And I can't with my Android device. HDMI playback is all well (if a bit of a battery drain) but I'd like to be able to control the playback from my TV remote control. Wouldn't be so bad if the Nexus10 had a memory card slot (which would be exported over UMS) but it doesn't.
  9. I never realise quite how bad this issue was until I started using Android but I'm now sick of the "Do you want to download our app" popups when I go to half the friggin' web sites on the internet. It's horrible. People install AdBlock and the like to get rid of intrusive nonsense but this is far worse. NO I BLOODY DON'T WANT YOUR APP - it's not that hard to just put a banner at the top advertising your app, but please don't intrude on my use of your site.
  10. Device-locked applications. I'm particularly looking at you SkyGo and itvPlayer. Is it really that hard to open up to all Android devices (possibly non-rooted if you must)? And even when they do work, some services lock out the external HDMI port when streaming (4OD explicitly displays a separate message on the external screen) This really doesn't feel like a laptop replacement.


So there you have it. A list of ten things that I really don't like about Android given my use case. About half I knew about before, and pretty much all weren't true of my pure Linux (as opposed to the "Yes I'm Linux but abstracted away by Dalvik" thing that calls itself Android) Nokia #N900. For me, the customer experience isn't quite what I'd hoped for given my use case. I wonder how the Surface or Playbook would do on all of these points?
Don't get me wrong, I don't think Android is inherently bad. It's just that for the use case of a desktop replacement, it is quite some way from perfect, and I feel some of the restrictions are in place for commercial reasons "because we are big market leaders and we can" as opposed to because they're right for the users.

(Don't forget to also read the article in my customer service blog about my experience with the Nexus10 and Google's support)

[EDIT 25/02/2014: Copied from a comment I made on G+ tonight:
I've just tried to stream the #NME awards at http://www.nme.com/awards - it managed to fire up at first but wouldn't go full screen (about 300pixels wide on a 2560x1600 screen is pointless). It now won't restart at all now in chrome. Fired up first time on my Linux laptop via #flash (with a 720p stream). Can't verify flash on #Android tablet because it's 4.4 #usabilityFail Maybe I'm being unfair in expecting it to work on my big brand tablet ... Oh wait a minute ... 

]


2 comments:

  1. Some thoughts on the post. I understand the caveats and I think what that says to me is that a lot of it is about what you were trying to do, and the kind of device you were using?


    1. Not had that, but usually setup at home. Sounds like a bug/design omission that should be fixed
    2. Yes I hit this ages ago, though most hotspots support infrastructure anyway. Certainly my home made hotspot c. 2000 did just fine, so some of the blame lies on the device you were using as the hotspot provider
    3. Yes recently started is more accurate IMO - but I think it makes sense for the average punter.. whilst giving scope for sw providers to achitect their app as they see fit.. of course if it goes wrong... though tbh I rarely end up killing process manually. Usually android does this for me (not responding)
    4. Apple were right. flash was/is a pain. Even when I had flash on my phone in earlier android days (2 gens' of phones ago) I basically didn't use it. I've never felt the need on my current phone. If sites still depend on flash now that adobe have clearly deprecated it then I blame the site, not android
    5. This is basically a youtube/content owners issue. I don't think it's fair to blame the device .
    6. On my samsung s5 I can play iplayer in a floating window. - might be a samsung extension, though multi window etc support is cropping up in the base too I *think* (might be wrong)
    7. Kinda agree - but this is a facebook issue. The new app has a modified layout, quite different. Main potential advantage of app is notifications/offline - though the facebook app isn't great in it's use, and html5 could be better too..
    8. USB mass storage is a problem for concurrent use which is how I want to use my devices. Though part of your complaint is HW specific (nexus 10). My s4/galaxy note 10.1 both have mem card slots, and there are 3rd party apps to enable mass storage mode. I stick with MTP though (on windows)
    9. Must be the sites you go to. I do agree when I see them though
    10. Yep agree, but that';s an app issue

    Didn't really see much there that was android specific, but accept they're a pain for you...

    ReplyDelete
  2. I agree that much of that list is not inherently down to Android itself and many of the issues would affect other mobile OSs, but they do form part of the overall Android experience so how important they are depend on what you're comparing it too. Recent years have shown us that apps can make or break a platform in the marketplace.

    I've discussed the flash issue elsewhere, and while I understand all the reasons I still think that losing the ability to development for a cross-platform runtime isn't a good thing. I don't think we're quite there with HTML5 adoption yet in terms of replacing it. Regarding things like youtube restrictions (and let's not forget YouTube is owned by Google) they are the ones who have chosen to give content providers the option, and I can't help feel that (like with music streaming subscriptions) the "mobile" (since that what Android seems to be classed as despite the fact mine isn't really used that way) devices are being artificially restricted for commercial gain (plus it's worth noting that those restrictions would be harder to enforce in many cases if flash was available on those platforms, so it's demise arguably makes it easier for companies to enforce such absurd restrictions)

    It's #3 that I find the biggest annoyance though - even if I'm just switching between a web browser (for research - it's an issue for me on Chorme and Dolphin) and another app (possibly to report that research) I find that the web browser can often start reloading from scratch. It can be a particular problem if you lose state at some point. All things that add to the overhead of using the platform and drop it's responsiveness. Let's not forget my Nexus10 is a model with 2Gb RAM.

    The floating windows sound good but that does sound like it might be a Samsung extension.

    Note to other readers - Nigel also pointed out to me that the UMS support even for SD cards was removed in the Android 4.4 KitKat upgrade :-(

    ReplyDelete