Oddbean new post about | logout
 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 are placed into the same app.

- Clients provide complete support for a single domain and its many use cases, including read, write, configuration and long-term data management. Examples: A marketplace app that help users manage product catalogs, manage orders, collect payment, manage fulfillment and tax reports.

- Mini Clients provide read and write support for single use cases, including configuration management and all actions related to the use case. Example: A fulfillment app that helps users view orders placed from another Client, pack and ship them.

- Micro Clients are single interface apps that execute only one action. Viewing some record and creating the same record are separate micro apps. Example: An app that simply scans the QR code of an order and marks as shipped. 
 Non-devs don't use the word "Client" sir 
 I always fuck things up....  
 They’re “Apps”. Normies think “Clients” are patients. 
 Reminds me of the fight for what name to use: Nostr Client, Nostr App or Nostr Browser. 
 This. Always got to think lowest common denominator for users. 
 💯 
 I think it’s clear enough to have a basic understanding. However, I think nothing would be more illustrative than seeing examples in action. 
 Seems like these are most useful **for** devs.

Normies will most likely only really see and feel two categories: 
1. Apps
2. Widgets  👉  Things that are functional **inside** Apps and are clearly non-native 
 Who is the target audience? Someone familiar with nostr already or someone new to it? If the target audience audience is new people, I might not say domains, just because they'll confuse that with other web stuff. I might use something like aspects, components, features, etc. 
 Also, by these definitions would Amethyst be a super client and Primal be a client, where Primal, from what I can tell, only offers a social media feed component, where Amethyst has a marketplace, streams, etc.? 

Amethyst also has the ability to do groups. A lot of other clients/super clients do not. Is that a separate thing that would bump a client into super client status? 
 yep 
 I think these make sense to me. I like that the terminology is out there. 
 It makes sense. 

I agree with the "app" sentiment but not "widget". I think of widgets as something that takes one function from an app & makes it easily accessible. Microapps do their own thing, but usually add something with some other app. 

 
 "microapp" like Orbot? that's a service, really... services (not system built-in) usually have an icon in the system tray/taskbar (top right of a mobile UI usually)

i don't think any distinction is really understood or made whether an app just shows an interface or even just an image on an independent screen with nothing upwards to anything more than that 
 Just sharing some non-dev perspective. 
 Nicely done. Since all of these things are clients, perhaps "clients" should not be one of the types of clients; I suggest renaming the client type "clients" to "complete client" is something like that. 
 Thanks for grouping, that really helps to navigate through nostr apps and space.

As a feedback for you:
Read, write, configuration, data management, domains are quite technical terms in my opinion. But don't have other suggestion at the moment.