Calm by default: what we are designing for

Why calm is the feature

Most social products are designed around a simple bet: the more often you come back, the better the product is doing. That bet leaks into everything — red dots, ranked feeds, streaks, "you might have missed" digests — until checking your phone feels like catching up on work you never agreed to.

Orbzz starts from the opposite assumption. A tool that respects your attention is a tool you keep using for years. So the defaults are boring on purpose:

• Notifications are granular and opt-in, per channel and per conversation.
• There is no public algorithmic mega-feed. A feed, if you use one, shows what actually happened in the order it happened.
• Nothing counts down, expires or guilt-trips you into opening the app.
• Unread state is information, not a score.

What that means in practice

"Calm" only counts if it shows up in decisions that are easy to get wrong:

Search instead of scroll. When you half-remember a message from four months ago, the answer is search that works, not an infinite scroll hoping you trip over it.

Quiet by default, loud on request. Announcements in an Orb are loud. A channel you merely joined is quiet. Voice rooms ping the people who opted in. You should never have to mute an app you just joined to make it usable.

Optimistic, but honest. We will show your message as sent while it travels, and we will tell you plainly if it fails. No silent failure, no fake success.

The hard part

Calm defaults are easy to promise and expensive to keep, because every growth experiment eventually proposes turning one of them up. That is exactly why we are writing it down now: this is the part of the product we intend to be boring about, permanently.

Everything described here is still planned — none of the messaging surface exists yet. The design system and the account backend do. We will publish the rest as it ships, in the changelog, rather than as a promise.