The chrt Driver App

What the app does, who it's for, and how to install it on iOS or Android.

The chrt driver app is the mobile client your drivers use in the field. It runs on iPhone and Android, picks up the orders dispatch assigns or offers, captures proof of delivery, and streams location back to the chrt web app so dispatch and shippers can follow each order in real time.

This page introduces the app and links to install instructions for both platforms.

Who the app is for

Anyone with the Member role on a courier or forwarder org who runs deliveries themselves — staff drivers, owner-operators, and onboard couriers. Dispatchers, managers, and admins use the chrt web app instead; the driver app does not have a dispatch or planning surface.

If your team hasn’t invited you yet, ask them to add you under Members settings. See Add an org member for the inviter side.

What you’ll do in the app

  • Offers — see new orders waiting on you, plus any incoming offers from the bidding marketplace.
  • In Progress — work the order you’re currently driving: stops, tasks, proof artifacts, messages with dispatch.
  • Completed — review orders you’ve finished and any open earnings statements.
  • Trackers — register hardware tracker devices (Tive, phone-as-tracker, OBC) onto cargo as you handle it.
  • Settings — your profile, location sharing, notification preferences, and org switching.

iOS vs Android

The two apps are intentionally close in shape — the same five tabs, the same order/task/artifact model, the same sign-in. The one significant difference today is offline mode:

  • Android has a full offline backbone. The app caches your assigned orders, queues task completions and proof uploads when you’re out of signal, and replays them automatically once you reconnect. A banner at the top of the app tells you when you’re offline and when changes are syncing.
  • iOS is online-first today. Cached reads exist for orders and task detail, but write actions (accepting an order, completing an artifact, sending a message) need a live connection.

Where flows in these docs diverge between platforms, we mark the iOS flow as primary and call out the Android offline behavior in a Note.

If you split a team between iPhone and Android drivers, the offline difference is the one place dispatch should know they’ll see different behavior. Everything else — accept, decline, start, capture, complete — works the same on both.

Install

After install, sign in with the same email your org uses on the web app.