We tried this with nsec.app, and went back to one req per confirm screen, because then there is more space for showing details of what the app is doing - raw json, raw encrypted payload, users added to contact list etc. Just saying, if that adds something to your design decisions. Maybe also check Amber, they are quite ahead of the curve here, i.e. support approval by nip, not just kind. 

 we will likely have a drill-down option, but I think we can fit a high level overview in a half-popup on the page 

 raw json is for nerds, most people won't know what they are looking at. I'm going to try to have ways to describe what is happening without having to show any json. of course there will be a way to view the json, but in reality most people won't be looking at that. 

 Fact 😴 

 100% that's the way, but json is still necessary. This and all kinds of things the app might be doing is not trivial to design for, at least for me. 

 this is why I put it as challenge to rob xD 

 good point on the nip/kind distinction though. I think by nip makes sense. 

 I think manually defining categories may be better than NIPs because some NIPs you may want to only partially authorize for 

 forcing raw json on a man is akin to demanding a duel 🤺