Skip to content
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

Timestamps in bubbles use unnecessary vertical screen realestste #95

Closed
ara4n opened this issue Jun 25, 2022 · 2 comments
Closed

Timestamps in bubbles use unnecessary vertical screen realestste #95

ara4n opened this issue Jun 25, 2022 · 2 comments
Labels
Z-BBQ-Alpha Required for ElementX - BBQ - Alpha

Comments

@ara4n
Copy link
Member

ara4n commented Jun 25, 2022

Describe the bug
Looking at the current demo screenshot of bubbles, we are wasting about 30% of the available vertical screen realestate on timestamps. Timestamps should only have their own line if there is not room to put them at the right hand side of the bubble - see Telegram for a great example of doing this.

To Reproduce

Observe that most of these timestamps are needlessly on a new line when they could be put on the rhs of the last line of content in their respective bubbles:

image

Expected behavior

Moar vertical screen estate = being able to read moar msgs

@pixlwave
Copy link
Member

My perspective on this would be to favour an option to hide the timestamps all together. For the personal messenger use-case, I'm rarely interested in the exact time a message came in. It would still need an interaction to reveal the timestamp for a specific message for those few times someone wanted to see it, but it would result in a less cluttered layout IMO.

@stefanceriu stefanceriu added the Z-BBQ-Alpha Required for ElementX - BBQ - Alpha label Jun 30, 2022
@stefanceriu
Copy link
Member

No longer relevant as per latest designs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Z-BBQ-Alpha Required for ElementX - BBQ - Alpha
Projects
None yet
Development

No branches or pull requests

3 participants