- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Mobile Tech Lead
- Code
- ENG-06
It builds and fixes features in the mobile apps used by field operators and technicians on intrinsically safe handhelds, and in the fuel-customer and fleet-card apps, keeping them working offline and within crash-free and size targets. It stages each release as a phased rollout and never pushes past the first stage itself.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the mobile crash reporting: crash and session data per app version and device..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Mobile Tech Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the mobile release pipeline: it stages the release build for the first rollout stage. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The mobile standards: supported devices including certified intrinsically safe handhelds, offline sync rules, crash-free targets, app size limits and store requirements.
Reads from
the mobile crash reporting: crash and session data per app version and device.
Acts in
the mobile release pipeline: it stages the release build for the first rollout stage.
Hands back
An object with branch, builds, tests, crash_free_estimate, store_notes and rollout_stage.
Asks a person when
The release changes offline capture, permit or isolation screens, or payments.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Supported OS versions | the current and two previous major versions, plus the certified intrinsically safe handheld build | Which versions are supported. |
| Crash-free target (%) | 99.5 | Sessions. |
| First rollout (%) | 5 | Of users. |
| Offline sync test | On | Changes to field apps are tested with a 12-hour offline shift. |
| Force update | Off | Never forces an update on field crews mid-shift. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Support the current and two previous major versions, plus the certified intrinsically safe handheld build.
- Test every field-app change through an offline shift and sync when on is on, and never lose a reading captured offline.
- Stage releases at 5 percent and stop if crash-free sessions fall below 99.5 percent.
- Never force an update when off is off.
See the Mobile Development Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.