MQTT · BLE · NFC · OCPP · Modbus · CoAP
Specialists in connecting mobile applications to physical devices. From electric vehicle chargers to industrial sensors, medical wearables and access control systems.
Protocols
We don't just "support" them. We've spent years debugging at the packet level, reading 400-page specifications and testing in real production environments.
IoT Messaging
Lightweight publish/subscribe protocol for connected devices. Ideal for sensors, telemetry, real-time dashboards and bandwidth-constrained applications.
Bluetooth Low Energy
Low-energy wireless communication between app and physical device. From wearables to beacons and peripheral control with custom GATT profiles.
Near Field Communication
Reading and writing NFC tags, card emulation and contactless payments. We integrate with iOS CoreNFC, Android NfcAdapter and access control systems.
EV Charging Protocol
Open Charge Point Protocol for managing EV charging infrastructure. OCPP 1.6 and 2.0.1 support, CSMS, session management and smart charging.
Industrial Protocol
Standard industrial automation protocol for PLCs, variable frequency drives and measuring equipment. TCP/IP and RTU over serial or USB adapters.
Lightweight API
Integration with REST APIs of embedded devices, CoAP for network-constrained environments, and WebSockets for bidirectional real-time channels.
Use cases
Apps for drivers and charge point operators. Session start, smart charging, charger reservation and billing. OCPP 2.0.1 integration with any CSMS.
Mobile interfaces to monitor and control production lines, PLCs and automation systems. Modbus TCP/RTU, OPC-UA and real-time visualisation.
Clinical and wellness applications that sync with wearables, glucometers, blood pressure monitors and diagnostic equipment via BLE and certified GATT profiles.
NFC and BLE access control, MQTT monitoring of temperature, occupancy and energy consumption sensors integrated with existing BMS systems.
GPS tracking, vehicle telemetry, maintenance alerts and real-time dashboards. MQTT + OBD-II + REST APIs from telematics platforms.
NFC readers for contactless inventory, tap-to-pay payments, product onboarding and supply chain traceability with ERP integration.
Why it matters
01
A software bug gets patched. A bug in hardware integration can shut down a production plant, leave a vehicle without charge or compromise medical data. Error tolerance is zero.
02
OCPP 2.0.1 has 400 pages of specification. BLE with custom GATT profiles requires packet-level debugging. Modbus in industrial environments has quirks you only learn in the field.
03
No emulator replicates the behaviour of an EV charger under variable network conditions, a BLE sensor with a low battery or an industrial PLC with interference. You need real equipment in the development process.
04
We've integrated apps with EV chargers (OCPP), medical devices (BLE/GATT), industrial systems (Modbus) and NFC readers. That experience translates into fewer bugs, fewer delays and fewer surprises in production.
Our technical stack
Frequently asked questions
We work with any hardware that exposes a standard protocol (MQTT, BLE, NFC, OCPP, Modbus, HTTP/REST, CoAP, Serial). For proprietary devices, we review the manufacturer's API documentation or SDK before committing to timelines.
We do the full integration: mobile app (iOS + Android with Flutter), backend if an MQTT broker, OCPP server or protocol translation middleware is needed. We deliver the full stack ready for production.
Flutter is our primary technology. Flutter's BLE, NFC and serial plugins are mature and well-maintained. For cases where very specific native access is needed (iOS CoreBluetooth at a low level, for example), we use platform channels with Swift/Kotlin code.
Yes, and that's the usual setup. We integrate into the client's team as the software layer owners, coordinating with firmware and hardware engineers to define the BLE/MQTT/API interface that both sides will implement.
We know the documentation and traceability requirements these certifications impose at the software level. We've participated in projects with medical devices under IEC 62304 and industrial equipment. Consult us on your specific case.
Hardware integration projects typically start at €25,000 due to the technical complexity of the protocol and the need for real hardware testing. We can start with a lower-cost technical discovery phase to validate the approach.
Tell us about the protocol, the hardware and what you want to achieve. We'll tell you if we can do it and how.
