Guides

Useful things to read on the way.

Short, practical material for anyone planning an app or website. No sign-up required.

Writing delivery status messages

Lead with what changed, then what the person should do, if anything. “Your parcel is with the driver. Expected 14:10–15:10.” works; “Exciting news about your order!” does not. Keep the most important words inside the first 40 characters, because lock screens cut text short. Use real time windows and update them honestly when they change. Do not send a notification for a status nobody needs to act on.

Offline-first, explained

An offline-first app assumes the connection might vanish. It saves actions on the device first, shows the user they are saved, and sends them when signal returns. The hard part is not the code; it is deciding what happens when two people change the same thing while offline. We agree those rules with you before building, in plain language: “the most recent change wins”, or “the dispatcher’s change wins”.

A one-page brief template

  1. What needs to move? The thing, information or person your product helps along.
  2. Who is involved? Each kind of user and what they need to know.
  3. Where does it get stuck today? The specific moments of delay or confusion.
  4. What must the first version do? Three to five things, not twenty.
  5. Fixed dates and constraints. Seasons, events, existing systems.
  6. Budget range. A wide one is fine; it helps us suggest a sensible route.

Glossary

Cross-platform
One codebase that produces both iOS and Android apps.
Push notification
A message an app sends to a phone’s lock screen, with permission.
Data safety form
Google Play’s required summary of what data an app collects.
Rollback
Returning to the previous version if a release causes trouble.
WCAG
The international guidelines for accessible digital content.