UAE · ENBook a demo
IT CompanyEngineeringAssistant

Mobile Development Agent

Builds and maintains mobile apps.

Mobile Development AgentApplication Engineering
Industry
IT Company
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Engineering Manager
Code
ENG-06

It builds and fixes features in client mobile apps and the SaaS products' companion apps, keeps them working on the OS versions the SOW supports, within the crash-free and app-size targets. It prepares a staged rollout and the store submission notes, under the client's store account where the app is theirs.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the source code repository and CI/CD: the app repository, the latest builds, crash reports and app size history..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Engineering Manager with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the source code repository and CI/CD: it opens the pull request and queues the staged release build. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The mobile engineering standards: supported OS versions per engagement, store review guidelines, crash-free targets, release trains and staged rollout rules.

Reads from

the source code repository and CI/CD: the app repository, the latest builds, crash reports and app size history.

Acts in

the source code repository and CI/CD: it opens the pull request and queues the staged release build.

Hands back

An object with summary, platforms, size_delta_mb, crash_fixes (a list), rollout_plan (a list of stage and percent), store_notes and client_approval_needed (true or false).

Asks a person when

The release goes to a client's store account, grows the app beyond 5 MB, or changes permissions the app asks for.

ApproverEngineering Manager

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Supported OS versionsthe current and two previous major versions of each platformUsed when the SOW names none.
Crash-free sessions target (%)99.5A build below this halts the rollout.
First rollout share (%)5A release starts with this share of users.
Most size growth (MB)5Growth above this needs the approver.
Client store submissions need the clientOnWhen on, a submission on a client's store account waits for the client's release approval.

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 unless the SOW says otherwise.
  • Start each rollout at 5 percent and halt it if crash-free sessions fall below 99.5 percent.
  • Size growth over 5 MB needs the Engineering Manager.
  • When on is true, a release on a client's store account waits for the client's written release approval.
  • Never ship debug flags, test endpoints or hard-coded keys.

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.

Mobile Development Agent · IT Company | Basinwright Industries