Being a ‘mobile’ developer is definitely fun. Although sometimes, when you think about it ‘deeper’ you’d rather drink a pint of whiskey:). Take a look at the enterprise Symbian OS:
http://www.codeproject.com/KB/mobile/Symbian_OS_design_faults.aspx
Reliable, huh? šŸ˜‰ And it’s not just Symbian – in my point of view it’s MIDP itself. You just can’t rely on it unless you test, test and once again – test. For me it feels like implementation usually just do not care about about what does the specification say. Things just DO NOT WORK… although documented that they should. Taking into account that there are tons of different devices out there your development might just drive you crazy. For example this issue haven’t ever been resolved so far.
We are moving to mobile applications fast and I hope many things would change soon, for developing Products with all the ‘stuff’ we have available now… it’s bit… em… unreliable. If not worse. I’m not talking here about mobile games or some sparky screensaver – this can do fine even now.
But it’s still interesting – you’re back into time when you had to count every single byte of memory you use and expect that environment “doesn’t really like those guys here”. SO that’s a bit of a challenge and it definitely makes you “programing understanding” better.