← about Cove

Welcome to Cove.

Someone in your group invited you. This page walks you through the whole thing — install the app, use your invite code, and find your way around. Plan on about ten minutes.

1Install Cove on your phone or laptop.

Cove runs as a web app that installs to your home screen or dock — just like a regular app. Nothing to download from an app store; the code loads once and stays offline-capable. Updates arrive automatically.

Open Cove →

On iPhone or iPad (Safari)

  1. Open app.cove.oap.dev in Safari. Chrome and other browsers on iOS forward to Safari when you install anyway.
  2. Tap the Share icon at the bottom (a square with an up-arrow).
  3. Scroll down in the share sheet and tap Add to Home Screen.
  4. Tap Add in the top-right.
  5. Open Cove from your home screen. It runs full-screen with its own icon.

On Android (Chrome)

  1. Open app.cove.oap.dev in Chrome.
  2. Tap the menu (top-right).
  3. Tap Install app (or on some Chrome versions, Add to Home screen).
  4. Confirm on the prompt.
  5. Open Cove from your home screen or app drawer.

On a laptop (Chrome or Safari)

  1. Open app.cove.oap.dev.
  2. Chrome: click the install icon in the address bar (a small screen with an arrow), then Install. Safari 17+ on Mac: File menu → Add to Dock….
  3. Cove appears in your dock/taskbar. Launch from there.
Why a web app and not a native one? Native App Store apps take weeks of review for every change, and updates on your phone only arrive when you remember to open the App Store. Cove's web app updates the moment your keymaster ships a fix, and installs the same to a home-screen icon. You lose nothing except an App Store loading bar.

2Use your invite code.

Your keymaster texted or handed you an invite code — a string of letters and numbers, single-use, expires within a day or two. When you first open Cove, you'll see a Get started button.

  1. Tap Get started.
  2. Enter your name (how the group will see you), the hub URL your keymaster gave you (e.g. https://lwccoa-hub.oap.dev), and the invite code.
  3. Pick how you'll unlock Cove on this device:
    • Passkey (recommended) — your device's Face ID / Touch ID / fingerprint. One tap to sign in later. Syncs across your Apple or Google devices.
    • Passphrase — type it yourself. Works everywhere, including non-biometric devices. Pick something you'll remember; there's no reset.
  4. Tap Get started. Cove generates a keypair on your device and asks your keymaster to attest you.
  5. You'll see a waiting screen with a colorful fingerprint. Your keymaster sees your request in their admin panel. When they approve you, this screen flips into the app automatically.
The fingerprint is your identity. The colorful strip on the waiting screen is a visual summary of your public key. If a keymaster ever asks you to confirm your identity out-of-band, that fingerprint is what to check. Nobody else has the same one.

3Inbox and threads.

Cove has two main ways to look at your group's messages. Understanding both makes the app feel obvious instead of overwhelming.

Inbox — "what's new"

The Inbox is Cove's landing screen. It lists every thread with the most recent activity first, showing you the latest message, who wrote it, and how many are unread. Think of it like an email inbox: you scan for what needs your attention, tap into the specific thread, catch up.

Unread threads bubble to the top with a small dot. Once you read them, they settle back into chronological order.

Threads — "the whole conversation"

A thread is one conversation about one topic. When you tap a thread from the Inbox (or from the sidebar), you see every message in it in order, from first to most recent. Long threads scroll like any messaging app.

Threads have names. The sidebar shows every thread the group has going, so you can jump between them without going back to the Inbox.

The sidebar on the left is your permanent nav: Inbox at the top, then a list of Threads (scrollable if there are many), then hubs at the bottom. On phones and narrow windows, the sidebar collapses; a hamburger button at the top-left reopens it.

4Reading and posting.

Inside a thread, type your message in the compose box at the bottom and hit send. Attachments (photos, PDFs, spreadsheets) go through the paperclip icon — they're stored on your group's hub, not in a third-party cloud.

Cards view vs. chat view

Cove offers two ways to render a thread's messages:

Toggle via the icon at the top of the thread pane. Your choice is per-device and persists between sessions.

5Starting a thread.

You can start a thread anytime by clicking the + button next to the Threads section header in the sidebar, or the + New thread button in the Inbox.

Naming conventions

Public vs. private threads

When you create a thread, you'll pick an audience:

6Ephemeral vs. permanent threads.

Cove treats "how long does this need to live?" as a first-class decision. Some conversations should be on the record forever; others shouldn't outlive their purpose. Every thread is one of two kinds:

Permanent (default)

Once posted, entries in a permanent thread are there forever — verifiable line by line, signed by the person who wrote them, part of the group's tamper-evident log. Governance decisions, meeting minutes, financial discussions, anything you might need to reference three years from now.

What gets kept: everything. Every message, every attachment, every read receipt.

Ephemeral

Ephemeral threads carry a self-declared expiration. When their time's up, the hub seals the thread and its contents disappear. A signed record proves what the thread was about and when it existed — but the messages themselves are gone.

Good for: a beach cleanup coordinating chat, the recital, a spring social, back-and-forth about a one-time event. Anything where "the conversation was useful in the moment but shouldn't clutter the archive."

What gets kept: the fact the thread existed, its name, when it was created, when it expired, and a signed proof of what was inside so nobody can later dispute whether it happened. The messages themselves are gone.

You pick permanent or ephemeral when you create the thread. Ephemeral threads show an hourglass icon and a countdown in the sidebar.

7Using Cove on more than one device.

Once you're signed in on your first device, adding a second one is a two-minute round-trip. You never generate new keys; the same identity travels with you.

  1. Install Cove on the second device (Step 1 above).
  2. On the launch screen, scroll to "Signing in from a new device? Use your Cove vault".
  3. Enter your hub URL and your public key (visible in the sidebar footer on your first device; tap to copy).
  4. Unlock with your Passkey (one tap) or passphrase.
  5. You're in. Same identity, same threads, same everything.
Cross-ecosystem is fine. Passkeys don't sync between Apple's iCloud Keychain and Google's Password Manager — that's an industry limitation, not Cove's. If your phone is Android and your laptop is Mac, use a Passkey on each (they'll each unlock the same identity) plus a passphrase as a shared fallback that works on any device.

8Being in more than one group.

Some people are in multiple Cove groups — an HOA, a church council, a small nonprofit. You can add all of them to one Cove client and switch between them from the sidebar.

Each group's keymaster gives you a separate invite code. The keymaster of the second group attests the same identity you already have, so no new keys, no new sign-in ceremony. From the Cove sidebar, tap + Add another hub, enter the new URL, and the app authenticates you against it.

Once added, hubs appear as rows near the bottom of the sidebar. Tap one to switch. Threads, Inbox, notifications — everything flips to that group's view.

That's the whole thing.

Cove is small on purpose. There's no feed algorithm, no ad targeting, no plugin marketplace. Just your group, having its conversations, on your group's server, forever.

If you get stuck, the person who invited you can help — they're either your keymaster or one keystroke away from them. And if you're curious about the technical details, the specifications page lays out the whole protocol.