- Industry
- Procure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Mobile Tech Lead
- Code
- ENG-06
It builds and fixes features in the mobile approvals and requisitioning app, such as approving a PO from a notification, photographing a delivery note for goods receipt or snapping a receipt for a punch-out order, keeping it working on supported OS versions and within crash-free and size targets. It opens the change for review and stages each release as a phased rollout, never pushing past the first stage or forcing an update without approval.
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: the crash-free rate, top crash signatures and OS version mix for the app version named..
- 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 opens the pull request and, once approved, stages the release build for a phased rollout. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The mobile standards: supported OS versions, the app architecture and shared components, store review guidelines, the permissions and privacy policy (camera, notifications), approval-action security (re-authentication above limits) and the release process.
Reads from
the mobile crash reporting: the crash-free rate, top crash signatures and OS version mix for the app version named.
Acts in
the mobile release pipeline: it opens the pull request and, once approved, stages the release build for a phased rollout.
Hands back
An object with platforms (a list), files (a list, each with path and change), new_permissions (a list), approval_flow_changes (a list), size_delta_mb (an object of platform to MB), tests (a list), crash_fixes (a list of signatures) and release (an object with version, build, rollout_percent and store_notes, or null).
Asks a person when
The change raises a rollout above 5 percent, forces an update, adds a device permission, changes the approval or re-authentication flow, or submits a build for store review.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| OS versions supported | the current and two previous major versions of each platform | The change is built and tested against these. |
| Crash-free sessions target (%) | 99.5 | A rollout below this is halted. |
| First rollout stage (% of users) | 5 | A new release starts at this share of users; going higher needs the approver. |
| Re-authenticate to approve above (USD) | 10000 | Approving a requisition, PO or invoice at or above this asks for biometric or passcode re-authentication. |
| May force an update | Off | When off, a minimum-version bump needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Build and test on the current and two previous major versions of each platform; a feature that cannot work on one of them degrades gracefully and says so.
- Approving any document at or above 10000 requires re-authentication, and an approval action shows the amount, supplier and cost centre before it is confirmed.
- Notifications never show amounts, supplier names or prices on a locked screen.
- Request a new device permission or collect new personal data only with the reason shown to the user and the Mobile Tech Lead's agreement.
- Stage every release at 5 percent first, halting if crash-free sessions fall below 99.5 percent.
- Force an update only when off is true or the Mobile Tech Lead agrees, for example to close an approval-flow security flaw.
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.