Platform
Nothing to install. Nothing for IT to approve.
The platform runs in the mobile browser and installs to the phone home screen, where it opens full screen and behaves like an app. A contractor pumper can be working in under a minute.
01 At the tank
07:12no signalTANK 3 · OIL
MethodinnageoutageGauge14 ft 7 3/8 inTemp78.4°FBS&W0.6%No paper table to carry. The strapping table turns the gauge into barrels.
02 Driving out
Queue3 waiting- gauge TK0307:12
- haul 447105:40
- amend TK0106:55
Held on this phone. Times stay as observed, not as sent.
03 Back in range
Queue0 waiting- gauge TK03sent 09:41
- haul 4471sent 09:41
- amend TK01sent 09:41
Every entry accounted for. A day of gauges is never silently dropped.
Add to home screen
The platform installs from the browser. There is no store listing in the way, and no separate build to keep in step.
- No app store review to wait on before a fix reaches a crew.
- No MDM approval cycle before a contractor can start using it.
- No version fragmentation — everyone is on the same build the moment it ships.
- Updates land when they ship rather than when someone updates their phone.
What the field actually does on it
The mobile experience is built around three jobs, not around a shrunken copy of the desktop interface.
- Record a tank gauge, a hauled load or a correction at the battery.
- Acknowledge an alarm from wherever the person on call is.
- Check well and facility status from a truck.
It works with no signal
Entry is captured and queued on the device with no connectivity, and syncs when signal returns.
- The queue survives the browser closing and the phone restarting.
- The pumper can see what is queued, what has synced, and what failed.
- Observation time is captured on the device; send time is recorded separately.
Built for the conditions
Designed for a phone held in a gloved hand, in sunlight, at a location with no bars.
- Touch targets sized for gloves.
- Contrast that survives direct sun.
- Low training burden, because crew adoption is the usual reason field deployments fail.
Why this is an advantage rather than a compromise
Installing to the home screen is sometimes framed as a lesser version of a native app. For this use case it is the better arrangement, and the reasons are practical rather than technical.
A native app puts a store review between a fix and the crew that needs it. It puts an MDM approval between a new contractor and their first shift. It guarantees that at any moment some portion of a crew is running a build from two months ago, which means a bug you already fixed is still in the field.
None of that applies here. There is one build, everyone is on it, and a pumper who was hired this morning can be recording gauges before lunch.
Common questions
Is there an iOS or Android app?
There is no store listing. The platform runs in the mobile browser and installs to the home screen from there, which is what removes the store and MDM approval steps entirely.
What happens to a gauge recorded with no signal?
It is captured and queued on the device, and sends when signal returns. The queue survives the app closing and the phone restarting, and the pumper can see exactly what is still waiting.
Will our pumpers need training?
The field surfaces are deliberately narrow — record a gauge, record a haul, acknowledge an alarm, check status. Crew adoption failure is the usual reason these deployments die, so the field experience is scoped to what the crew actually does rather than to what the platform can do.
See it against your own wells.
A demo runs against synthetic data first, then against a read-only connection to your system of record if you want to see real numbers.