2015: The Year of Android

I don’t often make predictions, but I’m willing to make this one: 2015 is going to be a huge year for Android. I’m not talking about the Market Share Wars, I never cared for them and Android won them long ago. I have little interest in the Who Makes The Most Money Wars either, I’m often baffled as to why people even care. As a developer and user of mobile platforms I’m more interested in app profitability, quality and diversity. I think 2015 is going to be a huge one for Android in this regard. Don’t believe me, ok, allow me to walk you through why.

Let’s start off with a myth: “No one makes money on Android”. I hear that all the time. The irony of the fact that we make 80% of our daily income on Android doesn’t escape me as these people wax eloquent about how this is a well established fact. Let’s start with facts:

In fact, since last year’s I/O, we have paid out over $5 billion to developers on top of Google Play. It’s not just the volume of this number, but the rate at which this number is growing. It’s increased two and a half times, from $2 billion the year before. So we are seeing tremendous momentum. We are very excited, because it directly translates to developers building their livelihood on top of our platforms.

- Sundar Pichai – SVP, Android, Chrome, and Apps, Google. Google I/O 2014

In other words in 2013 Google payed out $2 billion to developers on Google Play. In 2014, $5 billion. This is a growth rate of 2.5x since last year. The lazy way to analyse this would be to point out that Apple announced that they’d paid out $15 billion to developers in December of 2013. 15 = 5 x 3, case closed. We could argue all day about growth rates, profitability and which platform is ‘winning’ right now. The real thing I pay attention to as a developer is this: can you be profitable on Android? To me the clear answer, with many years of actual revenue flowing into our company is an emphatic ‘Yes’. The next question would be: “Is the platform growing or shrinking? Where will it be in a years time? 2 years?”. The answer to that is obvious too: “It’s growing explosively, Google are paying out more money, selling more phones and improving things at an exponential rate”. Long story short, if you make a great app on Android you stand a good chance of being rewarded for your efforts.

The next thing people often throw out is “Oh but it’s so fragmented, I could never bring myself to buy 300 phones and test on 1000 screen sizes!”. This too as it turns out is a mostly a myth based on a lack of understanding. Firstly screen sizes on Android are actually less fragmented on Android than iOS. If you don’t understand why, or don’t believe me then you need to read this, followed by this. Secondly platform fragmentation is largely not a concern anymore. If you launch an app today you can target Android 4.1 and above, and have access to far more users than the entirety of the iOS platform. If you really want to go Android 5.0 only, you can do that too. All of the Nexus devices, as well as high profile ones from LG, Motorola and many others are currently seeing Android 5.0 being rolled out to them.

So if I can convince you that there’s money to be made, that fragmentation is not as bad as people think it is, what’s left? To me the next most important thing is how the App Store on the platform works. On iOS we’re starting to see things like this on a daily basis:

And that’s just the high profile developers. I shudder to think of how many small developers, with no contacts in the media are just being crushed on a daily basis. Do I see those things on Android? Nope. The only place I’ve seen Google crack down is on apps that download from YouTube and apps that do nefarious things. The first is against YouTube’s TOS, clearly so, and the second is obvious. I can’t tell you just how refreshing it is to push ‘publish’ on a brand new app or update, and see it in the store an hour later.

As 2014 draws to a close I’m rocking the gorgeous 2014 Moto X (Black front, orange accents, leather back), there’s a Moto 360 on my wrist and a Chromecast stick in my bag. I may be completely wrong about 2015, but something tells me I’m not. Come to the dark side fellow developers, we have cake.

History Is Written By Storytellers

Have you ever listened to a podcast where someone interviews a founder of a company, and asks them their origin story? More often than not they are really interesting, full of quirky little details and unexpected events. If you haven’t, well you’d best get started with a podcast like Inquisitive by the British King of Podcasting, Myke Hurley (that’s his official title by the way). If you have though, I have some bad news for you: they are mostly lies and half-truths.

When you ask someone to recall a past event, it is invariably, and invisibly shaped by things that happened long after that event. A company wrote an app that was wildly successful in a category? Well clearly every decision they made going into that process was the right one. Events that happen later were foreshadowed, and predicted as part of the decision making process. Most likely they thought these decisions through and debated them. Perhaps they spent an agonising amount of time choosing between two completely different paths. So their reasoned, debated and heavily pondered decisions led them to the success they now enjoy right? The most likely answer in my experience is: not really. There were probably hundreds of other companies that made similar decisions, maybe even ones that on paper were smarter ones, and most of them failed. The painful truth is if you have a successful origin story, a lot of things went right for you. While you might like to attribute them all to careful planning and a keen eye for strategy, in the world of indie development, you probably just got lucky.

