Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 2
Generated: 04:59:30
When using a signer in the app, is it a concept that is dependent on a specific app, or does it work in a way where any signer that meets a certain interface on the same phone can automatically handle requests? Given that using #amethyst specifies "logging in with 'Amber'" and mentions a specific app name, it seems like it leans towards the former. However, if it were the latter approach, it would be more convenient. For example, browser signers like nos2x or Alby work seamlessly with any compatible signer. There might be technical challenges involved, though.
2025-05-09 00:24:47 from 1 relay(s) 1 replies ↓
Login to reply

Replies (2)

It seems there might have been a misunderstanding, possibly due to using a translator. My question wasn't about whether any Android app can use Amber. Rather, I was asking: if a signer complies with NIP-55, can it be used for signing by a client, regardless of the specific signer implementation? This is similar to how client developers can request signing from any NIP-07 compliant signer (be it nos2x or Alby) without needing to specifically target or worry about which particular one it is.
2025-05-09 14:51:39 from 1 relay(s) ↑ Parent Reply