The joy with Android development
Do you know how painful it would be, having to work 40 hours out of your 48 hours weekend? Me neither. But I know how lame it is, having to work for literally 24 hours out of my 48 hours weekend.
Last weekend I was asked to come in to work and help out on a project they are working on. It’s an app for a client, it’s targeted for Android users. They just needed us to do some little ‘retouches’ and small bug fixes. I thought fair enough, sounds simple and easy, how difficult could that be? Well, I was mistaken. It’s a nightmare to go through someone else’s code, especially when you don’t have something like intellisense or code sense AND when four different programmers, all with different experience, agree that the code is really, really horrible and clumsy.
I went in to work on Saturday at about 1.30pm and stayed there till about 2am. I was working on the app and trying to iron out the ‘little’ bugs. At least I wasn’t alone, Ian was with me and we both were working on the app and at the same time had a laugh and made fun about how crappy the code and Android emulator is. It’s a pain in the backside to provide multiple device support, because you have to provide the correct images and dimensions etc. If something looks good on one device, it doesn’t necessarily mean it’ll look good on a different Android device.
The worst thing about all this was the emulator, it kept crashing all the time, for no apparent reason. It was totally random, we just couldn’t figure out a pattern as to when it would crash. I seriously wonder if Google has implemented a random generator inside the Android OS, deciding which error it will randomly throw out next time it runs!
We’re still working on the same app, we’re still trying to help them out with it. Slowly but surely we’ll get there.. one day.. maybe.. hopefully.
But anyways, at least now I can look forward to my next weekend, doing my coursework for the placement office. Yey.. :|