Unify copy of device verification using another device #2898
Description
Background
The future designs of device verification, using another device, have been revisited. Note that these future designs are already implemented on EX (except that support for QR code verification is missing) whereas EW is currently still using legacy designs.
The eventual goal is to also implement the future designs on EW, as well as support QR code verification on EX but for this ticket the scope is to make sure that the copy across the platforms is consistent, in particular motivated by the fact that some copy on EW is heavily misleading.
During the revisiting of the designs, 2 things were adjusted:
- Ironing out copy inconsistencies.
- Shortening/simplifying the flow by immediately going QR-code verification (in case it is supported) and offering emoji as fallback; or going immediately to comparing emojis (in case QR-code verification is not supported).
- Note that this is more or less the case already in EW's current implementation but the future designs had the concept of asking the user to make a user an explicit choice in advance which caused an extra step. This has been now removed.
The designs for reference:
- Web: Verify at sign-in; Incoming verification request
- iOS: Verify at sign-in; Incoming verification request
- Android: Verify at sign-in; Incoming verification request
EW
Copy on Element Web current implementation should be updated as follows.
Verification requested (incoming)
Verify Session --> Start verification
Start at the other device (verify at sign-in)
Verify other device --> Start verification on the other device
To proceed, please accept the verification request on your other device. --> Once accepted you’ll be able to continue with the verification.
Choose verification method
This screen will have a different approach in the new designs (primary with a fallback vs selection between 2 options), thus the copy adjustments are stop-gap to avoid major mislead.
Verify other device --> Choose how to verify
Verify this device by completing one of the following: --> Verify by completing one of the following:
Compare emojis
Verify other device --> Compare emojis
Confirm the emoji below are displayed on both devices, in the same order: --> Compare that the emojis below match those shown on your other device
Verification successful
Since the future designs differentiate between an incoming request and verification at sign-in when it comes to this screen (copy is slightly different), then we will adjust the title only for now.
Verify other device --> Device verified
Verification cancelled
Verify other device --> Verification failed
Verification cancelled --> Delete this line
You cancelled verification on your other device + Start verification again from the notification. --> Either the request timed out, the request was denied, or there was a verification mismatch.
Note that EW has currently a dedicated screen for when there is a verification mismatch. This will remain currently as is, but is merged into a more generic verification failed modal in the future designs.
EX
Verification requested (incoming)
Start --> Start verification
Start at the other device (verify at sign-in)
Waiting for the other device --> Start verification on the other device
Compare emojis
Compare that the emojis below match those shown on your other session --> Compare that the emojis below match those shown on your other device
Verification successful (incoming request)
Verification complete --> Device verified
Your new session is now verified. It has access to your encrypted messages, and other users will see it as trusted. --> Now you can read or send messages securely on your other device.
Verification successful (verify at sign-in)
Verification complete --> Device verified