It should be easier for the end-user to load the connection (and authentication) details needed to communicate with an instance of lnd. There is a project by the maintainers of Zap Wallet called lndconnect which creates an encoded URI string that can be further encoded as a QR code and scanned by Zap Wallet. For details of the URI encoding:
I've already started working on a script that combines a few common unix command-line tools to do this (output as text or QR code). See this work-in-progress branch
It should be easier for the end-user to load the connection (and authentication) details needed to communicate with an instance of lnd. There is a project by the maintainers of Zap Wallet called lndconnect which creates an encoded URI string that can be further encoded as a QR code and scanned by Zap Wallet. For details of the URI encoding:
I've already started working on a script that combines a few common unix command-line tools to do this (output as text or QR code). See this work-in-progress branch