Mobile Development

Question 1

Core OS

Answer 1

• Security
• Memory Management
• Process Management
• Network Stack
• Driver Model

Question 2

Hardware Abstraction Layer (HAL)

Answer 2

• Interface for the Android framework to communicate with device hardware.
• Abstracts hardware-specific details, allowing Android to run on various devices.

Question 3

These libraries provide core functionalities for various Android components, such as graphics, sound, and security.

Answer 3

Native C/C++ Libraries

Question 4

Takes Java bytecode compiled into Dalvik Executable (DEX) format and translates it into native machine code that can be directly executed by the device’s processor

Answer 4

Android Runtime (ART)

Question 5

High-level API available to app developers

Answer 5

Java API Framework

Question 6

Abstracts the complexities of the underlying Core OS, making it easier for developers to build applications.

Answer 6

Core Services

Question 7

Provides the frameworks and technologies necessary for applications to work with audio, video, graphics, and animations

Answer 7

Media

Question 8

• This layer is what developers use to create the interactive and visually appealing aspects of iOS applications.
• It is the layer that directly interacts with the user.
• It is the main application layer for IOS.

Answer 8

Cocoa/Cocoa Touch

Question 9

Function passed as an argument to another function, which is then invoked (called back) inside the outer function to perform a specific action or routine.

Answer 9

Lifecycle Callbacks

Question 10

Types of Mobile Apps

Answer 10

1. Native Apps
   a. Android
   b. iOS
2. Hybrid Apps
3. Cross-Platform Apps
4. Progressive Web Apps

Question 11

These applications are developed for a particular platform or device.
1. Code for both platforms
2. Deploy to both platform stores
3. Update both codebases

Answer 11

Native Apps

Question 12

Native Apps Pros

Answer 12

• Performance
• Support
• Security
• Full device feature access

Question 13

Native Apps Cons

Answer 13

• Codebase
• Specialized skill
• Time -> Cost
• Platform specific nuances

Question 14

• Apps built using web technologies (HTML, CSS, JavaScript) and wrapped in a native container.
• Relatively easy and quick to develop.
• Can access some device features through plugins.
• Performance can be a concern.

1. Code using React, Angular, etc (HTML, CSS, javascript)
2. Build for mobile by using Cordova or Ionic

Answer 14

Hybrid Apps

Question 15

• Closest tier to native development
• Provides own components.
  1. Code
  2. Build and deploy for different platforms

Answer 15

Cross-platform

Question 16

• Built using web technologies
• Acts like a native app
• Limited hardware access
• Can bypass App Store/Play Store
• “App-like”

1. Code
2. Build and deploy a website
3. Install on mobile device. runs on browser

Answer 16

Progressive Web Apps (PWA)

Question 17

Native vs Hybrid/Cross-Platform vs PWAs Disadvantages

Answer 17

1. Native
   a. Higher Development Cost
   b. Multiple Codebases for the same app
2. Hybrid/Cross-Platform
   a. Complex apps = slower
   b. Apps cannot perform OS specific tasks
3. PWAs
   a. Limited offline functionality
   b. Limited access to device features/hardware
   c. Security Risk
   d. Appstore?

Question 18

Native vs Hybrid/Cross-Platform vs PWAs Advantages

Answer 18

1. Native
   a. Device specific features
   b .Works offline
   c. Better use of OS and device specific functionalities
2. Hybrid/Cross-Platform
   a. Reusable Code
   b. Access to native features
   c. Close-to-native UX
3. PWAs
   a. Reduced Development Costs
   b. Easy Updates
   c. Versatility
   d. Appstore?

Question 19

Some things to consider when making your decision

Answer 19

1. Performance
2. Development Cost and Time
3. UX
4. Access to Device and Features
5. Maintenance and Updates
6. Target Audience