5.1. The Tools

Throughout the development lifecycle of writing, building, and running the application, the primary tools Android developers use are:

Eclipse Java Editor

A specific text editor for Java that Android SDK has informed about the Android programming environment. The editor not only warns you about code the compiler can't parse, but also gives you a wealth of information about what it can.

Java and Dalvik Build System

Recall that Android converts your Java application to run on the Dalvik virtual machine under Android. The Java compiler and the Dalvik translator both provide error information if they can't build your application.

Eclipse Debugger

Eclipse provides a source-level debugger that the Android SDK connects with the running Dalvik bytecode, so you have all the debug capability you'd normally expect from a Java program running under Eclipse.

Logcat

Android also provides a general-purpose logging package that you can take advantage of to log informational or error messages from your running application. Perhaps of more importance, Android uses this facility extensively to tell you what is going on as it starts up, initiates your application, and tries to run it. There is also a special logcat log for telephony-related messages.

Android Debug Bridge (

adb

)

This provides a command-line debugging interface to a running Android phone or emulator.

DDMS

Android also provides a special window-oriented debugging environment custom tailored for Android and the Dalvik VM.

Traceview

An Android-specific utility that tracks all the method calls your application executed and the time spent in each method.