BLE companion app
Pairing, control, and firmware updates have to hold where the customer uses the device.
Most projects start in one of these situations.
Firmware and enclosure are ahead of the software in the user’s hand. Pairing, control, and a clear first flow are still missing.
A prototype pairs in the lab. In the field, after a restart, or on a second phone, that is not a product yet.
The app should do more than show buttons. It should operate the device, update firmware, and attach state to a cloud account.
Is your situation one of these, or a mix?
Book a Product Discovery Call (opens Calendly in a new tab)Services
Connect, reconnect, and show the user what the device is doing.
The controls your protocol actually supports: state, commands, and feedback in the app.
Firmware updates from the app, with a flow you can repeat in the field.
A user account, sync, and the data that should not live only on the phone.
The platforms your users actually have, not a bench demo for one phone.
First the protocol, then the app, then the account.
Source code, repository, and access to the infrastructure belong to you.
You speak with the developer who sets pairing, control, and the boundary with firmware. No handoff between an app agency and the hardware team.
A link that only holds on the desk is not a release. Reconnect, dropouts, and updates are part of the plan from the start.
An account is added when users, support, or updates need it. Not as an extra system with no task.
Your contact
Founder & Software Architect · Albrecht Apps GmbH
For more than ten years Andrej Albrecht has built mobile software for products where the app belongs to the device. The focus is Android, BLE, architecture, and the path from prototype into operation.
We email personal download links in your browser language.
Work
An industrial product needed an Android app that belongs to the device: not an add-on, but the way people operate the system.
Long-running development of a product already in commercial use.
His technical skill and expertise in app development, and in the related BLE communication with sensors in mechanical engineering, have been of inestimable value to our development work.
Martin K., INNIRION GmbH, 2024
He is highly committed and delivered on time.
Michael W., Endios GmbH
A lot of responsibility was given to him, and he handled it very well.
Hendrik R., Quantumfrog GmbH
Process
Device, users, pairing, what should be controlled, and whether update or cloud belong.
We read what the firmware already does and cut the first release to that.
You get a concrete next step, not a pile of options.
The app arrives in steps you can try on a real device.
Release, then the cases that only show up with customers.
A good fit is a product where the app is what makes the device usable, and the connection has to hold in the field.
The price depends on how far firmware, pairing, control, updates, and cloud already are. A narrow control app is a different project from a product with an account, OTA, and two platforms.
On the Product Discovery Call we place the scope. We do not quote a flat price without seeing the device.
FAQ
Place pairing, control, OTA, and cloud in one conversation.
Andrej Albrecht · Founder & Software Architect
Free worksheet
Sort out the goal, a first version, platforms, and integrations before you talk with us. You can fill in the PDF and pass it around internally.
We sent you a confirmation email. After you confirm, the checklist download link arrives.
You are also subscribed to updates from Albrecht Apps. You can unsubscribe at any time.