AR Defence

Customer Integration Docs

Build, deploy, and integrate a customer web app into the AR Defence host platform. This page is the customer-facing implementation guide. Use the separate build page when you need to generate or submit a client release package.

Open Build Page Open SDK Guide

Platform Overview

The solution is split into a native host app, a customer web app, and an AR Defence web integration layer.

1. Native Host App

Flutter container with RFID, NFC, QR, Bluetooth, diagnostics, and native settings.

Android and iPhone runtime
Hardware access and permissions
Shared multi-client pilot support

2. Customer Web App

Regular website, SPA, or PWA loaded inside the host app WebView.

Hosted on the customer domain
Own auth, backend, and business flows
Calls AR Defence bridge or SDK

3. Integration Layer

Bridge or SDK that connects the browser code to native host capabilities.

`ar-web-bridge` for simple websites
`ar-host-sdk` for PWA / SPA apps
Versioned via `cdn.lotix.co`

Deployment Endpoints

Use the stable production URLs below. Keep customer integrations pinned to explicit bridge versions.

Web Bridge CDN

https://cdn.lotix.co/ar-web-bridge/0.1.0/ar-web-bridge.bundle.js

Host SDK CDN

https://cdn.lotix.co/ar-host-sdk/0.1.0/ar-host-sdk.js

Customer Flow

Recommended pilot flow from build definition to production integration.

Create a build request

Provide client name, embedded URI, app identity, environment, and platform targets.
Generate build package

Download the ZIP or submit the request to the build backend for automated artifacts.
Deploy the web app

Host the customer web app on a stable HTTPS domain controlled by the customer.
Integrate bridge or SDK

Use the bridge for simple websites or the SDK for custom event handling and resolution logic.
Install the host app build

Distribute the Android/iOS pilot build and load the customer URI through the shared host app.

Integration Examples

Use the website bridge for standard embedded sites. The full SDK guide is on the dedicated SDK page.

Regular Website: `ar-web-bridge`

Fastest integration path. Best for standard sites that want resolved RFID/NFC events with minimal setup.

<script>
  window.AR_CONFIG = {
    gatewayUrl: "https://customer.example.com/personnel/resolve",
  };
</script>
<script src="https://cdn.lotix.co/ar-web-bridge/0.1.0/ar-web-bridge.bundle.js"></script>
<script>
  window.AR.on("rfid.personnel", (person) => {
    console.log("Resolved RFID person:", person);
  });

  async function startRfid() {
    await window.AR.startRfidScan();
  }
</script>

Need SDK integration?

Use the dedicated SDK page for PWA / SPA integration, raw events, resolver wiring, and the full function reference.

Go To SDK Guide

Example Screens

The screenshots below document the current pilot flow in the shared host app. Drop the matching image files into assets/screenshots/ to replace the placeholders.

crew-reporting-idle.png

Crew Reporting: idle state

Initial crew page with zero members, scanner controls, and bridge ready state.

rfid-connecting.png

RFID reader connection

Native loading state while the host app connects to the RFID reader.

rfid-waiting.png

RFID scan active

Batch scan highlighted with waiting status while RFID scanning is running.

crew-reporting-populated.png

Crew filled with members

Resolved RFID entries are added to the active crew and counted in the header.

crew-reporting-reported.png

Reported crews

Previously reported crews remain visible while the next active crew continues scanning.

tag-assignment-list.png

Tag assignment list

Member list used for selecting a person before assigning RFID or NFC tags.

tag-assignment-edit.png

Tag assignment edit

Edit panel for member ID, member name, and RFID / NFC assignment actions.

qr-scan-focus.png

QR focus scan

Native QR scanning view with a focus frame selecting a specific QR code in the camera feed.

crew-setup.png

Crew setup

Define crews, see current availability, and identify already reported crews.

user-menu-signout.png

User menu and sign-out

Current signed-in user name with menu access to sign-out flow.

microsoft-signout.png

Microsoft account sign-out

Microsoft account picker shown during the hosted sign-out sequence.

Provisioning Example

The shared pilot host app can also provision clients by QR payload.

{
  "clientId": "lotix-demo",
  "displayName": "Lotix Demo",
  "webUrl": "https://ar-demo.lotix.co",
  "environment": "pilot"
}