From prototype to series: The development process of a...

This article is part of our series about Bluetooth Low Energy. You can find the complete guide here: The ultimate guide to BLE App Development in Germany (2026)

From prototype to series: the development process of a BLE application

The development of a market-ready product with Bluetooth Low Energy (BLE) is a journey with many stages.

It is a complex interaction of hardware, firmware and software that requires careful planning and execution. Many companies underestimate the complexity that goes beyond the pure app development.

In this article we will guide you through the typical phases of a BLE project – from the first idea to the functional prototype to the certification and start of series production.

The development process in 6 steps

A step-by-step guide to the development process of a BLE application, from idea to prototype to mass production and certification.

If From prototype to series: The development process of a... is on your roadmap, Cost Calculator: Software Development und Discover solutions outline services and next steps.

Phase 1: Needs Review and Concept Everything starts with an idea. In this first crucial phase, the basic questions are resolved: what problem should the product solve?

Who is the target group? What functions does it have to have?

Here the needs for the entire system – hardware, firmware and app – are defined and stored in a load booklet.

It is also the time to conduct a first market review and to evaluate the cost-effectiveness of the project.

Phase 2: Hardware prototyping (Proof of Concept) In this phase, the idea becomes tangible.

The goal is to quickly create a first functional prototype, a so-called "Proof of Concept" (PoC).

Standard development boards (e.g. Nordic Semiconductor or Espressif) are often used to test the basic features without having to develop an expensive, custom hardware at once.

You test the sensors, the BLE connection and the basic interaction with a simple test app.

Phase 3: Firmware Development and GATT Design Parallel to hardware development, programming of firmware begins. A central point is the design of the GATT profile (Generic Attribute Profiles).

GATT defines the structure of how data are exchanged via BLE – in the form of "services". And "characteristics".

A clean and well thought-out GATT profile is the basis for stable and efficient communication between the device and the mobile app.

Phase 4: App Development (UI/UX and Logic) Now the mobile app comes into play.

Based on the concept created in phase 1, the user interface (UI) and the user experience (UX) are designed.

The developers implement the BLE communication logic to connect to the device, read the GATT profile and visualize the data appealingly.

At this stage, work is done in agile sprints to regularly get feedback and gradually improve the app.

Phase 5: Integr

References and further reading

The following separate references complement the topics in this article:

• Bitkom – German digital industry association.
• German Federal Office for Information Security (BSI).
• European Commission – Digital strategy.
• MDN Web Docs (Mozilla)
• W3C – World Wide Web Consortium.

"APIs are the backbone of modern systems; stabilise contracts early or pay twice in integration work later."

— Björn Groenewold, Managing Director, Groenewold IT Solutions

Frequently Asked Questions (FAQ)

What is this article about: “From prototype to series: The development process of a...”?

This article sums up practical aspects of From prototype to series. The development process of a... for leaders and delivery teams. In short.

A step-by-step guide to the development process of a BLE application, from idea to prototype to mass production and certification.

Who benefits most from the content described here?

It is especially relevant for firms in BLE development that need reliable systems, clear interfaces, and predictable delivery — from mid-market teams to expert departments.

How does this topic fit into an IT or digital strategy?

You can map the topic to service building blocks such as custom software and delivery support. Architecture reviews and stepwise rollout reduce risk and rework.

For multi-system landscapes, IT consulting and architecture helps align vendors and internal teams.

What are sensible next steps if we need support?

For architecture, rollout, or a second expert opinion, book a free initial consultation — including timeline and interface alignment.