A Nostr client is the app people touch. The client does not own the protocol. It reads and writes signed events through relays and shapes the user experience on top.
Client categories
The Nostr client universe is broad because the protocol can carry many kinds of events. Some clients feel like social feeds. Others are long-form publishing tools, media apps, chat surfaces, developer dashboards, marketplaces, search tools or power-user consoles.
- Mobile social. Damus, Amethyst, Primal, Nos, Nostur and related apps introduce users to daily social posting.
- Web social. Coracle, Snort, Iris, Nostrudel and Primal web show how the same identity can work in browsers.
- Publishing. Habla and YakiHonne point toward long-form and creator workflows.
- Power tools. Nostrudel, nak and relay tooling serve developers and advanced operators.
Choosing a first client
A first client should make key safety and posting simple. A second client should demonstrate portability. If a user signs into another client and still sees follows, posts or profile context, the Nostr idea becomes tangible.
What clients compete on
Clients compete on onboarding, relay strategy, search, moderation, feed design, wallet integration, notifications, media support, communities, long-form publishing and signer integration. They should not compete by trapping the identity.
Crays client logic
Crays.net should behave like a purpose-built Nostr client for the Crays ecosystem: profile, content, access, fan demand, status, award voting and venue routes. It can be opinionated without pretending to own the whole graph.