Arghdroid
September 5th 2010 -
Aside from developing my firs ever GTK application, last week I’ve also created simple app for Android operating system. And it was as unpleasant experience as it could be.
Android = Java (I don’t take into account NDK). And not desktop/enterprise-like Java with good and intuitive debugging. It’s some weird Java-like virtual machine, with literally, no in-ide debugging support.
Here’s why – debugging is hell. I’ve spend 3 hours searching for one bug in UI, that appeared only in system log – not in debugger – because app just kept FCing before debugger could do anything.
And that’s the problem. Most of FC causing bugs only appear in system log, and stupid debugger wont show them. I don’t know if it is NetBeans fault, or generic one (I have not tried Eclipse yet), but, for Gods sake, just make an option to make application spit all crash info on screen (just like .NET CF applications do).
And no, “adb log” is not an answer. Until it is pinned to IDE and shows just which line bug occurred, and all associated values.
Tags: Android, Java, Programming