Damus vs Primal: which Nostr client should you use?

Damus and Primal are the two most-installed Nostr clients on iOS and Android. If you are comparing the two and wondering which to install first, this article is the side-by-side.

We will skip the superlatives. Both are actively maintained, both work well in 2026, and the decision is about which tradeoffs match how you want to use Nostr. We lay them out.

The short answer. Damus is a neutral Nostr reader. Primal is an opinionated Nostr product. Damus gives you raw relays and chronological feeds; Primal gives you curated discovery and a built-in wallet. Pick Damus if you want full control; pick Primal if you want defaults that feel Twitter-like.

When you are ready, grab your @nostr.blog address →

What each one actually is

Damus is a Swift-first Nostr client built by developer Bill Casarin (jb55). It started as an iOS-only app in late 2022 and expanded to macOS. The stance is minimalist: show posts from people you follow, let you send zaps, stay out of the way. The default feed is strict chronological from your follows, with no trending or suggestions injected.

Primal is a Serbian company building a Nostr product: apps on iOS, Android, and web, a proprietary caching infrastructure, an in-app wallet, trending and explore feeds, algorithmic "For You" options. Primal is more of a platform than a client in the traditional sense; it has opinions about what good Nostr feels like and enforces them.

The difference is philosophical, not technical. Both use the same Nostr protocol. Both talk to the same relays. Both render the same signed events. Where they part ways is in what they layer on top.

Signup and onboarding

Damus. Install from the App Store, open, tap through the key-generation screens, land on an empty timeline. The app shows a starter list of accounts to follow on first launch. Signup takes about three minutes; the empty timeline takes another ten to fill with follows. Damus assumes you know what a Nostr account is.

Primal. Install, open, get walked through a guided signup. Primal generates keys, offers to save them, gives you a suggested list of high-quality accounts to follow, and drops you into a populated feed in about two minutes. The UX feels like a standard app signup, not a cryptographic one.

For total new users, Primal's onboarding is friendlier. For users who already understand Nostr, Damus's shorter path might feel less paternalistic.

Feed experience

Damus. Pure chronological feed of people you follow, ordered newest first. No "For You," no trending, no suggested posts. What you see is what your follows posted, in the order they posted. If your follows are quiet, your feed is quiet.

Primal. Default feed is still reverse-chronological from your follows, but the app surrounds it with three other feeds: Trending (what is popular across Primal's caching index), Explore (curated content), and a "For You" algorithmic option. Users can switch between them.

Damus's approach respects your curation work; Primal's approach fills in for curation when it is thin. Both are valid; the question is whether you want the app to recommend things you did not ask for.

Zap experience

Damus. Damus Wallet launched in 2024 as an integrated Lightning wallet. One-tap zapping works with either Damus Wallet or an external wallet via NWC. UX is solid; the wallet UI is minimal but functional.

Primal. Primal Wallet has been in the product longer and shows it. One-tap zapping, balance visible everywhere, sending sats to any Lightning address in or out of Nostr, buy-sats integrated for supported regions. Noticeably more polished than Damus Wallet in 2026.

If zapping is a big part of your use, Primal's wallet is easier. If you already use a different Lightning wallet, both clients let you connect it via NWC and the difference shrinks.

Direct messages

Damus. Supports NIP-04 direct messages (the older, less private standard) and NIP-44/NIP-17 gift-wrapped DMs (the newer standard that hides metadata better). Interface is compact; the focus is function.

Primal. Same support matrix. UI is more chat-app-shaped, feels closer to iMessage or Telegram.

Feature parity on protocol support; different UX taste.

Performance

Damus. Talks to relays directly. Feed load is live and current but has a "cold start" beat while the relays return history. On subsequent opens, the cached events appear instantly and new ones trickle in.

Primal. Runs a caching layer between the user and the relays. Feed load feels instant because the cache responds immediately; new events propagate from relays a moment later. The trade is that you are trusting Primal's cache to reflect the full network.

For most users, the performance difference is imperceptible. For users on slow connections or with many follows, Primal's cache is a meaningful speed advantage.

Privacy envelope

Damus. Talks to public relays you configure. No single company sees your whole activity. The attack surface is the set of relays you use, and you choose them.

Primal. Primal's caching infrastructure sits between you and the relays in the default configuration. Primal sees your subscription patterns, your relay choices, and your session behavior. This does not break Nostr's cryptographic guarantees, but it adds one company to the list of parties who can see your activity.

For users who care strongly about minimizing their single-vendor exposure, Damus has a narrower surface. For users who trust Primal to handle the data well, the cache is a net win for speed.

What each does poorly

Honest weak spots.

Damus has historically been slower to ship new features than Primal. The release cadence is slower, the UI makes some power features hard to find, and the iOS-first focus means Android users have been an afterthought. Damus's Android app exists but is less mature.

Primal is a company with product opinions, which some users perceive as centralization creeping into a protocol that is supposed to avoid it. The cache is optional in theory but default in practice, and opting out feels like fighting the app. Users who specifically chose Nostr to escape platform-like dynamics find Primal's model uncomfortable.

Neither problem is a dealbreaker. They are trade-offs with different flavors.

Which to pick, explicitly

Use Damus if:

• You are on iOS (it is more mature there than on Android)
• You want the simplest possible chronological feed
• You prefer minimizing which companies see your Nostr activity
• You like the Bitcoin-developer tone that comes through in the product

Use Primal if:

• You want the polished, Twitter-adjacent UX
• You want a built-in wallet with strong integration
• You like trending and discovery features
• You are happy with a slightly centralized service inside a decentralized protocol

Consider something else if:

• You want the smoothest cross-platform web experience (try nostr.blog, Coracle, or Primal's web app)
• You want Android with maximum feature depth (Amethyst exceeds both Damus and Primal on Android)
• You want to write long-form articles (Habla or Yakihonne)

Most users end up installing both and picking the one whose UI they prefer after a week of use. This is a free decision because switching costs nothing; your identity works in both apps simultaneously.

Where nostr.blog fits

Our own client is web-first and guided. We targeted the same user Primal targets (a Twitter refugee who wants a low-friction first hour) but on the web and with even more bundled onto one page. Identity, wallet, client, NIP-05 name, all set up in the two-minute signup.

We built it because the native-mobile-first clients (Damus, Primal, Amethyst) assume you will install an app. A meaningful fraction of new Nostr users bounce at the install step. The web path avoids that.

If you want to try Nostr without installing anything, nostr.blog is the option. If you prefer a native mobile app, Damus and Primal are the ones you should compare.