- Ya
- 14 Agosti 2026, 06:02 UTC
- Mwandishi
- kamo
- Ahadi ya
- d94a336
Reminders had nowhere to arrive. The calendar's popup was a plain alert in the top corner of whichever page happened to be open, it vanished on a timer, and anything raised while the member was elsewhere was simply lost — the socket publishes, and a publish nobody is subscribed to succeeds and disappears. So notifications are now stored as well as published, and the browser reads both through one context mounted above the whole tree. What arrives while you are here is pushed; what arrived while you were not is claimed on the next connection, once, so two tabs opening together do not both raise the same pile. The deck sits in a corner of the viewport, over whatever page is underneath. Cards stack rather than list — four reminders landing together, which is what a company event plus your own meeting does, would otherwise take the right-hand third of the screen — and hovering fans them out. Each card leads with the thing every notification in this product has in common: a clock. It counts down to the event, offers now, later or not at all, and drains a rail as its own welcome runs out, which stops while you are reading it. Swipe right to be rid of it. Everything else is behind the two menus: snooze by five, ten, fifteen, thirty, an hour, or until five minutes before the thing starts; mute this kind of notification outright; open the settings. Producer-supplied actions ride along, so a callback offers the lead's number and a meeting offers its join link. Links go through the router, never a document load — the deck can fire at any moment and a navigation here would tear down an unsent draft. The bell in the top nav is fixed chrome for the same reason the compliance clock is: a bell someone can unpin and then not be told anything is worse than none. Behind it is the history, filtered by kind or by unread, with do-not-disturb where a member notices the noise. The tab tells you too. TabAttention already flashed the title and badged the favicon for chat, leads and support; unread notifications join it, above chat because they are timed — a reminder that a call is due in five minutes stops being useful five minutes from now. Sounds are synthesised rather than loaded, so the first notification of a session is not the silent one on a slow connection. Desktop notifications are raised only when the tab is hidden, and permission is asked at the moment the member turns the switch on rather than on page load, which is the pattern browsers suppress and people reflexively deny.