Ledger model choice should start from the user's routine. Screen preference, connection needs, capacity boundary, and app habits make the comparison clearer than a generic ranking.
Start with the main use case
Write whether the device will mainly stay near a computer, move between devices, or be used with a mobile routine. The China buying scenario guide keeps model fit tied to actual use.
Match screen and connection needs
If mobile use or wireless convenience matters, compare connection habits directly. The Bluetooth and mobile-use guide gives a same-column comparison point.
Define the capacity boundary
Capacity should be written as an app-management boundary, not as a promise about future use. Record how many apps the user expects to manage and how often app changes are likely.
Use device role as the closing check
The final note should connect use case, screen, connection, capacity, and app routine. For basic device-role context, the hardware wallet working-principle guide explains the device and app relationship.
