Every tap, click, and app launch passes through one piece of software before anything happens — the operating system. Here's what it actually does, and why Windows, macOS, Android, and iOS all do the same basic job in different ways.
The "How Computers Work" article in this series explained that hardware — the CPU, memory, and storage — runs on binary code, and that software is the instructions telling that hardware what to do. An operating system is a special category of software that sits between the hardware and every other program, managing the hardware on their behalf so that no individual app has to know how to control a processor or a hard drive directly. This guide covers what that management job actually involves, and how it plays out differently across the operating systems in everyday use.
Without an operating system, every single app would need its own code for talking directly to the processor, memory, storage, screen, and every other piece of hardware — an enormous and error-prone duplication of effort. An operating system solves this by acting as a middle layer: it manages the hardware once, and gives every app a simpler, standard way to ask for what it needs, like "save this file" or "show this on screen," without needing to know the hardware details underneath.
When a word processor "saves a file," it isn't writing directly to the storage chip itself. It asks the operating system to do it, and the operating system handles the actual low-level work of finding free space and writing the data correctly.
At its core, an operating system acts like a traffic controller for a device's hardware resources, deciding which program gets access to the processor, memory, and storage at any given moment, and for how long. This matters because a device typically has far more programs wanting attention than it has processor cores to run them on simultaneously, so the operating system has to constantly and fairly divide that limited resource among everything competing for it.
Each running program is called a process, and modern operating systems run many processes at once — a browser, a music player, and a messaging app can all appear to run simultaneously even on a device with only a handful of processor cores. This works because the operating system rapidly switches the processor between different processes, giving each one a small slice of time before moving to the next, far faster than a person could notice.
| Term | What It Means |
|---|---|
| Process | A single running instance of a program |
| Multitasking | Rapidly switching the processor between multiple processes so they appear to run at once |
| Scheduler | The part of the operating system that decides which process runs next, and for how long |
Every running process needs a private area of memory to store its own data, and the operating system is responsible for allocating that memory to each process, keeping one process from accidentally reading or overwriting another's data, and reclaiming that memory when the process closes. This isolation is also a basic security boundary, covered in the cybersecurity article in this series — without it, one poorly behaved or malicious program could read private data straight out of another program's memory.
A file system is the operating system's method for organising data on a storage drive into named files and folders, and for keeping track of exactly where each file's data physically sits on the drive. Without this organisation, a drive would just be one enormous, unlabelled block of binary data with no way to find anything again. Common file systems include NTFS on Windows, APFS on macOS, and ext4 on many Linux systems — different implementations of the same underlying job.
A smartphone's operating system also manages battery life directly, by deciding which background apps get to keep running, how aggressively the screen dims, and which processes get slowed down or paused entirely to conserve power — the same resource-management job as on a desktop, just optimised for a battery instead of a power outlet.
The operating system is also responsible for the interface a person actually interacts with. Early operating systems used a command-line interface, where a person typed exact text commands to be carried out. Modern desktop systems mostly use a graphical user interface, with windows, icons, and a mouse or trackpad, and mobile operating systems are built primarily around a touch interface, with gestures replacing many of the clicks a desktop system would use.
| Operating System | Primarily Used On |
|---|---|
| Windows | Desktop and laptop computers |
| macOS | Apple desktop and laptop computers |
| Linux | Servers, developer machines, and many embedded devices |
| Android | Most non-Apple smartphones and tablets |
| iOS | iPhones |
Despite their different appearances, every one of these systems is doing the same core job covered throughout this article: managing hardware, running multiple processes, organising a file system, and providing an interface — just built for different devices and design philosophies.
The operating system is the one piece of software almost nobody thinks about, precisely because it's doing its job well — every app opening smoothly, every file saving correctly, and every background process staying out of another's way is the operating system quietly managing hardware most people never see directly. Understanding what it does makes the rest of computing make more sense: an app isn't really talking to the hardware at all, it's talking to the operating system, which is talking to the hardware on its behalf.
10 questions. Select an answer for each, then submit to see your score instantly.