Mobile & Wearable OS
Mobile and wearable operating systems are the runtime closest to the body. They host the apps people use, broker access to sensors, and govern what software may do in the background and how much battery it may spend. These rules are not incidental: a permission model decides what an app can read, and a power policy decides whether it can keep reading. Understanding the platform clarifies why apps behave as they do on the devices nearest to movement.
Mobile & Wearable OS
Hosting apps
The runtime nearest the body
Phones and watches run the apps closest to where movement happens, pairing with sensors and presenting results in the moment. This proximity makes them powerful for live feedback, but it also means they operate under the tight power and attention constraints of devices people carry and wear all day.
Brokering sensor access
Permission models
An operating system stands between an app and the sensors, deciding what it may read and when. Permission models protect the person by requiring consent for sensitive data like location and health signals. They also shape what is possible to build, since an app can only work with the access the platform grants it.
Background and power
Rules that govern battery
Mobile and wearable systems limit what apps may do in the background to protect battery and responsiveness. These rules explain much of an app's behavior, why it samples periodically, defers work, or syncs in batches. Working within them, rather than against them, is central to building software that is both useful and a good citizen on the device.
Health frameworks
Shared stores on the platform
Many mobile platforms provide a shared health framework that apps can read from and write to, so a workout recorded by one app and a vital captured by another sit together. These frameworks ease integration but concentrate sensitive data, making the platform's privacy and access controls a central concern rather than a detail.