Get in Touch
← Back to case studies

Construction & Field Services · Equipment control

Making a Bluetooth connection useful at the worksite

Native iOS and Android applications connected equipment readings with on-site controls, while targeted BLE maintenance addressed the gap between a connected device and a responsive one.

  • Bluetooth LE
  • Native mobile
  • Equipment control
  • Connection diagnostics

At a glance

Business need
Give operators responsive control and alignment feedback
Product
iOS and Android equipment applications
Delivery
Application development and targeted maintenance
Technology
Swift, Kotlin, CoreBluetooth, Bluetooth GATT

The business context

The operator needed to see the effect of a command.

At the worksite, a phone can be part of the equipment’s operating interface. The client’s application showed angle, direction, battery, and signal information while letting an operator adjust sensitivity, brightness, operating mode, zero position, and direction.

The useful experience was the full loop: connect to the equipment, read its state, make an adjustment, and see the resulting feedback. Shinetech developed native iOS and Android applications around that loop and continued to support them after the main delivery.

Reconstructed equipment-control interface with alignment readings, battery and signal status, and sensitivity, brightness, and zero controls.
System view

Control and feedback on the same screen

An illustrative equipment-control screen combines readings and operator actions. Device names, measurements, and interface details are fictional and do not reproduce the client’s hardware protocol. View full-size interface (new tab)

The operating challenge

“Connected” was not enough when the equipment did not respond.

An established Bluetooth connection could still leave a command without a useful result. Notification setup, the order of writes, connection state, firmware behavior, and weak signals all affected the exchange. From the operator’s perspective, those different failures could look like the same unresponsive control.

The two mobile platforms also had to interpret the same equipment consistently. A sensitivity setting, zero command, or direction flip needed the same meaning on either phone. Even when data arrived correctly, coordinate conversion and display state could change how the operator understood alignment.

The delivery decisions

Treat connection, command, and feedback as one operating flow.

  1. 01

    Use the native Bluetooth capabilities

    Swift and CoreBluetooth on iOS, and Kotlin with Bluetooth GATT on Android, supported device scanning, connection, characteristic subscriptions, and command exchange. The application logic followed the actual equipment controls rather than a generic remote-control screen.

  2. 02

    Make command handling observable

    Android maintenance separated connection state, notification configuration, queued writes, timeouts, retries, and device responses. Debug states and exception monitoring helped the team locate intermittent failures within the exchange instead of treating every problem as a dropped connection.

  3. 03

    Keep readings and controls consistent

    The applications translated angle and direction data into alignment feedback alongside battery and signal status. Zeroing, direction changes, and sensitivity settings were handled in the same operating context so that controls and the displayed state could be checked together.

How the workflow holds together

Intermittent field behavior needed more than a successful bench connection.

Follow the command through the exchange

The maintenance work focused on the stages between a tap and the equipment’s response: whether notifications were configured, a command had reached the write queue, a response arrived, or a timeout required recovery. Reconnection prompts made interrupted operation visible to the user.

Keeping this information at distinct stages helped investigate a difficult symptom: a phone that still appeared connected while commands stopped responding. The applications also provided instructions, troubleshooting, and support entry points, recognizing that equipment operation continues outside a developer’s controlled test environment.

The delivered result

Operators gained a shared control workflow across two mobile platforms.

Native applications

Both iOS and Android supported connection, equipment controls, alignment, and device status.

Clearer diagnostics

The maintenance approach exposed separate BLE states for investigating intermittent command failures.

Continuing support

The delivered applications remained in use, with further work on stability as field issues emerged.

The main mobile applications were delivered and remain in use, with periodic maintenance focused on equipment interaction, feedback, and BLE stability.

Case taxonomy

Searchable by industry, technology, product, and business need.

Industry and product

  • Construction & Field Services
  • Equipment applications
  • Equipment control

Technology and delivery

  • Bluetooth LE
  • Native mobile
  • Swift
  • Kotlin
  • Hardware integration

Business need

  • Alignment feedback
  • Command handling
  • Connection diagnostics
  • Field maintenance