Case study
Connected Products and IoT · 2 min read
One verification feature over BLE and WiFi
An equipment verification feature that reaches the device over BLE or over the network, with the transport hidden behind a single repository.
- Client
- Connected hardware company
- Industry
- Connected hardware
- Capabilities
- Connected Products and IoT, Mobile Apps
- Status
- Delivered
Highlights
- Each transport changes and is tested on its own
- Feature code stayed unchanged when one path's behaviour changed
The challenge
An equipment verification feature had to reach the device directly over BLE in some setups and over WiFi through an API in others. Branching on the transport inside every screen would have doubled the work and the bugs.
Our solution
- 01Put the transport decision in the repository layer, returning the same result type from both paths.
- 02Gave the BLE path its own manager for connection state and the serial protocol, and the network path its own client.
- 03Kept screens and view models unaware of which transport answered.
What we delivered
- Dual-path repository for BLE and WiFi
- Dedicated BLE manager for the verification flow
- One shared result model consumed by the interface
Impact
Each transport changes and is tested on its own
Feature code stayed unchanged when one path's behaviour changed
Technology
KotlinAndroid BLEREST APIClean ArchitectureHilt
Have a problem like this?
Start with a free 1-hour architecture review with a senior engineer.