right move imo, your daily driver should allow you to launch embedded apps and act as a signer/wallet, that's the killer UX (see @Keychat). installing 3 apps to use the nostr ngmi, i ain't listening to the nerds that think that's a good idea.
jb55's avatar jb55
I’ve never seen so many angry people just for suggesting not having amber support. Damus Android’s chrome is being designed as the signer, and our hosted micro apps will communicate with the chrome for signing. This is no different than a browser with a signing extension, except the signer is embedded in damus in an isolated fashion. We’re designing damus so that it can securely host multiple micro-apps for multiple platforms, and it will not depend on any external apps for its core function.
View quoted note →

Replies (12)

Interesting. I don’t understand the technicals, but I’m glad I read this perspective. Embedded apps would be nostr apps that work within many supporting clients? Or built for Damus?
I get the idea, and love the notedeck approach to hosting nostr micro-apps. But isn't it technically possible to proxy the signEvent() call to Amber if that one is already installed? Looking at the comments, Damus's success on android seems to depend on this piece of interoperability.
Niel Liesmons's avatar
Niel Liesmons 4 months ago
1) Daily driver should :110percent: have signer + wallet built in 2) There's very little reason for not giving the option to use external signers and wallets 3) Current Damus beta apk is waaaay to beta (in its performance, UI randomness and geeky UX) to be such a daily driver
jb55's avatar
jb55 _@jb55.com 4 months ago
We are nothing like keychat architecturally. We are building a nostr browser, not a web browser app manager.
jb55's avatar
jb55 _@jb55.com 4 months ago
damus android isn't just an android app, it needs this signing functionality on all platforms, and it needs features amber doesn't have