I find the floating bubbles which are for instance featured by Facebook Messenger very convenient. It makes it way easier to have several conversations at a time or to work with another app while answering incoming messages from time to time. Maybe this could be implemented for TextSecure in the future, too?
Mosrite
All 6 comments
If by floating bubbles you mean the "heads", I'm not sure that would be a good idea. It slows down phones pretty badly. To solve the problem of having several conversations at a time, textsecure could use a tab-like UI, sort of like surespot did. For example, swiping right could take you to the next conversation in the list, and swiping left could take you to the previous one. I think that would be much easier to implement and wouldn't even slow down the app that much.
What do you think?
ghost
on 23 Apr 2015
Yeah, exactly, I mean the heads. Maybe this could be implemented as an option? Just like Facebook does it? People with faster phones could enable it, while all others would leave it disabled.
A tab-like UI would improve parallel conversations but wouldn't help for switching between a conversation an another app. Furthermore, I think tabs might be used in the future to distinguish calls from text messages when RedPhone and TextSecure will be merged.
Mosrite
on 23 Apr 2015
Additional info: https://www.facebook.com/help/android-app/101495056700254?rdrhc
And end users commenting at how much they love FB messenger: https://www.reddit.com/r/Android/comments/4oa7iy/discussion_facebook_has_finally_given_me_the/
yoasif
on 16 Jun 2016
Would be helpful indeed. Especially for group chats where distinguishing between people can be difficult. Perhaps colored chat bubbles (one color for each person) could solve that as well though.
askielboe
on 10 May 2017
Is there any particular reason why there's so little discussion on this? It seems this was a requested feature since 2015.
I can understand if it's due to difficulties in implementing this or having focus on the core user experience with Signal as is but there's no official word on this.
JustPassingByHere
on 6 Oct 2017
GitHub Issue Cleanup:
See #7598 for more information.
automated-signal
on 2 Apr 2018
Related issues
nxfifteen
路
3Comments
derWalter
路
3Comments
kwlg
路
3Comments
j3fffff
路
3Comments
FeuRenard
路
3Comments
Most helpful comment
Is there any particular reason why there's so little discussion on this? It seems this was a requested feature since 2015.
I can understand if it's due to difficulties in implementing this or having focus on the core user experience with Signal as is but there's no official word on this.