Infos and settings

Estimated reading time: 3 minutes

Sections in this page

• Informations
• Settings
• Case study: blind signing for the Ethereum app

Provide helpful information to your users in the informations section. And for advanced use cases, provide app settings that unlock additional functionality or change the default behavior of your app.

Informations

Your app must provide at least its version number and the developer name or organization. These informations are part of the app’s resources and will be used automatically to build a default version of the app’s infos.

More informations can be provided with the same format: rows of key-value pairs.

Settings

  Important
App settings are reset to their default values each time the app is updated or reinstalled. This is a consequence of the architecture of Ledger’s secure OS.

Your app can have settings that unlock new capabilities or alter its behavior. As soon as your app contains a setting, the icon on the app’s home must change to a setting wheel, instead of the informational “i”.

Here’s the example of the Ethereum app, developed by Ledger. It provides three user-adjustable settings on the first page. App informations move to page 2. Note that navigation arrows appear as soon as there are two pages.

The settings can use the following elements for interaction:

• toggle switches;
• radio buttons;
• tappable rows for navigation.

Don’t mix interactor types on the same page. Look at how the Monero app is consistent with the types of its settings:

Case study: blind signing for the Ethereum app

  Important
This is not how the Ethereum app functions today, but it could be a great UX practice to put in place.

The “blind signing” setting of the Ethereum app allows users to review and sign transaction payloads outside of the safety of clear signing. It’s off by default in order to protect users, and it’s reset whenever the Ethereum app is updated or reinstalled.

When a signing operation requires the “blind signing” setting to be on, it’s recommended to invite users to activate the setting, instead of the wallet returning an error, or worse, doing nothing. That way, users have a natural continuation to their action, while still being warned about the safety of their operation.

---

Did you find this page helpful?

How would you improve this page for developers?

I am a developer.
Contributors will be chosen randomly to receive rewards. Check this box to send your email and participate.

Ledger collects your email address to send you rewards for your contribution to improve the Developer Portal documentation. Learn more about how we manage your data and your rights.

By providing your email address, you consent that Ledger may contact you for rewards delivery purposes. If you are part of the randomly selected contributors, we will send you an email to ask for your physical address and if necessary, ask you for additional information on the suggestion you made. Your information will only be available to Ledger and will be retained for no longer than 90 days. It may be transferred to non-European countries that ensure an adequate level of protection or under the standard contractual clauses adopted by the EU Commission.

Please note that you may withdraw your consent at any time, access your data and request their rectification or deletion. You may also request the limitation of the processing of your data. To exercise your rights or for any question on the processing of your data, please contact LEDGER’s Data Protection Officer here. If nevertheless you believe LEDGER did not adequately address your concerns and mishandled your data, you may lodge a complaint with the personal data protection authority of your country.

App’s home

← Previous

Transactions

Next →