Nostr app archive

Damus

Damus in the Nostr ecosystem: iOS Nostr client. This Crays archive page explains the public role, where it fits and why it matters.

Damus made Nostr visible for many iOS users by turning keys, relays, notes and zaps into a mobile social experience.

What it is

Damus is included because it represents an important category in the Nostr ecosystem: iOS Nostr client. Some readers will meet Nostr first through this kind of product, not through the protocol documents.

  • Category. iOS Nostr client
  • Protocol fit. It uses Nostr identity, events, relays, signers, zaps, media references or developer abstractions depending on the product.
  • Reader value. It helps explain how Nostr moves from an abstract protocol into usable interfaces.

Why it matters

Damus made Nostr visible for many iOS users by turning keys, relays, notes and zaps into a mobile social experience. The product also shows that Nostr can support specialized interfaces rather than one universal app.

Crays relevance

Crays should learn from this product category without copying it blindly. The Crays surface needs profiles, paid content, status, fans, venues, award voting, Lightning flows and real-world hospitality context.

Back to the Crays Nostr page