Theory
How does an app reach the camera?
You are about to build FestConnect Mobile, an Android app for fest registration. But think about what that means: your app will need to draw buttons, read text, maybe use the camera for a QR ticket. Your code cannot poke the camera hardware directly, and it should not have to.
Between your app and the phone sits Android: an operating system that manages the hardware, and offers your app a ready-made toolkit to ask for what it needs. Understanding that relationship is the whole of this first lesson.
Theory
The building and its facilities desk
Your app is a tenant in a large building (the phone). You do not run your own wiring to the water main or the power grid. You call the building's facilities desk and ask: 'I need water', 'show this on the notice board'. Android is the building management, and its API framework is that facilities desk: a published list of services you can request, so you never touch the raw plumbing.
Theory
Android, formally
Android is a free, open-source operating system built on the Linux kernel, designed for touch devices (phones, tablets, TVs, watches). Android Inc started it; Google acquired it in 2005, and the first phone shipped in 2008.
Key features: open source, multitasking, rich UI widgets, sensor and media support, and each app running in its own process.
The API framework is the large library of prewritten classes and methods (like Activity, View, Intent) your app calls to use device features. You code against the API; the OS does the hardware work.
At a glance
Three words people mix up
| Term | What it is |
|---|---|
| Android | the operating system running the device |
| An Android app | a program you build that runs on Android |
| API framework | the class/method library your app calls |
Think first
Why not talk to hardware directly?
Your FestConnect app needs to show a message on screen. Why is it better to call an Android API method than to write directly to the display hardware? Give two reasons before tapping.
Show the answer
1. Portability: thousands of Android devices have different screens and chips. Coding to the API means the OS handles each device's hardware, so your one app runs everywhere. 2. Safety and simplicity: direct hardware access could crash the device or other apps; the API exposes safe, tested methods and hides the messy details. You write textView.setText(...); the framework figures out the pixels. That is the entire point of an API framework.
Quiz
Which statement about Android is correct?
- Android is a Linux-based operating system that Google acquired in 2005
- Android is a programming language you write apps in
- Android is a specific brand of phone made only by Google
- Android apps run without any operating system underneath
Show the answer
Android is a Linux-based operating system that Google acquired in 2005
Android is an operating system built on the Linux kernel, and Google acquired it in 2005 (A). It is not a language (B): you write Android apps in Java or Kotlin. It is not a single phone brand (C): many makers (Samsung, Xiaomi, etc.) ship Android. And apps absolutely run on top of the OS (D): the OS manages hardware and processes for them. Keeping OS, app, and language separate is the core of this lesson.
Watch out
The vocabulary trap
Exams punish loose wording. Android is an operating system, not a language and not a phone. You write apps in Java (or Kotlin) that run on Android. And the API framework is the class library, not the OS itself. A question like 'Android is a ___' expects 'operating system (Linux-based, open source)', full marks lost for 'a mobile'.
Theory
Next: what is inside the OS
You now know Android sits between your app and the hardware and offers an API. The next lesson opens the box: the Android architecture, the four-layer software stack from the Linux kernel up to your app, so you can see exactly where your FestConnect code lives and what supports it from below.
Summary
Key takeaways
- Android is a free, open-source, Linux-based operating system for touch devices; Google acquired it in 2005.
- It is an OS, not a language and not a phone brand; you write apps in Java/Kotlin that run on it.
- Features: open source, multitasking, rich widgets, sensors/media, each app in its own process.
- The API framework is the prewritten class/method library (Activity, View, Intent) apps call to use device features.
- Coding to the API (not hardware) gives portability across devices and safety.
- Memory hook: the app is a tenant; the API framework is the facilities desk.