Case study · 2024

Smart Scan

Offline-first OCR correction for a container yard: low-confidence reads go to a person, and the correction syncs back once the network returns.

Runs on
iOSAndroid
Built with
Material · Ionic · Capacitor
Role
Owned delivery end to end, from offline sync to the app-store releases.

The problem

Container numbers are read by OCR as boxes move through the yard. Most reads are right. The ones that are not have to be caught before they reach the record, and the person who can check them is out in the yard, not at a desk.

The yard is where the network is weakest. An app that waits for a connection makes people wait too, or write things down to type in later.

Constraints

  • Connectivity drops in parts of the yard, often.
  • People wear gloves and work in sunlight.
  • A correction must never be lost, and must never overwrite a newer record.

Offline first

High-confidence reads go straight to the record. An uncertain read waits for a person. Both are stored on the device first and sync when the network returns.

Decisions

  1. Offline first, not offline tolerant

    Reads and corrections are written to a local SQLite store first and synced in the background. The app behaves the same with or without a connection.

    Trade-off. Every screen has to show whether its data is synced, which is more design work than pretending to be online.

  2. Conflict-safe reconciliation

    Local state is kept conflict-safe and reconciled when the device reconnects, so two edits to the same record resolve predictably instead of silently overwriting.

  3. Only the uncertain reads reach a person

    High-confidence reads go straight through. Low-confidence ones queue for a person, who confirms or corrects the number in seconds, with large touch targets and clear input states.

  4. Owned through to the store

    I owned delivery end to end: event-driven updates and push notifications, CI/CD, and the app-store releases for Android and iOS.

Result

  • Less of the yard's work done by hand.
  • One of 8+ web and mobile apps we shipped to 5,000+ active users.

Read deeper

  • Offline-first is a product decision

    A local database and a retry queue are implementation. The product decision is which actions may succeed before the server agrees, and what a person is owed when the server later disagrees.

  • The frontend is a control plane

    Operator interfaces work when navigation, state, and actions follow the system a person is responsible for. A dashboard that only reports on that system is a different product.

The screens are rebuilt in React with sample data. Open them from the work section.

Next: Smart Transport →