Then there’s the details that change over time. All great stories become better each time they are told. Sometimes you tell the same story enough times and it becomes indistinguishable from the real events. Most scientific research shows our human memories to be much less reliable than we might imagine them to be. We often add things to them based on what we think happened, and things people tell us. How many of us have memories of what we did as children that are nine times out of ten actually just invented memories based on a relatives telling of a story? Probably more than we’d ever know, or care to admit. In our own Shifty Jelly story I often get asked “Why the name Shifty Jelly?”. My usual answer goes along the lines of “Philip and I were working full time corporate jobs when we started this, and we wanted to make sure we picked a quirky name that would look out of place in a board room. No one should ever be able to say ‘we outsourced our security to Shifty Jelly’ and maintain a straight face. We also wanted to make sure our employers felt comfortable with the fact that we weren’t going to even attempt to compete in the same field that they were in”. Is that 100% true? In all honesty I have no idea. I’d like it to be, and I think I have memories of us having discussions about it, but I’m not sure whether that was our thinking at the time or not. It seems logical that it would have been, but that doesn’t mean much. “I have no idea to be honest” makes for a pretty sucky origin story though, which is where I think the story of our name came from. I didn’t make it up in order for it to sound impressive, it’s just how I remembered it at the time.

Now imagine you want to tell your origin story with 100% accuracy. The issue becomes, you actually can’t. Your human memory is not even close to 100% accurate. If you believe some studies, you’re lucky if even 50% of your memories actually represent exactly what happened. Even if you documented in painstaking detail what you did each and every day, you’d have to interpret what you wrote many years ago without using the lens of your current knowledge. Maybe you’re a better person than I, but I’m convinced that’s about as impossible as convincing Australia’s current Prime Minister to roll out fibre to my house and fix global warming.

Long story short: almost every origin story is just that, a story. There are a lot of truths in there, but often they are embellished with the facts of the present. Most successful people attribute their success to planning and determination, and thus every origin story skews that way. That’s why books, posts and podcasts about successful people are rarely good sources of information for those starting out. You can copy how 37 Signals run their business, but you won’t magically become as successful as them. You can read all the Donald Trump books in the world, but you still won’t be Donald Trump. The oddest part of this to me though, is this: I love origin stories. I learn so many things from them. They don’t have to be 100% accurate to be informative or entertaining. Perhaps, just perhaps, story telling is built into our DNA for a reason.

Brief Apple Watch Thoughts

It’s very interesting watching the Apple developer community and press thinking through and speculating about how the Apple Watch launch will go. I personally think it will be a hit, simply because there’s enough demand for something like this, made by Apple. As a long time Android Wear user though, I think Apple are going to make a few key mistakes that no one will pick up until after it launches.

The first, and least obvious of these is that a watch should always be on. Pebble got this right, Android Wear watches like the LG G Watch R I reviewed get this right as well. I’ve worn watches that turn off and wake up when you look at them, it’s an awkward experience at best. At its worst, it’s just plain annoying. As far as I know, Apple haven’t explicitly said what there’s will do, but with an LCD display and concerns around battery life I’d bet my left leg it turns off the display to save power. Don’t kid yourself, no amount of software polish will make a watch that needs to wake itself up based on your wrist movements an amazing experience.

The second is a bit more nuanced, but the SDK that Apple gave developers revealed something unexpected for me. Almost all the processing for watch apps will be done on your phone. Open a watch app, it launches a companion extension on your phone that runs all the code required. Glance at your watch? Ditto. I suspect that means my iPhone is going to take a decent battery life hit just for being connected to my watch. As a former Pebble owner I know that an always on bluetooth connection tends to take about 5-10% of your battery all by itself. Add to that processing and networking requests being made by your watch to your phone, and I wouldn’t be surprised to see that go up even more. iPhone 6 Plus users probably won’t mind, but if you have a 5S or 6, then you can kiss even more of your precious battery life goodbye.

I don’t think either of these things will stop people from buying the first Apple Watch, and as I said, it will still be a hit. It will annoy me personally though, since I’ve seen watches ship with both those flaws already solved.

LG G Watch R U OK M8

I ended my mini Moto 360 review by saying:

Supposing however that you magically transplanted the screen, battery and processor of the Gear Live into this watch, well then I’d be throwing my money at you.

It occurred to me shortly afterwards that LG might just have done that, with the extremely awkwardly named LG G Watch R. So dear reader, for your sake and that of science I went ahead and ordered one. I’ve been using it for almost a week now and I’ve definitely formed a clear opinion about where this watch sits in the current landscape of Android Wear watches. The TL;DR would look like this: LG R > Moto 360 > Gear Live > LG G.


