-
Notifications
You must be signed in to change notification settings - Fork 12
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
New Direct Messages screen is inconsistent between the different platforms #83
Comments
Thanks for raising - all great points and we hope to address this in Q1 :) |
@daniellekirkwood @giomfo Danielle, please feel free to get in touch for more info. We'll need to touch base on this at some point. |
Discussion of requirements:
This screen will change dependant on the life stage of the user;
|
My request concerns the screen opened when the user wants to create a new DM from the different Element application (Web/Android and iOS)
Here is a screenshot with the current implementation:
Element-web has a "Recent Conversations" section which doesn't exist on the other apps (I don't know if this is really useful)
I consider "Suggestions" and "Known Users" are the same, but they don't list the contacts in the same order (for the same connected account). FYI: known users are people with who the end user shares at least one room
Element-iOS don't have any suggestions, this is a pity...
The contact book access on mobile is handled totally differently on Android and iOS...
These inconsistencies may disturb the end users.They disturb our work at PS level to promote the use of the Element design for this screen. For example, I'm supposed to replace the existing Tchap (DINUM) contacts picker with the Element one. We did for Tchap-Android, but I don't want to do the same on iOS until Element-iOS has a suggestions/known users list. It will be a regression for Tchap end users.
Last remark, I consider this improvement about the contacts picker for the DM creation screen should be taken into account by the Application team (or a Feature team). I don't think we should ask sponsoring for that
(see https://element-io.atlassian.net/browse/PROD-48)
The text was updated successfully, but these errors were encountered: