Skip to content
Basin Thread

Add to home screen

Installing the platform to a phone home screen on iOS and Android, and what to expect from the offline queue.

The platform runs in the mobile browser and installs to the home screen, where it opens full screen and behaves like an app.

There is no app store listing. That is deliberate: it removes the store review between a fix and the crew that needs it, removes the MDM approval between a new contractor and their first shift, and removes version drift across a crew’s phones.

iOS

  1. Open the platform in Safari and sign in.
  2. Tap the Share button.
  3. Choose Add to Home Screen.
  4. Name it and confirm.

The icon appears on the home screen and opens full screen, without browser chrome.

Android

  1. Open the platform in Chrome and sign in.
  2. Open the browser menu.
  3. Choose Add to Home screen or Install app, depending on version.
  4. Confirm.

Signing in

Sign in once after installing. Sessions are server-side, so signing out — or an administrator suspending the account — takes effect on the next request rather than whenever a cached token would have expired.

A phone only ever holds the assets that user is granted.

The offline queue

This is the part worth testing before a crew relies on it.

  • Gauges, hauls and corrections are captured and queued on the device with no connectivity at all.
  • The queue survives the browser closing and the phone restarting.
  • Each queued entry carries a client-generated key, so a retried or double-tapped sync cannot create a duplicate reading.
  • Observation time is captured on the device at entry; send time is recorded separately. Interval maths always uses observation time.
  • The pumper can see what is queued, what has synced, and what failed.

Test it deliberately

Put the phone in aeroplane mode, record a gauge, close the browser completely, reopen it, and confirm the entry is still queued. Then reconnect and watch it send.

A field app that silently loses a day of gauges is worse than a paper sheet, and crews know it. Verifying this in week one is worth more than any assurance.

Conflicts

Two readings for the same tank and observation time, or a queued entry that lands after a server-side correction to the same record, are flagged for human resolution. They are never auto-merged and never resolved last-write-wins.

Updates

Updates land when they ship. There is one build and everyone is on it, so a fix reaches the whole crew at once with nothing to install.