Platform and Accessibility

Background processing and scheduled jobs

Several things the app promises only work if something runs while nobody is looking. This is that something.

From GrowthAndroid · iOS · Web · Windows

Promises that depend on a schedule

A payment reminder that goes out on the due date, a daily list of overdue bills, an alert when stock drops past its level: each of those is a promise that the app will do something at a time when the business is not using it.

That only holds if the work is scheduled server-side rather than waiting for somebody to open the app. It is invisible when it works, and the visible failure is subtle — reminders that arrive days late, or only when somebody happened to log in.

What you actually do

  1. 1Set the triggers

    Credit days, stock levels, message settings.

  2. 2Close the app

    The schedule does not depend on you.

  3. 3Things happen

    Reminders sent, alerts raised.

  4. 4You are told

    Through notifications rather than by checking.

Inside Platform and Accessibility

The app itself, wherever you use it: Android, iOS, the browser and Windows, kept in step so a bill raised on the counter phone is on the office laptop a moment later. The language, the notifications and the work that runs in the background live here too.

You notice this area when you switch devices, hand the phone to a staff member who reads another language, or expect a reminder to have gone out while the app was closed.

What it works with

The features that run on it.

Questions people ask

Do reminders need the app to be open?

No — the scheduled work runs independently of whether anyone is using the app.

What runs in the background?

Reminders, the daily overdue alert, low-stock alerts and the messages tied to billing events.

How do I know it worked?

The visible evidence is the alerts and messages arriving on time rather than when somebody next logs in.

The part that works while you are closed

Half the app’s promises are about things happening when nobody is watching.