Connectivity is the most unforgiving hardware decision in an IoT product. The radio is soldered onto the board, certified for specific regions and tied to power and antenna design. You cannot swap it with a firmware update. Choosing well means understanding the trade-offs between range, power, data rate, cost and operational burden.

The Questions That Decide It

Start with the deployment, not the technology.

• Where will devices live? Inside buildings, underground, on moving vehicles, in remote fields?
• How much data, how often? A reading a few times a day is very different from continuous streaming.
• How is the device powered? Mains power allows chatty radios. A small battery expected to last years does not.
• Who manages the network? Does the customer provide Wi-Fi, or must your product bring its own connection?
• Where will it ship? Radio regulations and available networks differ by country and region.
• How long must it operate? Networks evolve, and older technologies get retired on schedules set by operators.

The Main Families

Wi-Fi. High data rates and ubiquitous in buildings. Suited to mains-powered devices on a network the customer controls. Credentials, captive portals and changing router settings create support burden.

Cellular, including low-power variants. Wide coverage without customer infrastructure, which simplifies installation. Carriers’ low-power cellular IoT options aim at battery-powered devices with modest data needs. Costs include connectivity plans and carrier certification, and availability varies by region.

LPWAN (such as LoRaWAN). Very long range and low power with small payloads and low data rates. You may operate your own gateways or use a network provider. Suited to sparse, infrequent readings across wide areas.

Bluetooth Low Energy. Short range, low power, and a natural fit for devices paired with a phone or a nearby gateway. Often used as a local link rather than a path to the cloud.

Short-range mesh protocols (such as Zigbee, Thread or similar). Devices relay for each other across a building, useful for dense installations of low-power nodes with a border router to the internet.

Wired (Ethernet, serial buses, power-line). Highly reliable and predictable, at the cost of cabling. Common in industrial and building systems.

Comparison at a Glance

Option	Strength	Watch out for
Wi-Fi	High throughput, customer-provided network	Provisioning friction, power draw, router changes
Cellular IoT	Wide coverage, self-contained	Connectivity plans, regional variation, certification
LPWAN	Long range, very low power	Small payloads, limited downlink, gateway coverage
Bluetooth LE	Low power, phone-friendly	Short range, needs a bridge to the cloud
Mesh protocols	Dense local networks	Border router dependency, interoperability testing
Wired	Reliability and determinism	Installation cost and flexibility

Use this table as orientation only. Vendors, modules and regional networks change, so confirm current capabilities with module datasheets and carrier or network provider documentation.

Power Is the Constraint Behind Everything

A radio that is always listening drains batteries. Most battery-powered designs rely on sleep schedules: wake, measure, transmit, sleep. Your connectivity choice determines how long the radio takes to reconnect and how much energy each transmission uses. Fewer, larger, well-timed transmissions often use less energy than frequent small ones, although exact behaviour depends on the technology. Measure real consumption on your hardware rather than relying on datasheet estimates alone.

Think About Two-Way Communication

Some networks are optimized for uplink and make sending commands to devices slow or limited. If you need to push configuration, trigger actions or deliver firmware updates, check how the network handles downlink and whether the device must be awake to receive. A technology that is perfect for reporting may be poor for management.

Plan for Failure and Fallback

Single-path connectivity is a single point of failure. Consider whether the product justifies a fallback, such as a cellular backup for a gateway normally connected by Ethernet. Even without redundancy, the firmware should cope with intermittent links through retries with backoff, local buffering and sensible timeouts.

Operational and Lifecycle Concerns

• SIM and subscription management for cellular fleets, including how you activate, suspend and monitor connections.
• Certification requirements for radios in each target market, which can affect launch timelines.
• Network sunset announcements from operators, which can strand devices on retired technology.
• Roaming behaviour for devices that cross borders.
• Diagnostics such as signal quality reporting, which is invaluable when debugging field problems.

A Hypothetical Example

Imagine a team building soil moisture sensors for farms. Devices sit in fields far from buildings, run on batteries for long periods and send a few small readings per day. Wi-Fi is impractical because there is no infrastructure, and a high-bandwidth radio would waste energy. The team compares an LPWAN approach with a low-power cellular option. LPWAN suits the tiny payloads but requires gateway coverage across the farms, while cellular avoids gateway deployment at the price of subscription management. They choose based on whether customers will accept installing a gateway, a business question as much as a technical one.

Frequently Asked Questions

Can I support more than one connectivity option? Yes, with multiple radios or modular designs, but it increases cost, certification and testing effort. Consider variants of the product instead.

Is 5G needed for IoT? Rarely. Most IoT applications need modest data rates, and lower-power technologies fit better. Match the radio to the workload.

Does Bluetooth connect devices to the cloud? Not by itself. It typically links to a phone or gateway that provides the internet connection.

How do I estimate battery life? Build a power budget covering sleep, measurement, radio activity and retries, then validate with measurements on real hardware.

What about private networks? They can offer control and predictable performance for large sites, but add infrastructure to operate. Evaluate them when public options do not meet requirements.

Next Step

Write a one-page connectivity requirements sheet covering location, payload size, update frequency, power source, regions and expected lifespan. Use it to eliminate options that clearly do not fit, then prototype the remaining one or two on real hardware in a realistic environment.