@saviq:
The way phone calls and messages are clustered is different.
Whilst call history clusters calls per contact per day the messaging only does it per contact so that you wont create duplicates in the inbox. You have a chronological conversation history in the messaging thread.
The recent calls view can have e.g. on a Monday a clustered entry with 1 number if you received a call and made a call to this number. However if you call that person on a Tuesday it becomes a new data entry. The most important thing users want to know in recent calls is WHEN certain calls were made and who to. If you tap on a list item in recent calls, you will be always calling that entry. Whilst for messaging you are drilling down into a conversation.
In messaging apps users mostly want to know WHO they chatted with, content of the last message not necessarily when. Also showing multiple entries creates unneeded duplicates which bring other issues. E.g. multiple saved threads to a person will have either be kept up to date with the last message sent/received. Otherwise a user might tap on a thread with a person and will only see the last message from that day. This can lead to confusion.
Finally, as a security measure we could introduce a dialog asking users if they really want to delete the whole conversation. Maybe that would prevent accidental removal of the whole thread.
@saviq:
The way phone calls and messages are clustered is different.
Whilst call history clusters calls per contact per day the messaging only does it per contact so that you wont create duplicates in the inbox. You have a chronological conversation history in the messaging thread.
The recent calls view can have e.g. on a Monday a clustered entry with 1 number if you received a call and made a call to this number. However if you call that person on a Tuesday it becomes a new data entry. The most important thing users want to know in recent calls is WHEN certain calls were made and who to. If you tap on a list item in recent calls, you will be always calling that entry. Whilst for messaging you are drilling down into a conversation.
In messaging apps users mostly want to know WHO they chatted with, content of the last message not necessarily when. Also showing multiple entries creates unneeded duplicates which bring other issues. E.g. multiple saved threads to a person will have either be kept up to date with the last message sent/received. Otherwise a user might tap on a thread with a person and will only see the last message from that day. This can lead to confusion.
Finally, as a security measure we could introduce a dialog asking users if they really want to delete the whole conversation. Maybe that would prevent accidental removal of the whole thread.