Micro (or Nano) Client: supports only one NIP. Or, if one is really not enough, only the essential ones to make it useful.
Mini Client: supports some NIPs, related to each other around a specific concept
Client: supports even more NIPS, related to each other around one or more concepts. 

 Here's where I stand: 

- Super Clients merge vastly different use cases into just one app.

- Clients provide complete support for the many actions in a given use case, including read, write, configuration and long-term data management.

- Mini apps provide read and write support for single actions, including configuration management related to the action. 

- Micro apps are single interface apps that execute only one action. Viewing some record and creating the same record are separate micro apps.  

 I prefer the super apps. But if they're going to do "all the things" each feature should be baked in as well as each other. No skimping on quality for the sake of ticking off a box. 

 Client: Functional for continuous use, such as a complete social network or search engine, usually concentrating several functionalities

Mini Client: Functional only for some exclusive activities that require a certain amount of time to use, but that are not used frequently

Micro-client: Used for only some simple tasks, but with almost or completely no frequent use, such as: Only to create a community, download emojis, check relays...

Nano client: Does not have a front-end, it only serves to facilitate processes for each user who wants to run the code 

 Where do pollerama.fun and formstr.app fall on this terminology 🤣 

 ACHEI!!!! 

 Maybe by the amount of kinds it interacts with.  

 client: full featured phone or desktop application 

miniclient: purpose specific. used a couple, or one nips

microclient: for IOT devices. single kind, for sending and receiving data from a device 

 What about #notanostrclient?