CommunicationOS

Native clients

Five native clients built for speed

Real SwiftUI on macOS, low-power background sync on Android and an offline queue on every build. The same search index answers on all five.

5

Native platforms

38 MB

macOS binary size

80ms

Cold launch time

Unlimited

Offline queue depth

Platform builds

Software written for each device

We compile a binary per operating system instead of wrapping a website in a heavy container. Each app uses the platform's own interface primitives, notifications and storage engine.

CommunicationOS as a 38 MB SwiftUI application on macOS, with the iOS client recording a voice reply beside it.

CommunicationOS

SwiftUI
KN

Karim Nassar

one contact since 2016

Parcel cleared customs. Sending the manifest photo now.

Got it. Jan will be at the vault from 15:30.

queued, sends on reconnect

Web

Runs in Chrome, Safari, Firefox and Edge with the full keyboard model and a client-side index cache.

app.commsos.com

macOS

Written in SwiftUI and AppKit. Sits at 45 MB of memory when idle and opens in under 80 milliseconds.

Universal, 38 MB

iOS

Built for fast mobile work with one-tap voice note capture, background uploads and swipe assignment.

iOS 17 and later

Android

A background sync engine that keeps up with high-volume WhatsApp groups without draining the battery.

Android 12 and later

Windows

Native WinUI 3 controls, custom keymaps for dense desks and a tray icon that keeps sync running.

Windows 11

Shared search index

The same fast search on every screen

A local SQLite index runs on the device itself. A query hits local storage first, so results come back on a weak mobile connection at roughly the same speed as on a desk.

Local database cache

The most recent ninety days of message text and contact records sit in device storage.

Identical query results

Searching an invoice number returns the same message list on an iPhone as it does on the desktop.

Offline filters

Filter chats by label, sender or network with no connection at all.

Offline queue

Write replies from an airplane seat

A vault has no signal and a flight has no signal. The app keeps working: triage the queue, write the answers, attach the files. The local queue tracks every outbound message and sends them in order the moment you reconnect.

Local write cache

Outbound messages queue on device with a pending marker until a network handshake succeeds.

Ordered dispatch

Messages go out in the order you wrote them, so the conversation still reads correctly.

Failed send alerts

If a carrier drops an SMS, the client holds the draft and tells you to retry.

Queue, offline 41 min

Karim Nassarpending
Sarah Feldpending
Lin Zhaopending

sends in order on reconnect

Keyboard model

Run the whole inbox from the keyboard

Clear hundreds of messages without touching a trackpad. The bindings are the same on all five clients, so muscle memory carries from the desktop to a phone keyboard.

Default bindings

remappable
Cmd KOpen the command palette
G then UGo to the unread queue
EArchive or resolve the thread
AAssign to a teammate
SSnooze for later
Cmd EnterSend and resolve

Per platform

What differs between the builds

The features are the same everywhere. The machinery underneath is not, so here is what each client runs on.

CapabilityWebmacOSiOSAndroidWindows
Interface frameworkReact DOMSwiftUISwift, UIKitComposeWinUI 3
Local index cacheIndexedDBSQLiteSQLiteSQLite, RoomSQLite
Offline queueBrowser cacheOn diskOn diskOn diskOn disk
Global search hotkeyIn tab onlySystem wideNoneNoneSystem wide
Background syncService workerDaemonBackgroundTasksWorkManagerBackground task
Drag and drop filesIn windowNativeSplit viewDrag to appNative
Push notificationsWeb PushAPNsAPNsFCMWNS

Every client ships from the same release train, so a feature lands on all five in the same week.

Put the inbox on every machine you use

Native builds for macOS, Windows, iOS and Android, plus the web app. One account signs in to all of them.

No card required. Production deployment takes under an hour.

Book a demo