@rabble @Matt Lorentz @jb55 @Fabian @Pavle @miljan @PABLOF7z ^ Let me know what you think of this proof of concept UX screencap for a native iOS Nostr signer and if you’d be open to adding it in your clients once I get it production ready. I think this is the best possible UX given that the Nostr client stays in the foreground.
The alternatives were:
1. Ask the user to install a shortcut (non-intuitive) + invoke the shortcut (Action Button on iPhone 15+, accessibility back tap < iPhone 15, non-intuitive) + clipboard hacks (inefficient, error prone).
2. Use nostrsigner:// deeplinks to switch to the signer (forces app switching twice).
Login to reply
Replies (3)
Doing this for every action such as liking things is going to be a ux nightmare
Is it going to have to pop up the sheet for every event that needs signing?
I’m not opposed to accepting a PR to support it but the only people asking for this are Nostr devs who don’t want to trust the code of other Nostr devs. I don’t think anyone who isn’t already self-custodying their crypto will use it.
We’ve never had a user come to us and say they won’t use @npub1pu3v...tfch because we store the keys in Apple’s keychain.
Would it be nice to have an option for an Amber like solution for iOS, sure. But I doubt it’ll get much use. Kind of like how it’s great Signal is open source, but there isn’t much anyone can or does do with the source.
This is probably the best local UX given iOS limitations, still horrible (not your fault), but I’m open to adding it in Nostur