Secure Screen should be read as a confirmation-experience topic across newer touchscreen Ledger models. The point is not simply a larger display. The useful question is how screen readability, Ledger Wallet prompts, device-side confirmation, and local records work together.
Touchscreen confirmation changes the reading surface
A touchscreen gives more space for readable prompts and confirmation details. That can make the workflow easier to review, but the same principle remains: compare the app prompt with the device screen before approval and record the final state afterward.
The Nano Gen5 positioning article shows how touchscreen readability, NFC context, and Clear Signing fit into product positioning.
Secure Screen is model language, not a separate shortcut
Secure Screen should not be treated as a way to skip checks. It is a clearer device-side place to read the task. Users should still confirm the source path, app state, and screen wording before continuing.
- Read the app prompt before the device screen.
- Compare screen wording with the task you intended.
- Keep the final confirmation state in a concise record.
Ledger Wallet keeps the screen review grounded
Ledger Wallet provides task context and progress. The device screen provides device-side confirmation. If the two appear to diverge, return to update-layer reading before taking another step. The app versus firmware update guide helps separate app interface changes from device behavior.
Use the article as a dated product note
This row should preserve a product-update reading method, not claim to summarize every future touchscreen experience. Record the model, app version, source path, screen wording, and final state so later comparisons have a stable reference.
