Skip to content

Posts tagged ‘Android development’


Testing on multiple Android devices simultaneously

If you’re developing for Android, sooner or later you’ll have to test your app against different versions of Android and different screen sizes and you probably want to see how these changes get reflected on all these devices simultaneously.

I won’t go into how many devices you should have and emulators vs physical ones, but instead I just wanted to write out how to get this running on all these devices simultaneously.

  • Option 1 — Use ant
  • Dan Dyer wrote a very good post on how to do this here.

  • Option 2a — use your IDE
  • In Eclipse/ADT, you can do this already from the run configuration. Just set the target to launch on all compatible devices (and a bit more refining is possible here, such as emulators only etc.). Didn’t seem to be able to do it from the device selector pop-up, you do have to manually edit the configuration.

  • Option 2b — use your other IDE
  • If you’re using IntelliJ, it’s the other way around. I was not able to do it from the manual configuration screen, but can do it from the pop-up device selector. Just shift+select the devices you are interested in from the list and that will work. If you tick Use “Same device for future launches”, it remembers to launch on the devices you’ve selected.


London River Bus

My first mobile app is out, built by Marco and myself. Look for London River Bus on the Android Market, which will tell you when the next Thames Clipper will arrive at a pier near you. You can also checkout the map of all the routes.

We have many more features lined up and hopefully an iOS version, but all shall come in due time :)

In the mean time, please let me know what you think. We’ve already received some good feedback for improvement, but we’re always looking for more ideas.


Android is not fragmented, it’s outdated

This isn’t really news for anyone even vaguely familiar with the mobile space, but here’s one image that reflects what I believe is by far the biggest problem with Android, straight from the developer’s website.

The vast majority 90%+ of the Android users out there use versions of the OS that are more than one year old and some 30%+ use versions that are 2 years old. This is a much bigger problem than the multiple devices Android runs on.



To break the negative vibe of me posting about things I don’t like, here’s something that I DO like.

Recently discovered this app through Android niceties, one day after I declared that it seems to me that iOS apps are, on average, of much better quality (especially from a UI/UX point of view) than Android apps. Neither the app nor the blog itself have really been enough to make me take that statement back – and I will write more about why I think that is soon – but it has definitely made me a bit happier about the apps that are available to the droid platform.

Any.DO is a to-do/task list with a lovely interface. Hands down the best task list app I’ve used so far.

What I like about it is 99% in the user experience. It looks nice and it’s very easy to read and use.

I want to emphasise, for all the mobile devs out there: it didn’t convince me with features! So far I’ve only discovered a few extra features that my previous apps didn’t have (e.g. automatically searches and lists contacts as you type when you’re creating a task, in case you want to add someone to it; also allows you to create a task on the fly for a missed call – call Alice in one hour), but I discovered that after I had decided to use it instead of my current similar app. I haven’t even explored most of what it can probably do!


Suggesting contacts


For me, the decision was made when I saw, within minutes of using it, that I can do all that I was doing before with considerably less effort.

It’s all in the UX. That won me over and that’s what wins users over almost every time. There is no use in adding a super complex set of features, if they are hard to use or find.


So, bottom line – it’s out for Android (iOS coming soon) and it’s free! So go ahead and check it out and let me know whether you agree or not.


E-Books ups and downs

Almost a year ago I blogged about getting a Kindle and how I was pleasantly impressed by it (that’s an euphemism for being totally blown away). It’s been 11 months and in this time I have downloaded 58 books on my Kindle. Wow! Now I say download and not bought because about half of these are free ebooks that you can get on Amazon (mostly classics). Out of all these I read probably about 20-25. In case you’re wondering how do I end up getting more books than I actually read, that’s an interesting topic that I’ll touch on another time.


Regardless, that’s still a lot of books read and a lot of books bought. I can say with certainty that I bought more books this year (using the Kindle) than in any year before because of the convenience. Nonetheless, among these numerous books, free or paid, there is not one technical book. I just never bought an ebook that I would be directly using in my work. There are several reasons for that:

  • Kindles are great for reading a novel from start to end, but not that great for flipping through pages and going back and forth
  • I don’t even notice the screen lag when I’m reading, but it would bug me a lot if I were going back and forth between a few pages (as I often do with reference books) or if I was searching for something specific
  • No color makes many figures and screenshots useless and most others hard to read
  • The screen is small by “tech book” standard. This is perhaps a weaker argument since there are larger Kindles, but for me it’s an argument nonetheless
  • Old habits die hard… I just like having the reference book next to me so that I can flip through it, make notes and of course throw it at the wall when code crashes!

Recently though I did purchase what is most probably my first technical e-book. I actually bought three of them in a pack. These are the Android Books from CommonsWare and again there are several reasons why I decided to buy these. As tech books go, these are quite cheap actually so it’s not a huge gamble if it turns out to be a bad idea, I could check on the author (by observing his inhuman rep on StackOverflow and the way he explains things there) and they actually seemed quite promising in terms of quality. But really, the one selling point that got me to decide on this almost immediately was getting Free updates for one year.

Now let met just stop there and expand on that. Free updates for any period of time is a HUGE thing in technology documentation, especially with something young like Android that mutates into something new every 10 minutes or so. My previous book on Android was outdated by the time I purchased it. By the time I finished it, Android was something else altogether. Updating books is something that you can’t have with “dead trees” and I cannot overstate its importance for tech books. I believe this to be the strongest argument for getting tech books electronically. Unfortunately, not all ebooks come with this benefit (actually…most don’t as far as I know), so the argument becomes rather null. It’s sad to have a medium with so much power, but find it not be used to its full capability.


Of course, I’m now back at my original concerns. Having this new ebook I was faced with the challenge of…well…using it. This is for personal work and I’m doing that off a laptop now which means that I don’t have three screens so that I can put the book on one and just work as normal. Lion’s fullscreen mode plus gestures actually helps a lot, it’s easy to switch between the book and the environment… but I still have to switch, which is a bit annoying (for those of you confused, I was spoiled by working on two 24+21 inch screens for a year; you just can’t really ever get over the experience of 40″+ of screen space).

Among my numerous options with these ebooks, I could get a Kindle version of the book so I could put it on my Kindle, but I run into the problems I was previously mentioning. Again, call me fussy, but I just can’t see myself using my Kindle for a tech reference.
I think this is where I become interested in having a tablet. I can genuinely see that be useful for something like this. A 10″ screen is decent size and if going through pages is as smooth and quick as it is on the computer, that’s great. Since the reasons for getting a tablet are adding up, maybe once the Kindle Fire makes it to the UK, I’ll look into that.

(You know, it’s funny how when the iPad came out I was completely unmoved and considered it a dumb idea and as time went by, I slowly started buying into the whole tablet thing; I hate to admit something like this, but in this case Steve was absolutely right… I had no idea what I wanted until he shoved it in my face. Damn!).