Nostr clients should add a link to the NIPs that they implement, maybe also a link to the apps that are interoperable with it. More important for special purpose clients compared to genral ones
Thread
Login to reply
Replies ()
what is the benefit?
I'll give you a few examples.
I have been using Zapstore for a while and wanted to find the NIP that it uses, because I was thinking about a App Store for Linux using AppImage, I couldn't find it because the NIP is not merged and I didn't know what to search for in the PRs either. I had to manually scroll through the PRs to find it
I installed Keychat, 0xChat, XChat and Whitenoise. These use different standards for messages, and it was very difficult for me to figure out which app is interoperable with what
zapstore
Pull Request 
no they are not interoperable
NIPs - Zapstore Documentation
Zapstore documentation
GitHub
Software applications events by franzaps · Pull Request #1336 · nostr-protocol/nips
Rendered
This event represents an application as used in Zapstore. It is actively being used in a production setting for many months already.
This ...
For the interoperability part, 
was created.
There's a nip for relays to show their supported nips but clients usually don't. Also nips are meant to be created after they are implemented in a client, so a client doing something new is kind of the point. So if you want to collaborate with @franzap in building a compatible store, talk to him. He's always very open to suggestions and cooperation. And when you with your client validate his approach and implement it, too, the nip will get merged.
GitHub
nostrability/nostrability
Left curve nostr broken stuff and interoperability tracker + json schema validation - nostrability/nostrability