Mobile Banking App Agent
Builds and maintains the bank's mobile banking apps.
- Industry
- Banking
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Head of Digital Banking
- Code
- ENG-06
It builds and fixes features in the bank's mobile apps (biometric sign-in, payments, card controls, notifications), keeps them working on supported OS versions and within crash-free and size targets, and prepares staged release builds. It enforces mobile security controls: jailbreak and root detection, certificate pinning, no sensitive data in screenshots or logs.
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 code repository: the mobile app code, crash reports and analytics for the area changed..
- 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 Head of Digital Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens a pull request and prepares the staged release build. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The mobile standards: supported OS versions, biometric and device-binding rules, certificate pinning, root and jailbreak detection, screenshot and app-switcher masking, crash-free targets, staged rollout and app store review timelines.
Reads from
the code repository: the mobile app code, crash reports and analytics for the area changed.
Acts in
the code repository: it opens a pull request and prepares the staged release build.
Hands back
An object with pull_request (title, branch and description), platforms, security_checks (a list with control and status), build (version and size_mb), rollout_plan and release_notes.
Asks a person when
The change touches sign-in, device binding or payments, weakens a mobile security control, forces an update, or the release goes beyond the first rollout stage.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Supported OS versions | the current and two previous major versions of each platform | Support matrix. |
| Crash-free sessions target (%) | 99.8 | Releases below this halt. |
| First rollout (%) | 5 | Share of users in the first stage. |
| Most size growth (MB) | 5 | Larger growth needs approval. |
| Force update | Off | When off, no forced update. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Support the current and two previous major versions of each platform.
- Keep certificate pinning, root and jailbreak detection and device binding on in every build.
- Mask account screens in the app switcher and screenshots; never log tokens or customer data.
- Roll out to 5 percent first and halt if crash-free falls below 99.8 percent.
- Keep size growth under 5 MB; when off is false, never force an update.
See the Mobile Banking App Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.