Handbook

Appearance

The Owner App ​

What this chapter covers ​

The owner app is Korido on the fleet owner's phone — a native companion that answers "how is my fleet right now?" from a pocket. This chapter describes who it serves, the fleet-at-a-glance experience it offers, the deliberate rule that it shows functional information only and never raw device telemetry, and how its notification preferences and push eligibility respect a person's sleep.

Who it is for ​

The owner app is for owners and managers who need to check on the fleet away from a desk. It is a glanceable, read-first surface, not a full operating console: the deep planning, mission creation, and evidence work stay on the fleet app in the browser. Sign-in is by WhatsApp OTP, matching how owners already receive alerts.

The guiding principle is that an owner should see everything that helps them run the business and nothing that only an engineer would read.

Fleet at a glance ​

The app opens onto the fleet the way an owner thinks about it: a live map and a searchable list. A live-map tab places the trucks on the corridor — moving, stopped, waiting, or offline — reading the same activity and position-freshness wire contract as the web app. A compact preview card can summarize a selected truck with primary actions, but the full picture always opens as a proper detail page.

A fleet tab lists every vehicle with search and filtering over a fast, virtualized list, so an owner with a large fleet can find one truck instantly. Selecting a vehicle opens its detail page — kept inside the tab navigation so the bottom menu and native back gesture stay available — organized into functional panels: the active mission and its route, the vehicle itself, connectivity, and its alerts. A vehicle wears an honest activity label straight from the fleet's own wire contract: "Stationné — dernière position connue" for a parked truck, an amber-shaded variant when its last position may be stale, and "Sans GPS" for a tracker that is talking but cannot get a fix. The vehicle panel gathers identity, the linked trailer, the effective driver's contact, speed, total distance, alert count, and a fuel reading shown as a "150 L · 62 %" figure — a plain "-" when the truck carries no fuel sender. A separate Connectivité panel answers "is the tracker still reaching us?" with connection state, time since last contact, and signal quality, standing in for the raw engine and sensor readings an owner has no reason to parse. A profile tab rounds out the app with the owner's own identity and settings.

Notifications, preferences, and quiet hours ​

The owner app shares Korido's notification stream with the driver app. Notifications arrive in the same five categories — mission, Route Guard, fuel, documents, and system — and tapping one deep-links straight to the relevant vehicle. Expo push dispatch is wired into the platform pipeline but currently gated off by worker configuration, so the in-app center is the live delivery surface until rollout enables outbound push.

What matters at the owner surface is control over the flow. A preferences screen lets an owner switch each category on or off and set a quiet-hours window so routine notifications defer to the end of the window instead of buzzing overnight. The one exception is deliberate: Route Guard alerts are treated as time-sensitive and are exempt from quiet hours, because a corridor deviation is the kind of thing an owner wants to know about the moment it happens. Quiet hours are evaluated in the owner's own local time, and the app auto-detects the timezone rather than asking anyone to pick one. On phones from vendors that aggressively kill background apps, a one-time onboarding nudge guides the owner to grant the battery permission that will let high-priority alerts through once outbound push is enabled.

An in-app notification center keeps the history regardless of what was pushed, so a notification an owner chose not to receive as a buzz is still there to read later. With push dispatch disabled, eligibility and deferral decisions are still part of the record, but no Expo push leaves the worker. The full notification pipeline — how records are created, made push-eligible, dispatched when enabled, and reconciled — is covered in Part 6 — Fleet intelligence.

The boundaries of this surface ​

  • Functional information only. The owner app deliberately shows what an owner needs to run the fleet — status, connectivity, position, mission, and fuel — and withholds raw device telemetry. Deep sensor diagnostics belong to operations tooling, not to the owner's glanceable view.
  • Read-first. The owner app does not create or edit missions and has no vehicle diary. Those workflows stay on the web fleet app.
  • Documents are metadata-only. An owner can see that a vehicle's documents exist; reviewing previews, diary history, and historical GPS tracks are not part of the owner mobile surface today.
  • A standalone native app. Like the driver app, it runs its own native release cadence and builds its screens for the phone rather than porting the web design system. It reaches the backend through the mobile API, which accepts only owner and viewer roles for these fleet reads.

How it connects ​