You can do this already on Android to some extent. I zap in Primal from my node. The big honking ⚡ icon in the middle of the wallet is worthless though, since I cant utilize it.

That said, being able to use the wallet you are already using in another application such as Olas for example is powerful for new users. If I onboard a musician to Primal and Fountain, they have to have two complexly separate walkers. Now imagine them having just one. It's much less confusing.

Reply to this note

Please Login to reply.

Discussion

Yea I'm talking the primal wallet UI (the big ⚡ icon). I want to use that UI but have it pointed at my alby-hub.

But the more I think about it these things should really be delivered together.

i.e. the strike-backed wallet is given NWC AND the UI becomes a NWC agnostic frontend. That way the typical onboarding flow would be the same inside of primal, but improved for other clients (as you mentioned). And then they would also only have to maintain the UI as a NWC frontend.

default) Primal UI -NWC-> strike-backed primal wallet

optional) Primal UI -NWC-> any NWC enabled wallet

Yes. I would like this very much and I think it would be a popular change.

Yes, this would be ideal. Complete interoperability in both directions via the NWC standard. I am pretty sure we can get there; one step at a time.