Comparison of cross-platform instant messaging clients

From Wikipedia, the free encyclopedia

The landscape for instant messaging involves cross-platform instant messaging clients that can handle one or multiple protocols.[1] 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.

General

Summarize
Perspective
More information Client, Developer ...
Close

Operating system support

More information Client, Windows ...
Close

Connectivity

More information Client, Registration requirement ...
Close

Privacy

Summarize
Perspective

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.

More information Client, Share username ...
Close
  • 1: Apple iOS doesn't allow screenshot protection.

Screenshot security

More information Client, Hide number in chats ...
Close

Message handling

More information Client, Threads ...
Client Threads Sent messages Read messages Self-destructing messages
Threads Collapse[128] Ignore Editing Deleting Delete for contacts Delete notification Receipts Hide receipts Exists Deletion trigger
Briar Yes[129] No No Yes No
Discord Yes Yes[130] Yes[131] Yes Yes No No
Element Yes[132] Yes No Partial Yes Yes No
Fractal
Gadu-Gadu
Gajim Yes Yes No
Gitter
Google Chat Yes[133] Yes Yes Originally for Google Workspace accounts only; rolled out to consumer accounts in July 2023[134] Originally for Google Workspace accounts only; rolled out to consumer accounts in July 2023 Yes No
Google Messages (RCS) No No No No Yes Yes No
ICQ No No No Yes
Jami No No No No Desktop only No Not applicable Yes[135] Android only[135] Yes
Jitsi No No No No
KakaoTalk No No No
Kik Messenger No No No
Line No No No No Partial Yes No
Linphone No No No
Mattermost Yes Optional 7+[136] No Yes Yes No No
Messages (Apple) No No No No
Messenger Yes[137] No No No Yes Yes Yes
Movim Yes[138] No No Yes Yes No
Mumble No No No
Palringo No No No
Paltalk No No No
Pidgin No No No Yes
Psi No No No Yes
RetroShare Yes Yes[139] No No No Yes No
Ricochet No No No
Signal No No No Yes Yes Within 24 hours[140] Yes Yes Yes Yes Read[141]
Skype No No No
Slack Yes Yes[142] Yes[143] Yes Yes Yes
Snapchat No No No No Yes Yes Yes
Surespot No No No No
TeamNote No No No Yes Yes No
Telegram No[144] No No Yes Yes Yes No Yes No Yes Read
Tencent QQ No No No
Threema No[145] No No No Yes Yes No
Trillian No No No Yes
Viber No No No Yes Yes Yes Yes
WeChat No No No
WhatsApp No No No No Partial Yes Yes No
Wire No No No Yes Yes Yes Yes[146]
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
Close

Media

More information Client, File transfer ...
Close

Backup and restore messages

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

Miscellaneous

Summarize
Perspective

Messaging services can operate around different models, based on security and accessibility considerations.[152]

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.

More information Client, Typing notifications ...
Close

See also

Notes

  1. In addition to other official and third-party solutions, a native desktop application can be generated for the instant messaging app website using Nativefier.[101]

References

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.