User blogs

Almost every new connected product starts with the same design question: which wireless protocol actually fits this device? For a huge share of consumer and commercial IoT products today, the honest answer is "both" — and that's driving rapid growth in combo BLE + Wi-fi SoCs, which handle setup, control, and high-throughput data over a single chip rather than forcing a choice between the two.

Here's what's actually driving that shift, and what to weigh when evaluating a combo SoC for a new design.

BLE and Wi-Fi solve different problems, and most connected products now need both problems solved at once.

BLEis cheap on power, simple to provision, and ideal for short-range control and setup — pairing a phone to a device, sending small command payloads, or maintaining a low-power always-on link. Its weakness is throughput: BLE isn't built for streaming meaningful amounts of data.

Wi-Fidelivers the bandwidth BLE can't — video streams, firmware-over-the-air updates, cloud connectivity for real-time data — but at a real power cost, and with a setup experience (entering network credentials, dealing with 2.4/5GHz band selection) that's clumsy without help.

The pattern that's emerged across smart home, security, and gateway products is now well established: use BLE for out-of-box setup and low-power control, hand off to Wi-Fi for the heavy lifting.A smart camera pairs via BLE in seconds, then streams video over Wi-Fi. A smart speaker configures its home network credentials over BLE before switching to Wi-Fi for actual audio streaming and cloud queries. This is why combo SoCs — rather than separate single-protocol chips — have become the default architecture for an increasing share of new designs.

Beyond the obvious "one chip instead of two" simplification, a well-designed BLE + Wi-Fi combo SoC offers real engineering advantages over pairing two separate radios on a board:

Coexistence handling.Running BLE and Wi-Fi radios simultaneously on 2.4GHz creates real interference risk if not managed carefully. A combo SoC with proper coexistence logic built in avoids the packet loss and connection drops that plague poorly integrated dual-radio designs.

Smaller footprint, lower BOM cost.One chip instead of two radios, two antennas (in some designs), and the supporting components each would need, meaningfully reduces board space and bill-of-materials cost — which matters at consumer product volumes.

Simplified provisioning flow.Combo SoCs make the "BLE hands off to Wi-Fi" provisioning pattern far easier to implement cleanly, since both radios share the same processing core and can coordinate the handoff without cross-chip communication overhead.

Unified firmware and OTA updates.Managing firmware across two separate radio chips is real ongoing engineering overhead. A combo SoC collapses that into a single firmware image and update path.

Datasheets for combo SoCs can look similar at a glance. A few areas are worth digging into specifically:

Real-world throughput, not just peak PHY rate.Advertised Wi-Fi speeds (often citing OFDMA or MU-MIMO support) rarely reflect what a device achieves in a typical home network with several competing devices. Look for real throughput benchmarks under realistic conditions where available, not just headline PHY numbers.

Standby and idle power, not just active transmission power.Many connected devices spend the overwhelming majority of their operating life idle, not actively transmitting. A chip with excellent active-mode power but mediocre idle power will disappoint in real deployment, especially for battery-assisted designs.

Band support (2.4GHz only vs. dual-band 2.4/5GHz).Dual-band support matters more in dense environments (apartments, offices) where 2.4GHz congestion is common, but adds cost and complexity — worth matching to your actual target environment rather than defaulting to the highest spec available.

Processor headroom for your actual application stack.If the device also needs to run Matter, a mesh protocol, or meaningful edge processing alongside its wireless stack, check that the SoC's CPU and memory are specified with that full stack in mind — not just the wireless radio's own requirements.

Certification maturity.A combo SoC that's already carrying FCC/CE modular certification and has an established track record in shipped consumer products meaningfully de-risks your own certification timeline compared to a newer, less-proven part.

As Matter continues pushing toward Wi-Fi and Thread as its primary transport layers, with BLE remaining the standard commissioning mechanism, the BLE + Wi-Fi combo architecture is likely to become even more central to mainstream smart home and IoT hardware — not a niche choice, but close to a default starting point for any product that needs both a smooth setup experience and real data throughput.

For teams currently scoping a new connected product, the practical takeaway is straightforward: if your device needs easy setup and meaningful data throughput — which describes a large share of modern IoT products — evaluating combo SoCs from the outset, rather than bolting Ble SoCs onto a Wi-Fi-only design later, tends to produce a cleaner, more power-efficient, and easier-to-certify result.