i would agree here. this is a feature that i want too, and nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsqzp4sl80zm866yqrha4esknfwp0j4lxfrt29pkrh5nnnj2rgx6dm622d3ttr has stated that it will be on the roadmap after 2.0 launches. i am anxious for both features to come to Primal. Amber support is for the more technical and tech savvy users and your users that push the platform forward and Olas image support would be for everyone.
I know it's the rage, but please can we have external signer support for Android before that?
Sure, it's not an option on iOS and we already have NIP-07 on the web client, but there really isn't an excuse on Android, especially if a one-man-show like nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has already supported NIP-46 for Olas. (It mostly works.)
Discussion
For sure. I would like to see it change so that Amber isn't thought of as just for more technical and tech savvy users, though. After initial setup, which could be streamlined a bit, using Amber is a breeze with NIP-55 clients. Clients that allow setting up a NIP-46 connection by just scanning a QR code are also narrowing that gap. It's just the creation and copy/pasting of bunker tokens that is foreign UX for most folks. Arguably not much more foreign than pasting in an nsec, though.
I 100% agree.