Comparison of cross-platform instant messaging clients

Template:Short description Template:See also {{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= Template:Ambox }} The landscape for instant messaging involves cross-platform instant messaging clients that can handle one or multiple protocols.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> Clients that use the same protocol can typically federate and talk to one another. The following table compares general and technical information for cross-platform instant messaging clients in active development, each of which have their own article that provide further information.

GeneralEdit

Template:Sticky header Template:Sort-under

Operating system supportEdit

Template:Sticky header

ConnectivityEdit

Template:Sticky header Template:Sort-under

PrivacyEdit

Some messaging services that are not designed for privacy require a unique phone number for sign-up, as a form of identity verification and to prevent users from creating multiple accounts.

Some messaging services that do not solely focus on a mobile-first experience, or enforce SMS authentication, may allow email addresses to be used for sign-up instead.

Some messaging services offer greater flexibility and privacy, by allowing users to create more than one account to compartmentalize personal & work purposes, or not requiring personally identifiable information for sign-up.

To find out if the software has end-to-end encryption, see "media" table below.

Template:Sticky header Template:Sort-under

  • 1: Apple iOS doesn't allow screenshot protection.

Screenshot securityEdit

Template:Sticky header

Message handlingEdit

Template:Sticky header

Client Threads Sent messages Read messages Self-destructing messages
Threads Collapse<ref>The Importance of Message Threads in Team Messaging Apps</ref> Ignore Editing Deleting Delete for contacts Delete notification Receipts Hide receipts Exists Deletion trigger
Briar Template:Yes<ref>Briar User Manual</ref> Template:No Template:No Template:Yes Template:No
Discord Template:Yes Template:Yes<ref>Discord Threads FAQ</ref> Template:Yes<ref>Discord I Want To Leave A Thread</ref> Template:Yes Template:Yes Template:No Template:No
Element Template:Yes<ref>Introducing Threads in Beta!</ref> Template:Yes Template:No Template:Partial Template:Yes Template:Yes Template:No
Fractal
Gadu-Gadu
Gajim Template:Yes Template:Yes Template:No
Gitter
Google Chat Template:Yes<ref>Learn how to manage a space with in-line threading</ref> Template:Yes Template:Yes Template:Partial<ref>{{#invoke:citation/CS1|citation CitationClass=web

}}</ref>

Template:Partial Template:Yes Template:No
Google Messages (RCS) Template:No Template:No Template:No Template:No Template:Yes Template:Yes Template:No
ICQ Template:No Template:No Template:No Template:Yes
Jami Template:No Template:No Template:No Template:No Template:Partial Template:No Not applicable Template:Yes<ref name="Jami FAQ">{{#invoke:citation/CS1|citation CitationClass=web

}}</ref>

Template:Partial<ref name="Jami FAQ" /> Template:Yes
Jitsi Template:No Template:No Template:No Template:No
KakaoTalk Template:No Template:No Template:No
Kik Messenger Template:No Template:No Template:No
Line Template:No Template:No Template:No Template:No Template:Partial Template:Yes Template:No
Linphone Template:No Template:No Template:No
Mattermost Template:Yes Template:Okay<ref>Organize conversations using Collapsed Reply Threads</ref> Template:No Template:Yes Template:Yes Template:No Template:No
Messages (Apple) Template:No Template:No Template:No Template:No
Messenger Template:Yes<ref>Facebook Messenger gets threaded replies</ref> Template:No Template:No Template:No Template:Yes Template:Yes Template:Yes
Movim Template:Yes<ref>Movim: a decentralized open-source XMPP-based messaging and social platform</ref> Template:No Template:No Template:Yes Template:Yes Template:No
Mumble Template:No Template:No Template:No
Palringo Template:No Template:No Template:No
Paltalk Template:No Template:No Template:No
Pidgin Template:No Template:No Template:No Template:Yes
Psi Template:No Template:No Template:No Template:Yes
RetroShare Template:Yes Template:Yes<ref>Retroshare » Docs » User Guide » Interface</ref> Template:No Template:No Template:No Template:Yes Template:No
Ricochet Template:No Template:No Template:No
Signal Template:No Template:No Template:No Template:Yes Template:Yes Template:Partial<ref>{{#invoke:citation/CS1|citation CitationClass=web

}}</ref>

Template:Yes Template:Yes Template:Yes Template:Yes citation CitationClass=web

}}</ref>

Skype Template:No Template:No Template:No
Slack Template:Yes Template:Yes<ref>Use threads to organize discussions</ref> Template:Yes<ref>How to Unfollow Thread in Slack?</ref> Template:Yes Template:Yes Template:Yes
Snapchat Template:No Template:No Template:No Template:No Template:Yes Template:Yes Template:Yes
Surespot Template:No Template:No Template:No Template:No
TeamNote Template:No Template:No Template:No Template:Yes Template:Yes Template:No
Telegram Template:No<ref>Bugs and Suggestions » Threads</ref> Template:No Template:No Template:Yes Template:Yes Template:Yes Template:No Template:Yes Template:No Template:Yes Read
Tencent QQ Template:No Template:No Template:No
Threema Template:No<ref>Comparison of Communication Tools for Companies</ref> Template:No Template:No Template:No Template:Yes Template:Yes Template:No
Trillian Template:No Template:No Template:No Template:Yes
Viber Template:No Template:No Template:No Template:Yes Template:Yes Template:Yes Template:Yes
WeChat Template:No Template:No Template:No
WhatsApp Template:No Template:No Template:No Template:No Template:Partial Template:Yes Template:Yes Template:No
Wire Template:No Template:No Template:No Template:Yes Template:Yes Template:Yes Template:Yes<ref>{{#invoke:citation/CS1|citation CitationClass=web

}}</ref>

Client Threads Sent messages Read messages Self-destructing messages
Threads Collapse Ignore Editing Deleting Delete for contacts Delete notification Receipts Hide receipts Exists Deletion trigger

MediaEdit

Template:Sticky header

Backup and restore messagesEdit

Official status to guarantee support for backing up and restoring messages.

Template:Sticky header

MiscellaneousEdit

Messaging services can operate around different models, based on security and accessibility considerations.<ref name="messenger-model-design-decisions">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

A mobile-focused, phone number-based model operates on the concept of primary and secondary devices. Examples of such messaging services include: WhatsApp, Viber, Line, WeChat, Signal, etc. The primary device is a mobile phone and is required to login and send/receive messages. Only one mobile phone is allowed to be the primary device, as attempting to login to the messaging app on another mobile phone would trigger the previous phone to be logged out. The secondary device is a computer running a desktop operating system, which serves as a companion for the primary device. Desktop messaging clients on secondary devices do not function independently, as they are reliant on the mobile phone maintaining an active network connection for login authentication and syncing messages.

A multi-device, device-agnostic model is designed for accessibility on multiple devices, regardless of desktop or mobile. Examples of such messaging services include: Skype, Facebook Messenger, Google Hangouts (subsequently Google Chat), Telegram, ICQ, Element, Slack, Discord, etc. Users have more options as usernames or email addresses can be used as user identifiers, besides phone numbers. Unlike the phone-based model, user accounts on a multi-device model are not tied to a single device, and logins are allowed on multiple devices. Messaging services with a multi-device model are able to eliminate feature disparity and provide identical functionality on both mobile and desktop clients. Desktop clients can function independently, without relying on the mobile phone to login and sync messages.

Template:Sticky header

See alsoEdit

Template:Portal

NotesEdit

Template:Notelist

ReferencesEdit

Template:Reflist

Template:Instant messaging