Signers can be made easier to understand IMO. Instead of saying "com.vitorpamplona.amethyst" wants you to sign an event: Kind 1, we can say "Amethyst wants to sign a new note containing "this is my new note"

People won't have a clue what a Kind 1 is, or any "kind". The word itself is confusing in any context of app usage. The same for long strings of techno terms. If we see "Amethyst" in the string, we should be able to deduce this is from Amethyst. I don't know if all of those follow the same format (probably not), but at least for the known major clients we should be able to extract client name, no?

This makes for a much more user friendly message.

The same may go for "sign". Keys signing doesn't sound intuitive. But approving something does. "Amethyst needs your approval to post new notes" (Accept / Deny). This makes it a lot more obvious what the client wants. Also, when you go back to check your permission settings, it's a lot easier to see what the app is able to do vs. trying to figure out what each kind means.

But, even broader than that, it may help to set an approval policy (signing policy) which covers basic events such as new notes, reading npubs, reactions, dms, etc... People shouldn't have to mess with all of this all the time UNLESS they want to. In which case they can select another approval policy and deal with all of that stuff as they please.

my 2 sats.