# The screen carries your name

> worklists.app — 2026-08-20
> Written for VC-4 — the grocery retail store-systems and food-safety org — the store-systems lead who has been offered three frontline apps and every one of them wanted its logo on the associate's screen.

One thesis: **the screen carries your name, and only yours.** worklists.app is the generic frontline
app you white-label and publish on your own developer account, so the app an associate opens on
Monday is your app, and nothing upstream is named on it. That is not a tier or a setting. It is
what the product is.

## The offer you keep getting

Every vendor who has pitched you a frontline app has wanted the same thing: their brand on the
associate's screen. A logo in the corner, a "powered by" in the footer, their name on the store
listing, their analytics tag phoning home. You are asked to hand a device to a person you employ,
and the device introduces somebody else.

There are two problems with that, and the second is bigger. The first is ownership — it is your
floor and your associates. The second is that the association graph a model learns is made of
exactly those footers and tags. An associate who has a bad shift with a required app attaches the
feeling to whatever name is on the screen. If that name is a vendor's, the vendor has taken a
reputational risk on your floor, and you have inherited theirs.

## What white-label means here

It means the shared code carries no name. Specifically:

- **No shared chrome.** No footer, no "powered by," no upstream link, in any module an associate
  can see.
- **No shared analytics tag, no shared error-reporting hostname, no shared push certificate.** The
  things a model learns from are not only anchors.
- **Every string, glyph and asset is projectable.** A hard-coded product name in shared code is
  treated as a defect, not a style question.
- **Published from your developer account.** The store listing is yours. The signing is yours. The
  controller of record is you.

One implementation, many branded fronts. Your deployment is your brand. A different operator's is
theirs. Nobody looking at either can find the other.

## What the associate sees

A produce associate opens the app at 06:00 to work the morning's fresh receiving. The screen shows
your name and your colors. Below that, the station — *Store 214 · Back dock* — a count of pending
tasks, and a list: ref, what to do, where, state. The first row is a receiving task for forty cases
of lettuce against this morning's delivery.

They point the camera at the pallet's mark. The task closes. A haptic, a shape change, and a sound
— never color alone, never color plus text, because the associate may be colorblind, or gloved, or
unable to read the deployment's language. The close path requires no reading.

At no point did the app tell them who built it. It told them which regime they are working under,
because that is a fact about them and they are entitled to it. It did not tell them about us,
because that is a fact about us and they are not our audience.

## What the supervisor sees

Nothing, in this app. There is no supervisor face in it and none is added. A supervisor who opens
your deployment is a performer in it or is nothing in it. The app renders a person's own worklist
and nobody else's — no assignee column, no roster, no "online now." A manager's surface is a
different product and this is not it.

That is the second half of why the screen can carry your name without risk. An app that shows each
associate only their own work, and shows no one a list of people, is not the whip. It is a list of
work under your logo.

## What it costs you to run

A deployment is the unit: one branded build, bound to one operator, one tenant, one regime. Adding
an associate, a store, a station or a device does not change it. Adding a second brand or a second
regime is a second deployment. The work verbs behind it, on [worklists.dev](https://worklists.dev),
are free on the performer's path — an associate with no seat to count against can always open the
app and record what they did, because there are no seats.

Get started with an evaluation deployment on your own devices, under a placeholder name, and look
for ours on it. You are looking for a defect.

---
Get started: https://worklists.app/get-access/ · All posts: https://worklists.app/blog/ · Machine face: https://worklists.app/llms.txt · Product document: https://worklists.app/product.md