Introduction to Android App Development | Android development | Android application development
Content
Introduction to Android App Development
The Android software stack that can be described as a Linux Kernel and C/C++ libraries exposed through an application framework that provides services for and management of runtime and applications.
The elements of the Android software stack are:
1. Linux Kernel: provides abstraction between the hardware and the rest of the stack, responsible for device drivers (Camera , Wi Fi, etc…), resources management , power management, security and net working 2. C/C++ Libraries: such as SQL lite, Graphics libraries OpenGL ES, media framework and webkit layout engine. 3. The Android Runtime: includes Core libraries and the Dalvik Vitual Machine. The Core libraries provide most of java libraries + additional Android libraries. The Dalvik VM provides (Just In Time) JIT compilation. The VM is optimized to run multiple instances of VMs. As Java applications access the core libraries each application has its own VM 4. The Android Application Framework: Provides classes required to develop an Android application and abstraction between hardware accesses. The Android Java API’s main library includes telephony, content providers (data), resources, locations and UI. 5. Application Layer: all Android applications (native or third party) are built on the application layer using the same API. So Android applications are written in Java, but remember it is not Java ME (Mobile Edition). It’s just Most of J2SE libraries + Android’s own Java libraries.
The Android Application structure:
Android architecture encourages component reuse allowing you to publish and share activities, services and data between applications with security restrictions defined by you. This enables developers to include out of the box components such as the phone dialer or contact manager to their applications, or add new functionalities to them. The bases of the Android applications are:
Activity Manager: which controls the life cycle of the activities, activities can be compared to the windows or web forms they carry the controls (views) that construct the interface, an activity represents a single screen. Views: the UI components that construct the interface. They can be compared to the swing or windows forms controls
Notification Manger: provides a consistent mechanism to notify or alert users. Content Providers: lets applications to share data between them. Resources Manager: much like the ASP.NET resources concept. Enables the developer to store resources such as strings or images.
If you have Android development requirements contact us for further inquiry.
The Android software stack that can be described as a Linux Kernel and C/C++ libraries exposed through an application framework that provides services for and management of runtime and applications.
The elements of the Android software stack are:
1. Linux Kernel: provides abstraction between the hardware and the rest of the stack, responsible for device drivers (Camera , Wi Fi, etc…), resources management , power management, security and net working 2. C/C++ Libraries: such as SQL lite, Graphics libraries OpenGL ES, media framework and webkit layout engine. 3. The Android Runtime: includes Core libraries and the Dalvik Vitual Machine. The Core libraries provide most of java libraries + additional Android libraries. The Dalvik VM provides (Just In Time) JIT compilation. The VM is optimized to run multiple instances of VMs. As Java applications access the core libraries each application has its own VM 4. The Android Application Framework: Provides classes required to develop an Android application and abstraction between hardware accesses. The Android Java API’s main library includes telephony, content providers (data), resources, locations and UI. 5. Application Layer: all Android applications (native or third party) are built on the application layer using the same API. So Android applications are written in Java, but remember it is not Java ME (Mobile Edition). It’s just Most of J2SE libraries + Android’s own Java libraries.
The Android Application structure:
Android architecture encourages component reuse allowing you to publish and share activities, services and data between applications with security restrictions defined by you. This enables developers to include out of the box components such as the phone dialer or contact manager to their applications, or add new functionalities to them. The bases of the Android applications are:
Activity Manager: which controls the life cycle of the activities, activities can be compared to the windows or web forms they carry the controls (views) that construct the interface, an activity represents a single screen. Views: the UI components that construct the interface. They can be compared to the swing or windows forms controls
Notification Manger: provides a consistent mechanism to notify or alert users. Content Providers: lets applications to share data between them. Resources Manager: much like the ASP.NET resources concept. Enables the developer to store resources such as strings or images.
If you have Android development requirements contact us for further inquiry.
