Device APIs with Wisej.Hybrid.Device

Hybrid & Native PackagingModule 5The samples are ready before the course is: the module outline is on learnwisej.com, and the lessons, the knowledge checks and the hands-on labs follow when it launches — free, with an AI tutor in every lesson.

See the outline

The work-order detail page of the walkthrough — FieldOps · WO-4187, Chiller 3 — pressure fault, Meridian Foods · Unit 7, Halstow Industrial Park, the SLA chip, the device actions (Take Photo DEVICE · Signature · Navigate DEVICE in the client; Upload Photo · Signature · Open route in a browser), the Device.Valid = true|false note, the PHOTOS strip with three slots, the SIGNATURE pad and the STATUS strip that says what the last action did, with N photos · signed/unsigned on the right.

The source of this sample

iceteagroup/LearnWisej-SamplesHybrid and Native Packaging Course/Module 5

Browse this folder on GitHub

Or clone it: git clone https://github.com/iceteagroup/LearnWisej-Samples.git — then open FieldOps.slnx in Visual Studio and press F5.

Run it

cd "Hybrid and Native Packaging Course/Module 5/FieldOps"
dotnet run -f net10.0 --urls http://localhost:6305

Open http://localhost:6305, double-click WO-4187 Meridian Foods. Hybrid client: as in Modules 3–4 (FieldOpsServer now points at port 6305; Android emulator http://10.0.2.2:6305/).

What to try

Action	Expected result
Browser: open WO-4187	Upload Photo · Signature · Open route, Device.Valid = false.
Draw in the pad, press Signature without a name	Type the signer's name under the signature.
Type a name, press Signature	Signed by … · N KB PNG · hh:mm server time; PNG + record in %LOCALAPPDATA%\FieldOps\signatures\WO-4187.
Upload Photo with a phone picture	Stored downscaled to 1600 px; Photo uploaded · (original) KB → (stored) KB on the server; thumbnail in the strip.
Open route	The site address opened as a maps link in a new tab.
Client: Take Photo	Reason sentence → camera prompt → camera; back out → Capture cancelled; a photo → 1 photo stored · NNN KB · thumbnail pushed.
Client: refuse the camera / location, then refuse for good	Amber may not use … this time with the manual path; then red switched off … in the phone's settings and Open Settings (Device.AppInfo.ShowSettingsUI()).
Client: Navigate	Location → Arrival stamped hh:mm · ±(accuracy) m · (distance) km to the site → the maps app; no fix → No location fix … route opens from the site address.
POST /dispatch/assign while the client is open	New work order notification and a Next job reminder scheduled 30 minutes before the appointment.

What was verified, and how

• Builds: FieldOps (net10.0-windows, net10.0); FieldOps.Client + FieldOps.Offline for net9.0-windows10.0.19041.0 and net9.0-android: 0 errors, 0 warnings.
• Browser (fieldops-m5): WO-4187 matched the fallback scene (Upload Photo, Signature, Open route, Device.Valid = false); the signature pad was drawn with pointer events, the no-name path refused, the named signature saved (4 184-byte PNG + JSON record on disk, logged).
• Upload downscale (server half), run on net10.0 with the same PhotoStore source: a 4000 × 3000 image became a 1600 × 1200 JPEG; thumbnails render as data URIs.
• Windows Hybrid client: the session logged capabilities: Device.Valid=True camera=CapturePhotoAsync navigate=Geolocation+Map reminders=LocalNotification; a dispatched order logged both Device.LocalNotification.Schedule "New work order" and "Next job" … at 17:05 (30 minutes before its appointment).
• Not exercised: the camera, location, maps and permission prompts (they need a click in the native window or a phone; no emulator here), Responded (needs a tap on the notification), the browser Open route and Upload Photo clicks (external site; native file picker).

Where this sample differs from the lesson

• Signer's name field. The lab requires the signer's typed name; the pad shows no field, so a Signer's name box sits under the pad.
• The status flow stays (Module 1) as a compact UPDATE STATUS row under the media; the detail page does not show it.
• Thumbnails are data URIs, not a URL handler. The lesson describes serving photos through a handler that checks the session's work order; FieldOps never exposes a URL at all — the page gets a small server-rendered thumbnail of the order it has open. Same guarantee, less surface.
• Biometric unlock is described by the lesson but not built: it needs the separate Wisej-4-Hybrid-Authentication packages; the capability matrix marks it absent everywhere, as the browser scene does.
• Distance on arrival uses Wisej.Hybrid.Location.CalculateDistance (verified by reflection), and the site coordinates are seed data.
• Inside a Wisej Page, Location resolves to Control.Location; the code writes Wisej.Hybrid.Location in full.