Best platforms for Bluetooth LE product development and seamless mobile app integration

On the hardware and firmware side, Nordic Semiconductor, STMicroelectronics and Espressif are among the most commonly considered vendors. Each of these ecosystems has different strengths, so the choice of microcontroller should be based on the product requirements, not only on the popularity of a development board.

Nordic nRF52 is a very proven choice for classic Bluetooth Low Energy products. The nRF52 family is well known in the industry, has a mature ecosystem and works very well in battery-powered devices, sensors, wearables, beacons and IoT accessories. Nordic nRF53, especially nRF5340, is a better choice for more advanced applications that require more computing power, a dual-core architecture or Bluetooth LE Audio. Nordic nRF54 is a newer, future-oriented platform for the next generation of BLE products, especially where energy efficiency and a longer product lifecycle are important.

STMicroelectronics offers, among others, the STM32WB and STM32WB0 families. STM32WB55 is a good choice for teams that already know the STM32 ecosystem and want to combine BLE with a familiar embedded environment. STM32WB0 is a cheaper and simpler line that fits less complex sensors, beacons and BLE products where cost and simplicity matter. For companies that already have experience with STM32, choosing this family can shorten the time needed to enter the project.

Espressif ESP32 is very popular in prototypes and IoT projects, especially where Wi-Fi is needed in addition to Bluetooth. ESP32 has a low entry barrier, many examples, a large community and easily available development boards. Compared to Nordic devices, it is often a less obvious choice for ultra-low-power BLE, but it works very well in fast prototypes, Wi-Fi-enabled devices, configurators and projects where cost and availability are more important than extreme power consumption optimization.

Embedded software development services

Building a BLE product on Nordic, STM32, or ESP32? Our Poland-based team delivers firmware, GATT, mobile apps, and OTA—from dev kit prototyping to custom hardware.

Explore embedded software development services

Best development kits for Bluetooth LE prototyping

At the MVP stage, it is worth using development kits that allow technical assumptions to be verified quickly without designing a custom PCB. In the Nordic ecosystem, popular choices include nRF52 DK, nRF5340 DK and nRF54L15 DK. They make it possible to start working on firmware, GATT, the mobile application, connection tests and measurements without waiting for custom hardware.

In the Espressif world, the natural starting point is ESP32-DevKitC and related development kits for ESP32-C3, ESP32-C6 and ESP32-S3. They are inexpensive, easily available and well suited for fast prototyping. In the STM32 ecosystem, it is often worth starting with NUCLEO-WB55RG or NUCLEO-WB05KZ, depending on whether the project requires a more classic and advanced STM32WB55 platform or the simpler and cheaper STM32WB0 family.

A good development kit does not replace final hardware, but it allows the most important risks to be verified faster. You can test range, connection stability, data format, onboarding flow, firmware updates, application behavior on Android and iOS and the first user scenarios. Only after such verification is it worth moving on to designing a custom board.

Nordic Thingy:53 as a platform for a fast MVP

One of the best platforms for quickly prototyping an MVP with Bluetooth Low Energy is Nordic Thingy:53. It is a ready-made IoT platform based on nRF5340, equipped with sensors and prepared for building a proof of concept without designing custom hardware from scratch. Its biggest advantage is that it allows you to move very quickly from an idea to a working demo.

Thingy:53 makes particular sense when the project involves sensors, data analysis, battery-powered devices, embedded machine learning, a mobile application and BLE communication. Instead of starting with a custom PCB, you can build the first firmware version, design GATT communication, prepare the mobile application and show the client a working flow. This shortens validation time and helps answer faster whether the product makes sense from both a technical and business perspective.

However, it is important to remember that Thingy:53 is a prototyping platform, not an automatic choice for the final product. After MVP validation, it is usually necessary to move on to custom hardware design, choose the target chip, optimize BOM cost, power supply, antenna, enclosure, production, certification and the firmware update process. Thingy:53 is therefore a great tool for reducing risk at the beginning of a project, but it does not replace the full embedded product development process.