UAE · ENBook a demo
RetailEngineeringAssistant

Shopping App Development Agent

Builds and maintains the retailer's shopping app.

Shopping App Development AgentMobile Development Agent · Application Engineering
Industry
Retail
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
E-commerce Director
Code
ENG-06

It builds and maintains the shopping app's features, such as barcode scan in store, the digital loyalty card, click-and-collect check-in and push notification preferences, from the design spec. It opens the change with tests and prepares the store submission notes, keeping old app versions working.

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 code repository: the app code, tests, crash reports and analytics for the feature named..

  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 E-commerce Director with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens a pull request with the change, tests and rollout plan. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The app engineering guide: the app architecture, supported OS versions, the minimum supported app version, the push consent rules, store submission guidelines, offline behaviour in stores and the app analytics plan.

Reads from

the code repository: the app code, tests, crash reports and analytics for the feature named.

Acts in

the code repository: it opens a pull request with the change, tests and rollout plan.

Hands back

An object with files_changed (a list), tests_added (a list), platforms, rollout_plan (stages and stop conditions), store_submission_notes and pull_request_description.

Asks a person when

The change touches payments, scan and go checkout, loyalty points or the data the app collects.

ApproverE-commerce Director

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Oldest OS versions supportediOS 16, Android 10The change must work on these and newer.
Crash-free sessions target (%)99.5A release that would fall below this is held.
Loyalty card works offlineOnWhen on, the loyalty card and receipts work without signal in store.
First rollout stage (%)10New versions go to this share of users first.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Support iOS 16, Android 10 and newer, and never break the minimum supported app version's API calls.
  • When on is true, the loyalty card, barcode and receipts work without signal.
  • Ask for push permission only after the shopper chooses a notification type, and respect their preferences.
  • Release to 10 percent of users first and stop if crash-free sessions fall below 99.5 percent.
  • Never store card data or loyalty credentials in plain text on the device.

See the Shopping App 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.

Shopping App Development Agent · Retail | Basinwright Industries