Mobile computing is computing that moves with the person: phones, tablets, wearables and laptops, on batteries and on networks that come and go. Its design problems are different from a desk machine's: scarce energy, small screens, touch, sensors, intermittent connectivity and the fact that the device is personal and always with you.
Key concepts
- Energy as the main budget: radios, screen and processor all drain the battery, so work is batched and deferred.
- Intermittent connectivity: the network drops and changes, so apps store data locally and synchronise later.
- Sensors and context: location, motion, camera and microphone let software react to where and how it is used.
- Input and screen: touch, small displays and one-handed use shape the interface.
- Privacy: a device that knows where you are and who you call needs strict limits on what apps can learn.
Vocabulary
- Offline first: a design that works without a network and syncs when one returns.
- Push notification: a message sent by a server to a device, delivered through the platform.
- Handover: a connection moving from one cell or access point to another without breaking.
- Duty cycle: the share of time that a component is on.
What to study, in order
- Measure how much battery a simple app uses with the screen on, in the background and with the radio active.
- Read how a phone connects to a mobile network and how it hands over between cells.
- Build an app that works offline, stores changes and synchronises them without losing any.
- Use a device's sensors in a small project and handle the case where the user refuses permission.
- Study how location data can reveal more about a person than it seems to.