=== Development tools ===
In order to start development A lot of your Android “Apps”, first of all you should download and install the Android SDK (http://developer.android.com/sdk/index.html). Please follow the instructions reported information on http://developer.android.com/sdk/installing.html in order how to properly install the SDK. If you want to use Eclipse as IDE, you should also install the Android Development Tools (ADT) Plugin (please find start programming can be found here the related instructions: http://developer.android.com/sdkguide/developing/eclipse-adtindex.html#installing).
[[File:Android-sdk-manager.png]]
A lot Before starting, make sure you can match the following prerequisites: * Windows (XP, Vista or 7), Mac OS X (10.5.8 or later) or Linux (tested on Ubuntu Linux, Lucid Lynx) development host* [http://www.eclipse.org/ Eclipse IDE] 3.6.2 (Helios) or greater installed on the development host (if you want to use Eclipse as IDE)* Eclipse JDT plugin (included in most Eclipse IDE packages) (if you want to use Eclipse as IDE)* [http://www.oracle.com/technetwork/java/javase/downloads/index.html JDK 6] (JRE alone is not sufficient)* Basic experience with Eclipse IDE (if you want to use Eclipse as IDE)* Good knowledge of Java language In order to start development of your Android “Apps”, you need to install the following components: * Android SDK* Eclipse ADT plugin (optional)* Android NDK (optional) First of all you should download and install the Android SDK (http://developer.android.com/sdk/index.html). Please follow the instructions reported on http://developer.android.com/sdk/installing.html in order to properly install the SDK. If you want to use Eclipse as IDE, you should also install the Android Development Tools (ADT) Plugin (please find here the related instructions: http://developer.android.com/sdk/eclipse-adt.html#installing). [[File:Android-sdk-manager.png|thumb|none|700px|Eclipse with ADT plugin]] ==== Android NDK ==== The NDK is a toolset that allows you to implement parts of your app using native-code languages such as C and C++. For certain types of apps, this can be helpful so that you may reuse existing code libraries written in these languages and possibly increased performance. For further information on how , please refer to start programming https://developer.android.com/tools/sdk/ndk/index.html === Overview of the SDK === An '''overview''' of the SDK can be found here: http://developer.android.com/guidesdk/exploring.html === Android emulator === Please refer to the [http://developer.android.com/tools/help/emulator.html Android emulator page] for detailed information on how the emulator provided with the Android SDK works. In particular, check the [http://developer.android.com/tools/developinghelp/emulator.html#KeyMapping Keymapping] table to know how to navigate the Android GUI on the emulator. === Android Tools === Please refer to [http://developer.android.com/tools/help/index.html.Android Tools page] for detailed information on the available useful tools, including:
For further information* [http://developer.android.com/tools/help/adt.html ADT]: a plugin for Eclipse that provides a suite of tools that are integrated with the Eclipse IDE. It offers you access to many features that help you develop Android applications quickly. ADT provides GUI access to many of the command line SDK tools as well as a UI design tool for rapid prototyping, please refer designing, and building of your application's user interface.* [http://developer.android.com/tools/help/adb.html Android Debug Bridge]: Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:** A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.** A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.** A daemon, which runs as a background process on each emulator or device instance.You can find the adb tool in <sdk>/platform-tools/.* [http://developer.android.com/tools/help/monkeyrunner_concepts.html MonkeyRunner]: The monkeyrunner tool provides an API for writing programs that control an Android device or emulator from outside of Android code. With monkeyrunner, you can write a Python program that installs an Android application or test package, runs it, sends keystrokes to it, takes screenshots of its user interface, and stores screenshots on the workstation. The monkeyrunner tool is primarily designed to test applications and devices at the functional/framework level and for running unit test suites, but you are free to use it for other purposes. See for example [[Button Pressing Emulation On Android]]* [http://developer.android.com/indextools/help/logcat.htmllogcat]: The Android logging system provides a mechanism for collecting and viewing system debug output. Logs from various applications and portions of the system are collected in a series of circular buffers, which then can be viewed and filtered by the logcat command. You can use logcat from an ADB shell or directly on the serial console shell to view the log messages.
=== Useful Links ===
[httpshttp://developer.android.com/training/index.html TutorialAndroid Developer Website]
[https://developer.android.com/training/index.html First project tutorial]
=== Notes ===
Portions of this page are reproduced from work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.