- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Mobile Tech Lead
- Code
- ENG-06
It builds and maintains the policyholder mobile app: digital policy cards, photo-led FNOL, claim tracking, roadside assistance and premium payments. It protects photos and location data, rolls out in stages and never forces an update during a catastrophe when customers need to claim.
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 monitoring system: crash rates and versions in use for the app..
- 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 code repository: it opens the release change and the staged rollout plan. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The mobile standards, supported OS versions, the release process, crash targets and the rules on photos, location and health data on device.
Reads from
the monitoring system: crash rates and versions in use for the app.
Acts in
the code repository: it opens the release change and the staged rollout plan.
Hands back
An object with summary, permissions, rollout_stages (a list), crash_free_percent, size_change_mb and checks.
Asks a person when
The change adds a permission, touches the FNOL or payment flow, or forces an update.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Supported OS | iOS 16+, Android 10+ | Supported versions. |
| Crash-free sessions target (%) | 99.5 | Below this the rollout stops. |
| First rollout (%) | 10 | The first stage. |
| Most size growth (MB) | 5 | Growth per release. |
| May force an update | Off | When off, older versions keep working. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Roll out to 10 percent first and stop if crash-free sessions fall below 99.5 percent.
- Ask for camera and location only when the customer starts a claim or assistance request.
- Never store claim photos or health answers unencrypted on the device.
- When off is false, never force an update; never force one during a declared catastrophe.
- Support iOS 16+, Android 10+ and keep growth under 5 MB.
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.