-
Notifications
You must be signed in to change notification settings - Fork 748
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
VOIP call cards are too large #2955
Comments
the suggestion is also mentioned here |
Well it's certainly leaps and bounds over what we have currently (at least on android), and personally I like it quite a bit. If it was implemented just like this I would be quite happy. My only concern is that the cards are still a bit tall. I often have 2-6 calls in a row when I do end up calling someone/getting called, and this card design would quickly fill the scroll height of the conversation. One thing that would probably help with the space issue is combining similar cards, I mentioned a possible way of doing that in this issue for Element Web: element-hq/element-web#16409 (comment) In addition you might want to put things more side by side so they don't take as much height. Perhaps make a few quick mockups to see if you can make it look good and be smaller vertically, I'm not entirely sure. I'm more of an illustrator than UX/UI designer. Overall, looks really good though! |
Agreed. An option to collapse them to a single line event would also be nice, like Element web can do. |
It would also be nice to be able to (temporarily) hide/delete calls (like in element-web). |
At first the cards seem great, they reduce the number of lines in a chat, but the problem is they're huge! They should be one or two lines tall at most, not the almost 5 line tall card height that is currently used. It takes up valuable space for any conversation that's important.
Obviously this is somewhat based on preference, but hopefully at least some people agree that the card size should be reduced for usability and readability.
The text was updated successfully, but these errors were encountered: