All IoT devices will need power to run the circuitry for the sensors, for the radio and the processing unit. The device developer will need to take the ultimate use case into account when designing the unit’s source of power. If the device is mobile, meaning that it will move around a room (like a wearable fitness tracker), or move around the country (like a monitor in the cargo bay of a long haul truck) or around the planet (like a sensor on an airplane engine), it will require some sort of internal battery. Designers will need to consider whether the IoT device can draw power from a larger source (like the battery that powers the truck) or if the device will require its own built in battery. If the device is fixed, the question then becomes whether the IoT device can plug into a wall socket to receive power or if the device can be set/inserted into the circuitry of the overall machine to receive its power. If the device is mobile, and it will be drawing power from a car battery, then there are a number of considerations that should go into the device design, such as: whether the IoT device will always be on? Or if not:  when should it receive power? Under what circumstances? How often should the device power up if the car has not moved? For example, with a car that has a locater device, how often should it wake up and take power from the battery to transmit its location data. These kinds of decisions regarding power management are key so that a car owner does not find the car battery dead because the IoT device has drained it. Another consideration for a mobile device is the use case – for example, a wearable device sold to consumers will need a battery. Can a rechargeable battery be built into the device or will it require the user to replace the battery? And if the battery is rechargeable, is the form factor so small that the consumer will need to learn a whole new behavior – like recharging the device multiple times per day – in order to keep the device operable, thus causing a consumer acceptance issue?