Maintenance software

For maintenance-software vendors: no second technician app, only the missing protocol

The person in the conversation is the vendor product owner, not the plant maintenance manager. Most have already rebuilt the mobile app or deliberately kept the browser. A second technician app is the wrong project. What can remain is a device protocol your product will not take.

Book a technical assessment (opens Calendly in a new tab) 30 minutes. Bring the device your product will not take.
What the assessment covers
Buyerthe software vendor
Nota second technician app
Onlya missing protocol
Staysthe job list
Typical technology device protocolexisting interface

Adoption in the hall is already your product

Technicians in halls and basements are why the vendor built the app or kept the browser on purpose. SAP-side mobile clients are sold to the plant by specialists, not by a studio.

The app is there

A large customer wanted offline Android. The vendor shipped it or hired it.

The browser is a choice

That is a product decision, not a missing project.

The plant buys a package

mobileX, Ontego, or the like is an SAP PM client, not a second project.

What a second stack costs

Two technician apps mean two update paths and a customer who does not know which one counts.

One of them sits unused

Adoption fails on the duplicate screen.

Offline, twice

Conflicts and sync are already in the product.

The plant buys beside you

A package for SAP is the shorter path than a project.

Only the protocol that does not fit

Connect one device

The protocol the software will not take.

No second job list

Jobs, times, and feedback stay in the product.

Saying no is a result

If the package is enough, we say so.

Technology only at the device edge

Bluetooth or another device protocol can be the missing edge. The job data belongs to the product.

The device protocol

Read what maintenance otherwise cannot see.

Hand off to their interface

A record the product can already store.

No parallel app

No second client with its own job list.

Public signals show in-house mobile apps or packages for the plant. We do not offer a second technician app.

What the assessment checks

  1. 1

    Discovery

    The assessment checks whether offline Android is already in the product. Only if a concrete device protocol does not fit there does an edge remain. We do not rebuild the job list.

  2. 2

    Show the product

    App, browser, or package. Usually the project ends there.

  3. 3

    Show the device

    Only the protocol that does not fit.

  4. 4

    One handoff

    Into the interface the product already has.

  5. 5

    No second list

    Jobs stay there.

Why Albrecht Apps

No maintenance-software reference. We do not offer a second technician app.

From 2019 to 2024 Andrej Albrecht built the Android app for iTENDO: Bluetooth LE to sensors on an industrial tool holder for INNIRION. That is not a project in the industry on this page. Hardware and firmware stay with the manufacturer. Albrecht Apps takes the app, the backend, and the cloud.

App development. BLE app development.

What a first workflow can look like

Example, not a client project

A sensor the product does not speak

A reading from a device whose protocol the maintenance software does not have goes to their interface as a record. The job list stays there. Example, not a client project. If the device is already connected, this workflow does not exist.

Named work from another industry

The named industrial example is iTENDO for INNIRION: an Android app that reads sensor data from a tool holder over Bluetooth LE, built by Andrej Albrecht from 2019 to 2024. It is not a client project in the industry on this page.

The published IIoT article describes how a tablet companion app could be built today. It is a method article, not a delivered client project, and not evidence for this industry. Method article on an IIoT companion app

Questions before a project

We already have the technician app.
Then a second one is the wrong project. Bring only the device the app will not take.
We ship the browser on purpose.
That is a product decision. A studio does not replace it with a second screen.
The plant wants SAP on the phone.
Packages exist for that. It is not a project to rebuild the job list.
Should we advertise this?
No. Without the missing device protocol there is nothing to build.

Show the protocol, or stop

Bring the device your product will not take. Without that boundary there is no scope.

Book a technical assessment (opens Calendly in a new tab) 30 minutes. Bring the device your product will not take.
30 min technical assessment Book a technical assessment (opens Calendly in a new tab)