0% found this document useful (0 votes)
20 views12 pages

Android and iOS

The document provides an overview of Android and iOS, detailing their architectures, histories, and key features. Android, developed by Google, is an open-source mobile operating system based on the Linux kernel, while iOS, created by Apple, emphasizes security and integration within its ecosystem. Both operating systems have evolved significantly since their inception, with distinct approaches to app development, user experience, and security measures.

Uploaded by

hariramsathya2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views12 pages

Android and iOS

The document provides an overview of Android and iOS, detailing their architectures, histories, and key features. Android, developed by Google, is an open-source mobile operating system based on the Linux kernel, while iOS, created by Apple, emphasizes security and integration within its ecosystem. Both operating systems have evolved significantly since their inception, with distinct approaches to app development, user experience, and security measures.

Uploaded by

hariramsathya2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Mobile OS:

Android and
IOS

1
Introduction to Android and Its
Google Connection
What is Android?
● A mobile operating system built on the Linux kernel, designed for smartphones, tablets, and diverse devices.
● Primarily written in Java, with low-level components in C/C++, offering a robust and open-source platform.

Key Features
● Uses Linux features (processes, user IDs, virtual memory) in unique ways for mobile needs.
● Open-source via the Android Open Source Project (AOSP), customizable for manufacturers.

Android and Google


● Developed by Google after acquiring Android, Inc. in 2005, integrating Google’s cloud services (e.g., Gmail, Google
Play).
● Balances open-source flexibility with proprietary services, enforced via the Compatibility Definition Document
(CDD).

Google Play’s Role


● Google’s app store ensures compatibility by requiring CDD adherence and matching app features to device
capabilities.

2
History and Early Development of
Android
Origins
● Started by Android, Inc. in the mid-2000s to create smarter mobile devices, initially targeting cameras before
shifting to smartphones.
● Acquired by Google in July 2005, gaining resources to build a complete platform.

Early Development

● Initially supported multiple languages (JavaScript, Java, C++), but pivoted to focus solely on Java in 2006 for
quality and efficiency.
● Developed alongside Google apps (e.g., Maps, Gmail), refining the platform iteratively.

First Release

● Preview SDK released in November 2007, followed by Android 1.0 on the T-Mobile G1 (Dream device) in
September 2008.
● Targeted two devices: "Sooner" (dropped) and "Dream" (touchscreen, 3G, GPS-enabled).

Growth
● Evolved rapidly with 15 major updates by 2013, expanding to tablets, TVs, and more, driven by open-source
adoption. 3
Android Architecture
Linux Kernel

● Forms the foundation of Android’s software stack.


● Modified by Google to support mobile-specific needs:
○ Enhanced power management.
○ Optimized memory management and allocation.
● Introduces Binder IPC (Inter-Process Communication) for efficient process interaction.
● Provides core system services and hardware abstraction.

System Libraries and Drivers

● Bionic Standard C Library:


○ Replaces GNU C Library (glibc) with a smaller memory footprint.
○ Optimized for slower CPUs in mobile devices.
○ Avoids GPL licensing constraints of glibc.
● Native Libraries:
○ Includes Webkit (web browsers), SQLite (databases), and SSL (network security).

4
Android Architecture
Android Runtime (ART)

● Executes Java applications optimized for mobile devices.


● Ahead-of-Time (AOT) Compilation:
○ Compiles .dex files to native machine code during installation.
○ Improves efficiency and reduces power consumption compared to JIT compilation.
● Supports limited memory and CPU environments.

Framework

● Rich set of APIs for developers:


○ Supports graphics, audio, and hardware features.
○ Includes Android-specific Java API (distinct from standard Java API).
● Enables development of portable, feature-rich applications.
● Provides consistent functionality across varied hardware platforms.

Applications

● Built using Java, compiled to .dex files for ART execution.


● Leverage frameworks and libraries for functionality (e.g., browsers, databases).
● Run on a wide range of Android-enabled devices.
5
6
Security
Sandboxing

● Each app runs as a unique Linux UID, isolating it in its own file
system sandbox.

Permissions

● Apps declare permissions in manifests; users approve access (e.g.,


READ_PICTURES) at install time.

Binder Integration

● IPC carries UID info, enabling services to verify caller permissions


via the package manager.

Dynamic Access

● Intents and content providers allow fine-grained, user-driven data


sharing (e.g., sharing a photo URI).

7
Introduction & History of IOS
Introduction to iOS

● iOS is Apple’s mobile operating system, powering iPhones, iPads, and iPod Touch devices.
● Known for its sleek design, user-friendly interface, and tight integration with Apple’s ecosystem (e.g., iCloud, App
Store).
● Emphasizes security, privacy, and a seamless experience across hardware and software.

History of iOS

● Launched on June 29, 2007, with the first iPhone, originally called "iPhone OS."
● Renamed to iOS in 2010 with the release of iPhone OS 4, expanding to iPad.
● Key milestones: App Store (2008), Siri (2011), iOS 7 redesign (2013), and regular annual updates.
● Evolved from a basic touch OS to a robust platform with advanced features like ARKit and Face ID.

8
IOS Architecture
User experience layer:

● This layer defines the software interface that allows users to interact with the computing devices.
● macOS uses the Aqua user interface, which is designed for a mouse or trackpad, whereas iOS uses the
Springboard user interface, which is designed for touch devices.

Application frameworks layer:

● This layer includes the Cocoa and Cocoa Touch frameworks, which provide an API for the Objective-C and Swift
programming languages.
● The primary difference between Cocoa and Cocoa Touch is that the former is used for developing macOS
applications, and the latter by iOS to provide support for hardware features unique to mobile devices, such as
touch screens.

Core frameworks:

● This layer defines frameworks that support graphics and media including, Quicktime and OpenGL.

Kernel environment:

● This environment, also known as Darwin, includes the Mach microkernel and the BSD UNIX kernel.
9
10
Darwin
Hybrid Structure

● Combines Mach microkernel (tasks, threads, IPC) with BSD UNIX kernel (POSIX compatibility).

Dual System-Call Interfaces

● Mach traps: Core OS services (memory, scheduling).


● BSD calls: UNIX-like functionality (e.g., fork()).

Key Components

● Mach: Memory management, scheduling, IPC (ports, RPC).


● BSD: POSIX standards, file systems, permissions.
● I/O Kit: Device drivers and kernel extensions (kexts).

Single Address Space

● Mach, BSD, and I/O Kit run together, boosting performance over pure microkernels.

11
Security
Built-in Encryption

● All data on iOS devices is encrypted by default using AES-256, protecting user information even if the
device is lost or stolen.

Secure Boot Process

● Ensures only trusted software from Apple runs on the device, preventing unauthorized modifications.

App Store Vetting

● Apps undergo strict review to block malware, ensuring a safe ecosystem for users.

Face ID & Touch ID

● Biometric authentication secures access, with data stored locally in a Secure Enclave, not on servers.

12

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy