Simplepush

Appearance

Names & Devices ​

In an organization, people are addressed and attributed by name, not by topic values or ids.

Member names ​

The name given at invite time (sp org members invite "Alice") is the member's identity in the org: it's what you pass to --member / -m when sending, and what comes back as recipient.name and actor.name when collecting. Member matching on sends is case-insensitive.

bash
sp task -m "Alice" --title "Quick question" --text-input "Where are the keys?"

Device names ​

Members can name each of their devices in the app under Settings → Device Name. Device names don't address anything (sends always go to a member's every device), but they show up in event attribution, so you can tell which device answered:

json
"actor": {
  "publicId": "usr_…",
  "name": "Alice",
  "devicePublicId": "dev_…",
  "deviceName": "Alice's iPhone"
}

That's useful for shared or role-based devices: a member like "Warehouse" with devices named forklift-tablet and office-desk tells you where an answer came from without extra bookkeeping.

Conventions ​

For larger orgs a naming convention helps senders find people and read event streams:

  • People: first name, or name-role (alice-eng, bob-dispatch)
  • Function accounts: the function (oncall, warehouse, front-desk)
  • Devices: location-device (berlin-printer-room, truck-3-tablet)