Hardware Meets
Software

Frequently Asked Questions

Can you build a companion app for our BLE hardware?

Yes. The Classified Cycling companion app manages 4 hardware types over BLE with challenge-response authentication, firmware OTA via Nordic DFU, and multi-device bonding.

Do you handle firmware OTA?

Yes. We implement over-the-air firmware updates using Nordic DFU or custom protocols. Version management, progress tracking, and rollback support included.

Can Flutter run on embedded devices?

Yes. The Xplore Group charger dashboard runs Flutter on Raspberry Pi, displaying real-time EV charger status and office management data at 60fps.

Do you work with custom BLE protocols?

Yes. We've integrated Shimano Di2, TRP CMD, and custom proprietary protocols. We read your protocol spec and implement the mobile-side communication layer.

How do you test BLE integrations?

We test with real hardware throughout development. BLE behavior differs between iOS and Android, between foreground and background, and between Bluetooth versions. Real device testing catches issues that simulators miss.

Can you integrate with MQTT or other IoT protocols?

Yes. We integrate with MQTT brokers, WebSocket servers, and REST APIs for device management backends. Lava uses WebSockets for live auction bidding, streaming 100 price points with 20 updates per second.

How long does a BLE companion app take to build?

A companion app with device pairing, basic telemetry, and firmware OTA typically takes 3 to 5 months from discovery to launch. Complex multi-device setups with custom BLE protocols can take longer. We scope after understanding your hardware.