This watch gets a lot of things right:

  • The AMOLED screen is great. Bright, clear and most importantly of all: visible in ambient/dim mode.
  • The battery life is also good: 2 days in always on mode, with the watch never turning off. I haven’t even bothered to see how long you’d get with it going to sleep.
  • In terms of looks it’s no work of art, but it does look the most watch like of all the devices I’ve worn. This means it doesn’t stand out on your wrist as a futuristic computer. If you like to fit in, this might be a plus for you.
  • The screen is completely and utterly round, with no cut outs to be seen. Gruber hasn’t even seen fit to come up with a catch phrase for this watch, or even mention that it exists, that’s how round it is.
  • Whatever processor is in there, is clearly the right one. I haven’t noticed a single bit of lag in any of the Android Wear UI like I did on the Moto 360.

But it doesn’t get everything right:

  • The default watch faces are noticeably uglier and more tacky than those on the 360. Android Wear 2.0 is meant to address this by providing support for downloadable watch faces. In the mean time you’re left wishing that LG had even half of the design prowess that Motorola has.
  • The screen is smaller than the Moto 360, and noticeably so. A lot of content gets cut off far earlier than on the 360, which is annoying.
  • The charging cradle it comes with, while better than most, is not as nice as the Moto 360 inductive charger. It also means you need LG’s dock, unlike the 360 that you can drop onto any wireless charger.
  • It just doesn’t look as nice as the 360. I know this is subjective, but the 360 feels like a class act sitting on my wrist. This just feels like a cheap-ish watch. I’ve talked to other people that completely disagree with me on this point though, so your mileage may vary.

My overall impression is that this watch gets a lot of things right. A bright, always on screen. A snappy, responsive User Interface. Decent battery life. If I had to recommend only one Android Wear watch, this would be it. That said if you’re on the fence, I’d really recommend waiting to see what the second generation of these watches bring. A lot of these watches, and even Android Wear itself, feel like products that are in a rapid transition phase. Personally I have a soft spot for Motorola and their superior hardware design and aesthetic. I really hope they nail it with the Moto 720…or One…or whatever they end up calling the next one.

Moto 360 Thoughts

Back in June I gave my first impressions of the Galaxy Gear Live that Google gave developers like me at I/O. At the same conference they also announced we’d be getting a Moto 360 later in the year as well. So I patiently waited. And waited…then I waited some more. Well last week the long wait was over, this arrived in the mail:

moto_boxThe first and most stunning feature about this watch is immediately obvious: the box is round, the watch is round, 360 degrees makes a circle…are you getting it yet? Yes, it has a circular screen. In person it looks nothing short of stunning. The aluminium frame and the edge to edge screen are truly impressive to behold. Sitting on my wrist it looks less smart-watch and a lot more just watch. I’ve been using Android Wear ever since June, so I don’t want to review the software again, since it’s the same on every watch. I do however want to talk a bit about what makes this watch different, and how it compares to the Gear Live.

The Good Bits

  • The hardware design, as mentioned above, is amazing.
  • The watch faces are elegant, and you can customise them using the Motorola Connect app, something you can’t currently do with the Gear Live.
  • The watch is incredibly light, and the band very comfortable. Unlike the Gear Live I sometimes don’t even notice it on my wrist.
  • The heart monitoring (which I believe it does every 5 minutes by default) seems accurate, and gets a reading far more than the Gear Live could on my wrist. This is probably because it just fits better on me than the Gear Live did.
  • The inductive charging cradle is a thing of beauty. I place the watch in it, and it gently levels itself and displays the time and current battery level in the new orientation.


Things I’m Less Than Enamoured With

  • The processor is noticeably slower than the one in the Gear Live. I don’t give two hoots about tech specs, but the UI is quite often sluggish and unresponsive to immediate touch. The Gear Live didn’t have this issue at all.
  • The ‘ambient’ mode is next to useless. On the Gear Live’s AMOLED screen, the watch is able to power down most of the display, while still keeping a power saving watch face visible. This means you can get two day battery life, while still having a watch visible at all times. The Moto 360 is capable of the same thing, but the ambient mode is too dim to be even remotely useful. I can barely see it in a dark room, and outside, nothing.
  • Even when the ambient mode is on, the watch still tries to be clever and power down the screen when it’s not horizontal. I’m sure this seemed like a good idea to conserve battery, but the few times you do manage to catch it off is annoying. The Gear Live doesn’t do this, and it’s better for it.
  • Even at full brightness, the screen is not as good outdoors as the one on the Gear Live.
  • The battery life is a decent amount worse than the Gear live. I tend to take my watch off the charger at 7.30am and place it back on before I go to bed, normally around 11.30pm. I tried 3 different setups, one each day. Here’s how much battery I had left at the end of each of those days:
    1. Ambient Mode on, auto brightness: 19% (Gear Live: 60%)
    2. Ambient Mode off, auto brightness: 62% (Gear Live: 70%)
    3. Ambient Mode on, max brightness: 5% (Gear Live: 50%)

