As you probably noticed in previous pages, various settings can be configured contextually throughout the app experience (like hiding and unhiding the balance). All these options, and a few extra ones, are bundled in the settings area.
While not the most frequently visited part of an application, it fills an important functional role by giving users precise control over their experience.
This sub-section includes various non-essential settings that are not covered in the other categories and let users adjust the application to their context and personal preferences.
Paying fees for transactions is unavoidable and typically not something users enjoy. Being transparent and communicating them clearly in context (e.g. when reviewing a payment before sending it) is crucial. Since contextual information is selective, this fee screen in settings is needed to provide a concise summary of all the types of fees that may be charged.
During regular use, only lightning network fees will apply to transactions in this wallet. An additional fee may be charged for opening new channels to increase liquidity.
When users send to an on-chain address, a swap fee applies. This fee also applies if the user receives to an on-chain (swap) address. This may cause confusion, as typically, the sender is responsible for paying fees.
Privacy settings are straightforward and focused on whether balances are visible or hidden. While there are some best practices for users, much of the responsibility to ensure good privacy rests in the hands of the developers.
Security is all about preventing unwanted access to the application. Basic access options (PIN, FaceID) are configured during first use, and users receive regular reminders to review them. Wallet limits are an additional option, only available in settings, to block potentially unwanted high-value payments.
Wallet backup #
First use also guides users towards appropriate backup options, and users may never need to access this screen. A unique piece of information here is when the last cloud backup was performed. This can give users peace of mind that their information is securely being backed up.
Most users will not need or want to change network settings, but it is important to offer these features for those who do. While it may be personal preference for some, it may be a privacy or security matter for others to connect through services they personally maintain or trust. Interoperability is a core design principle and also makes the application more versatile.
Help & support #
Open-source projects do not have large support teams but instead often rely on their communities and forum discussion to allow users to help each other. Contributors are also part of this activity but usually cannot dedicate time to address all support needs. Therefore it is important to provide several different methods to get help. It distributes the burden of support across documentation, community, and contributors.
Next, let’s dive into the savings wallet reference design.