Hardware companion apps

Your device works. We build the iOS and Android apps that talk to it.

The hardware is finished; the app is the missing piece. We build native iOS and Android companion apps for connected devices, debug them against real hardware, and hand you the protocol documentation along with the code. The app is released under your own developer account.

01

Ways we have connected apps to devices

Bluetooth LE

Pairing, reading device data and sending settings back — the pattern behind our companion apps for screening and health devices.

Wi-Fi and local networks

Devices that report over the network instead of a cable: TCP, HTTP and MQTT reporting, and apps that talk to the device on the same network.

USB

Wired links where wireless is not allowed or not reliable enough — including low-level device code in C on the Android side.

Depth camera

Phone-based 3D capture: our scanning apps drive the depth camera directly in Swift, from capture to a measurable 3D model.

02

What makes these projects hard, and what we do about it

The protocol document is incomplete — or missing

We work against the real device instead: capture the traffic, reconstruct the protocol, confirm every command on hardware, and write it down as documentation your team keeps after handover.

Firmware versions drift apart

Devices in the field do not all run the same firmware. We test against the versions you actually ship and record where the behaviour differs.

The connection drops in the background

Reconnection, background modes and the differences between Android vendors are designed in from the start and verified on real devices, not patched after launch.

Every model behaves differently

An adapter layer between the device and the app keeps model-specific behaviour in one place, so a new model does not mean a rewrite.

03 — Relevant work

Where this shows up.

Foot-scanning apps for a US foot-care company
Native appsAI & visionApp publishing

Foot-scanning apps for a US foot-care company

A US foot-care and orthotics company

Two native Swift apps that capture the foot in 3D and turn the scan into a custom orthotics order. Released on the US App Store, with the first app maintained and updated since 2022.

Swift · 3D scanning SDK · Firebase

Full write-up (Chinese)
3D scanning and reconstruction pipeline
AI & visionNative apps

3D scanning and reconstruction pipeline

A 3D scanning technology company

An end-to-end chain from phone capture to finished 3D model: iOS scanning in Swift, a reconstruction engine in C++, and Python processing stages. Eight repositories, maintained from 2024 to 2026.

Swift · C++ · Python

Full write-up (Chinese)
04 — FAQ

Questions we get asked.

Where is the app published?

Under your own developer account, on the App Store and Google Play. We work in your accounts with the access you grant; nothing is published under our name.

Can you work with us remotely?

Yes. Most of our projects are delivered remotely: a written scope first, a clickable prototype before development, milestone demos, and a full handover of source code and documentation.

What about time zones?

We are in Beijing (UTC+8). Mornings overlap with Europe; for the Americas we work asynchronously with scheduled calls.

Do you also handle the store release?

Yes. We publish under your developer account and handle review, rejections and ongoing compliance. See App Store & Google Play publishing.

Contact

Tell us what you want to build.

What the product does, which platforms or devices are involved, and your timing. We reply within three working days, in English, with questions or a short written proposal.

Based inBeijing, China (UTC+8)