Those of you in the Apple Camp might have noticed that I haven’t even mentioned the little black cutout at the bottom of the screen. I find it ironic that the thing Gruber et al worked themselves into a frenzy about before the watch launched, turns out to be the least interesting flaw you could focus on. Your mileage may vary, but I stopped noticing it after the first day of using it.

Overall I wouldn’t have spent my own money on this watch. There are just too many downsides to make it worth the price tag. The software is great, the case is amazing, but the internal hardware needs some serious work. Supposing however that you magically transplanted the screen, battery and processor of the Gear Live into this watch, well then I’d be throwing my money at you. I hope you’re listening Motorola.

It Just Works

My first Apple product was an iPod Mini. I still vividly remember being hooked by the design and functionality of such a tiny, sexy device. My next Apple product was a Powerbook G4. Those two products started a long journey of buying and loving Apple products. iPhoto. iPhone. iPad. iWork. I bought them all, and I loved them all. One phrase always kept me coming back for more: “It just works”. After coming from devices that always felt buggy and half-finished it really did feel just like that. Everything, well, just worked.

Fast forward to today, 2014. Zoom in to me. I’m typing this on a Macbook Pro. In my pocket is the iPhone 6. Three metres away sits a Mac Mini. On the surface, nothing has changed. The problem is, it feels like everything has changed. In short while Apple’s hardware continues to impress me, their software has gone downhill at a rapid pace. iPhoto is an unusable mess with the volume of photos I now have. Aperture has been discontinued and is badly lagging behind in terms of both performance and features. iTunes takes forever to launch, and is bloated mess of way too many features and functions. iCloud is still a mess that I wouldn’t dream of storing my important data in. iOS 7 crashed so often that I became intimately familiar with the Apple logo that appeared every time it did. iOS 8 fixed the crashing, but introduced thousands of little paper cut like bugs. I used to install updates from Apple the second they came out, now I wait a few days to see if they are actually any good.

If you think this is just my experience, let’s take a quick recap of the last few weeks of Apple news:

  • iOS 8.0.1 was released, with bugs that prevented iPhone 6 and 6 Plus owners from connecting to the cell network, and using Touch ID.
  • Users trying to fix iOS bugs, reset the settings on their devices. This had the fun, unexpected consequence of wiping their iCloud documents, and syncing those deletions to all their other devices.
  • Apple released HealthKit as part of iOS 8, only to pull it, and any apps that supported it due to bugs.
  • Apple ‘fixed’ HealthKit as part of iOS 8.0.2, but my Twitter timeline is still full of people complaining about bugs. By all accounts, and going by the iOS 8.1 change log released today, it’s nowhere near ready for prime time.

On the developer front recently:

  • iTunes Connect is still amazingly buggy, and Apple managed to make it more so while developers were submitting their iOS 8 updates. I saw so many automated rejections, upload errors and bugs fill my timeline.
  • Xcode still crashes for me, at least once or twice a day.
  • Apple bought TestFlight, much to our delight, only to reveal that their answer to ‘beta testing’ is to let us distribute to 25 people that have administration rights over our apps. Do you want your beta testers to be able to change your app prices, descriptions, screenshots and to be able to pull apps from the store? Yeah me neither. The alternative is to submit your app for app review, before you’re allowed to distribute it to beta testers. Really Apple? Did I mention that the review queue is currently 9 days long and growing? Thank Thor that HockeyApp still exists.
  • Size classes, Apple’s answer to ‘how on earth are we going to deal with the new screen sizes’ lack even the most basic functionality required to do that. The iPhone 6 Plus has it’s own size class, in landscape, but in portrait orientation? Every single iPhone ever made is treated the same way. That’s right, you can’t lay out a different UI for the 3.5″ iPhone in portrait than you can for the 5.5″ monstrosity of a 6 Plus. How Apple missed this basic developer requirement is baffling to me.
  • Swift, the language we were all amazed by in June, has turned out to be a bag of hurt for anyone that jumped into it headfirst. It’s clear that it too wasn’t ready for prime time. I would have happily waited another year or two, especially if Apple built some major apps using it first. As it is we’re beta testing it for them, even after the 1.0 release.

Tim Cook keeps telling us that ‘Only Apple’ could do the amazing things it does. I just wish that Apple would slow down their breakneck pace and spend the time required to build stable software that their hardware so desperately needs. The yearly release cycles of OS X, iOS, iPhone & iPad are resulting in too many things seeing the light of day that aren’t finished yet. Perhaps the world wouldn’t let them, perhaps the expectations are now too high, but I’d kill for Snow iOS 8 and Snow Yosemite next year. I’m fairly confident I’m not alone in that feeling.