Nostr
Vitor Pamplona
Does Size Matter? How big is too big?

In the early days of Nostr, developers often competed to see who could implement the most NIPs. Although all were optional (except NIP-01), it became a point of pride and vital for the ecosystem's growth. Back then, there were only a few dozen relatively simple NIPs to implement. Fast forward to today, with nearly 100 NIPs, maintaining and implementing everything has become nearly impossible. Yet, the drive among developers to "code all things Nostr" remains as strong as ever.

fiatjaf raised the point that everyone, even I, agrees:

nostr:nevent1qqsqqqp2zrs7836tyjlsfe7aj9c4d97zrxxqyayagkdwlcur96t4laspzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3q80cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsxpqqqqqqzgcrrrp

But how big is too big? How can we better understand the range of options available for devs out there?

I went out for a hunt in my own brain to figure out how to clarify the situation. I came up with the following 4 categories for Nostr Clients:

  • Super Clients: These apps merge vastly different domains into a single application, offering basic support for reading, writing, configuration, and data management for each use case within each domains. An example would be an app that combines a Marketplace and Live Streams under one roof.

  • Clients: These apps provide comprehensive support for a single domain, handling all its use cases in a single home. They manage the complete set of reading, writing, configuration, and long-term data management within that domain. An example is a marketplace app that helps users manage product catalogs, process orders, collect payments, and handle fulfillment and reports.

  • Mini Clients: These apps focus on read and write functionality for a single use case, including configuration management and any actions related to that specific task. For example, a fulfillment app that helps users view orders placed from another client to then pack and ship them.

  • Micro Clients: These apps have a single interface and perform one specific action. Viewing and creating a record is handled by separate micro apps. An example is an app that simply scans an order's QR code and marks it as shipped.

Based on my made-up categories described at the end, this is how I would split our most known apps.

Super Clients

Clients

Mini Clients

Micro Clients

Super apps will try to do everything, but can't really do most things super well. Regular-sized Clients will try to manage most of a given domain but are likely to centralize users on themselves, an unwanted effect inside of Nostr. If we want Nostr to grow in a decentralized fashion, we have to start betting on and using more Mini and Micro clients.

Related Articles

But blogging on a phone sucks... :)…...

Habla.news…...

We are live!…...

@hodlbod is on fire. 👀 Here's a discord/slack Nostr client:…...

Based on my made-up categories, this is how I would split our most known apps. Also... Microapps are clearly not getting the marketing they deserve Super Clients amethyst.social nostrudel.ninja coracle.social Clients habla.news damus.io primal.net 0xchat.com snort.social yakihonne.com iris.to satellite....

Are these definitions clear enough to non-devs out there? Do they make sense? Super Clients merge vastly different domains into just one application, generally providing some basic support for read, write, configuration and data management of each use case inside of each domain. Example: when Marketplace and Live Streams…...