-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
End-to-end encryption UI/UX #723
Labels
design
feature
P1
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
Milestone
Comments
giomfo
added
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
feature
P1
design
labels
Oct 13, 2016
giomfo
added a commit
that referenced
this issue
Nov 7, 2016
#723 - Chat screen: Display a padlock in the bottom tool bar in case of encrypted room.
giomfo
added a commit
that referenced
this issue
Nov 7, 2016
#723 - Prompt user before turning on the room encryption - Check power level before displaying toggle button
giomfo
added a commit
that referenced
this issue
Nov 8, 2016
#723 - Define bubbles cells used to displayed encrypted events
giomfo
added a commit
that referenced
this issue
Nov 8, 2016
#723 Bubble cells for encrypted event: add more padding around the encryption icon.
giomfo
added a commit
that referenced
this issue
Nov 8, 2016
#723 - Disable attachments and call options in encrypted room
giomfo
added a commit
that referenced
this issue
Nov 9, 2016
#723 - Let user send clear attachments in encrypted rooms
giomfo
added a commit
that referenced
this issue
Nov 10, 2016
#723 -Prompt the user to log in again when no device id is available.
giomfo
added a commit
that referenced
this issue
Nov 10, 2016
#723 - Add an unencrypted icon in the composer of a non-crypto room
giomfo
added a commit
to matrix-org/matrix-ios-kit
that referenced
this issue
Nov 10, 2016
element-hq/element-ios#723 - Chat history: Display a message for m.room.encryption events
9 tasks
giomfo
added a commit
that referenced
this issue
Nov 16, 2016
#723 - Display device information when user taps on the encryption icon. - Add this option in event context menu
giomfo
added a commit
that referenced
this issue
Nov 16, 2016
#723 - prompt user before verifying a device
No design has been defined for the mobile app yet. We implement the following points by applying the web design:
|
Please fill a new issue for any request on e2e encryption UI/UX |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
design
feature
P1
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
This is a high level bug to track all the design & UI implementation dependencies for E2E crypto, to compliment the list of individual issues we've had historically. It's also written to reflect the guide I gave at the Ribot offices this morning. Top priority first:
Show whether room is either:
Untrusted messages / users / rooms are not necessarily the end of the world, so should not be a huge red flashing warning, but an advisory warning (hence the /!\ suggestion) that users could choose to ignore if they don't care about verifying who they're talking to.
Show whether received messages in an encrypted room are, per message:
Toggle encryption for a room on (and off, in future)
Show whether users in an encrypted room's membership list are:
Show and manage list of devices for a given user. For each device for a user in the MemberInfo contents of RightPanel we need to show:
UI for sending messages in an encrypted room
UI for verifying someone else's device. When the user asks to verify someone's device (e.g. using the UI control mentioned on the previous line), we need to show some UI that guides the user through proving that the device is owned by that user.
Show UI for verifying your own device with someone else.
Show and manage list of our own devices. For each of our devices, in UserSettings, we need to show:
deprioritised:
The text was updated successfully, but these errors were encountered: