We are trying to see if we can do a Nostr invitation deep link that installs zap.store first and then opens the invitation data with a picture of your friend and a create a new Nostr user screen. When the user inserts his/her name to create a new account, zap.store installs a My Nostr Profile app (a signer, like Amber) and, in the background, asks the signer to create a new user. With the new user created, zap.store follows the friend recommendation to install a client.. say Amethyst. After installed, zap.store sends the users to an Amethyst that was already logged into from Amber straight into the user profile of the friend.

Flow is:

- New user receives a link (or scans a QR Code)

- Zap.store is installed, opens to a new user screen.

- User inserts the name, Amber is installed.

- Zap.store points to Amethyst to install.

- Amethyst is installed, logged in and ready to be used.

Lots of things happening on the backgrond to simplify things. The new user gets a new key, a signer and an app installed and ready to go.

Reply to this note

Please Login to reply.

Discussion

Looking forward to this experiment

I'm going to have a hard time rewiring zap.store -> Zapstore...

And the .store domain is expiring anytime now😐

This seems like a long way (three app install) workaround to the manufactured problem of :

“Nobody wants a dedicated onboarding client … onboarding should happen from within the social client”

I happen to think there is a LOT of value in just making a GREAT onboarding client that:

- introduces a user to the world of Nostr

- creates a profile and key pair with minimal friction and zero KYC.

- helps new users to discover all their friends friends who are using Nostr

- helps with discovery (and setup) of clients and relays that are used within their network of friends.

- continues on as an account hub, key manager, nostr activity monitor, and app discovery client for the new user.

- rewards existing users for onboarding (and retaining) their friends on Nostr.

This is what I’m (still) building … and happy to collaborate.

https://nostrmeet.me

https://github.com/nostrmeetme/nostrmeetme

https://geyser.fund/project/nostrmeetme

A great onboarding client could work, but the issue is that it needs access to an App store to install everything the user needs in order to see the different things different friends are doing.

If I have friends using Zap.Stream, the onboarding must suggest a client that can see streams. If I have friends using NIP-17 DMs, the onboarding clients MUST suggest apps that support that specific kind, install and make them ready to use without any additional setup in each app. There are 100s of new kinds now and figuring out what I need to install to see my friends is the most important task of the onboarding tool. That's why a Store app can be a good place for this.

Onboarding people to Nostr is basically onboarding them to a new app ecosystem.

At some point in there you need to at least suggest they backup their nsec.

Yes, 3 months later if they are still here. No one gives two shits about a recently created nsec.

Ah, true enough. Maybe after their nth post in a client, or first post after x days?

I know you are Dr. Amethyst, but could Zap.store also point to another/other Nostr app(s) to install as well? In the interest of decentralization and choice?

Yep, it's the recommendation of whoever is inviting the new user.

if they sign up that way, what's the easist transition to desktop/web apps?

👀

🔥🚀

Personell Web of trust models, built on sensorship resist networks, fueled by decentralized money..

Solo Bullish on the future!!

Installing 3 apps to post 1 cat picture will seem like malware shit to the average user if it happens automatically