Brand
Voice and tone
Playful, witty and a little odd, including when things go wrong. Never at the expense of saying what happened.
Principles
- Playful, witty, quirky. We sound like the friend who’s organising movie night, not like a router manual.
- No emoji. Anywhere. Not in buttons, toasts, errors, docs, placeholders or examples. If a line needs an emoji to land, rewrite the line.
- Wit goes everywhere, errors included. A broken link or a host who left is still a moment we get to write well.
- The joke never replaces the facts. Every message says what happened and what to do next. A pun can sit next to the facts; it can’t stand in for them.
- Never blame, never mock. The person reading it didn’t break the internet. If someone did something on purpose (like the host removing you), say so plainly and kindly.
Style rules
- Short sentences. Contractions are fine and usually better.
- Headings and messages in sentence case. Labels go uppercase through CSS, never in the source text.
- Numerals for numbers: 3 people, 30 seconds.
- Timecodes in mono:
01:12:04. - At most one exclamation mark per screen. Most screens need none.
- No jargon. No status codes, protocol names or stack traces in anything a viewer reads.
- Our own name is always lowercase: sideby. See casing.
Do and don’t
| Situation | Do | Don’t |
|---|---|---|
| Link the room can’t play | That link is playing hard to get. We can play direct video files and YouTube links, so try one of those. | “Error: unsupported URL.” with no explanation. “You pasted a bad link.” blames the person. “This link has commitment issues.” is cute and leaves them stuck. |
| Host left | The host wandered off. We’ll hold the room for 30 seconds, then turn off the lights. | “HOST DISCONNECTED.” All caps reads as shouting, and it hides the 30 seconds that matter. |
| Can’t play on this device | Your device and this video aren’t on speaking terms. Ask the host for another link; everyone else keeps watching. | “This video can’t play here.” followed by a crying-face emoji. The emoji is banned, and the line still offers no way forward. |
| Reconnecting | The internet blinked. Reconnecting you now. | “Socket closed (1006). Retrying.” A protocol name and a status code mean nothing to a viewer. |
| Buffering | Your video is buffering. You’ll catch up on your own, and nobody else is waiting. | “Buffering!!! Hang tight!!!” An exclamation pile-up, and it skips the reassuring part: nobody is waiting on you. |
| Needs a tap | Your browser wants proof you’re here. Tap to start watching. | “Playback was blocked by the autoplay policy.” True, but it’s jargon and never says to tap. |
| Removed by the host | The host removed you from the room. Awkward. If it was a misclick, ask them for a new link. | “Kicked. Bye.” Mocks the person and leaves them nowhere to go. |
| Empty chat | No messages yet. Somebody has to go first. | “Nothing here yet.” It doesn’t say what’s missing. |
| Success | Loaded. Everyone is watching the same thing now. | “Success!” It’s loud and says nothing about the room. |
Checking a line
Before a line ships, read it back and answer three questions:
- Does it say what happened?
- Does it say what to do next, or that nothing needs doing?
- Would it still be kind if the reader were having a bad night?
If any answer is no, fix the facts first and keep the joke only if it still fits.