Android Software Stack and Terminology (Tutorial 01)
DZone's Guide to
Android Software Stack and Terminology (Tutorial 01)
Join the DZone community and get the full member experience.
Join For FreeHow do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.
The Android system software stack is typically divided into the four areas as the following graphic:
Terminology
- Android Software Development Kit (Android SDK) contains the necessary tools to create, compile and package Android applications
- Android debug bridge (adb), which is a tool that allows you to connect to a virtual or real Android device
- Google provides two integrated development environments (IDEs) to develop new applications.
- Android Developer Tools (ADT) are based on the Eclipse IDE
- Android Studio based on the IntelliJ IDE
- Android RunTime (ART) uses Ahead Of Time compilation, and optional runtime for Android 4.4
- Android Virtual Device (AVD) - The Android SDK contains an Android device emulator. This emulator can be used to run an Android Virtual Device (AVD), which emulates a real Android phone
- Dalvik Virtual Machine (Dalvik)-
- The Android system uses a special virtual machine, Dalvik, to run Java-based applications. Dalvik uses a custom bytecode format which is different from Java bytecode.
- Therefore you cannot run Java class files on Android directly; they need to be converted into the Dalvik bytecode format.
How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.
Like This Article? Read More From DZone
Topics:
Published at DZone with permission of Madhuka Udantha , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}