Nsec.app on iOS needs these settings for now, until the web push technology graduates from 'experimental'. Not sure if 'add to homescreen' requirement stays or not. On other platforms it works out of the box.

Nostr-login is nip46 client, noauth/nsec.app is nip46 server (running in your browser) - there isn't much more than that.

The smoothest mobile-first signup experience is when you just generate nsec in your client and eventually when user is ready start explaining to them how to get their nsec 'reused' in other apps. If you need to immediately give them an option to sign into other apps then you could host your own nsecbunker instance and generate nsecs inside it and store on your server - it would be as smooth, but custodial. The next option is nsec.app - non-custodial, but more friction on some platforms/browsers like iOS or Brave.  

 That does help. How does one “port” existing keys into nsec.app? 

 On use.nsec.app click Get started (or Add account) and then Import keys. 

 Ok. I like your recommended onboard flow. So I’d just generate nsecs for new accounts, pass them “raw” to the NDKSigner, and encrypt/decrypt them with a password for local storage? (In case the user closes the browser) Wd this be best practice? 

 Right, but also I am not sure adding a password is that necessary for starters. 

 Hmm … yea. I can see that.