Skip to main content

Module delivery

Module delivery 

Expand description

One delivery vocabulary, rendered the same in every conversation.

A message leaves a composer and may be queued, in flight, handed to a transport, acknowledged by its server, delivered to the other person’s device, read, refused, or left uncertain when the transport cannot say. Chat and Messages learn those facts from different systems, in different words, and each used to print its own: Messages had five honest labels, Chat had none at all except a line saying a send was refused.

DeliveryState is the one vocabulary. A transport maps its own states onto DeliveryStep — a plain rename, no judgement — and DeliveryState decides the word, the glyph and the tone. Both apps paint it through DeliveryFace, so “delivered” looks the same wherever a person meets it, and a state that cannot be known says so instead of pretending.

Structs§

DeliveryFace
A delivery state as it is painted: a small glyph and its word, in one line.

Enums§

DeliveryState
The state a line shows, in the one vocabulary both apps speak.
DeliveryStep
What a transport reported, before this toolkit decides how to say it.