Sounds way too complicated, why nost just use nostr:
This way I could choose which nostr app to open with the same way I can choose the broelwser for http: / https: or lightning wallets for lightning: .
The one click open for arbitrary kind should be based on [nip89](https://nostr-nips.com/nip-89) .
If clients start supporting that instead of hardcoding links (of which I'm guilty too, as of yet) then you can look up the the handler info based on app recommendations of the logged in user, then redirect him to the handler he prefers.
Alternatively, show recommendations for the user based on some web of trust pubkeys, ones that have a preferred handler for that kind. That would be a two-click jump ofc.
Sounds way too complicated, why nost just use nostr:
This way I could choose which nostr app to open with the same way I can choose the broelwser for http: / https: or lightning wallets for lightning: .
What if you don't have that handler app installed?
Point is, Nostr transcends the confines of the OS with nip89 and allows for UX yet unavailable with intents and other techniques