Jami

First contact with Jami: account creation and device linking

Opening Jami for the first time presents a simple screen with two options: "Create a new account" and "Link this device to an existing account." The account creation process is straightforward. It asks for a display name and a password. No phone number, no email address. The app generates a unique Jami ID, a long string of characters that serves as your identity. This ID is what others use to find and contact you. The password is used to encrypt your account data locally. The app does not store your password on any server. This is a key feature of the decentralized architecture. Once the account is created, the main dashboard loads. This dashboard shows a list of contacts, a call history, and a settings menu. The interface is clean but minimal. There is no tutorial or walkthrough. New users must explore on their own. The "Add contact" button is the most prominent feature. Tapping it allows entering a Jami ID or scanning a QR code. The app also supports adding SIP accounts, which is useful for users who want to integrate traditional phone systems. The settings menu allows configuring audio/video options, extensions, and account management. The entire onboarding process takes about two minutes, assuming the user already has a Jami ID to add or knows how to create one.

For users who want to use Jami on multiple devices, the app offers a "Link device" feature. This allows linking a new device to an existing account. The process requires scanning a QR code from the primary device. Once linked, the new device synchronizes contacts and messages. However, this synchronization is not always immediate. Some users have reported that messages do not appear on all devices simultaneously. The app relies on the distributed hash table (DHT) for discovery, which can introduce delays. This is a trade-off for the decentralized nature of the platform.

When peer-to-peer meets multi-device synchronization

The app's core value is enabling private, decentralized communication. The peer-to-peer architecture is the primary tool for this. Calls and messages go directly from one device to another, with no central server in between. This provides a high level of privacy and security. The end-to-end encryption ensures that only the intended recipient can read the messages. This works well when both devices are online and reachable. However, the real test comes when a user wants to use Jami on multiple devices simultaneously. Suppose a user has Jami installed on their phone and their desktop computer. They send a message from the desktop. The message goes directly to the recipient's device, but it also needs to appear on the user's phone. This requires synchronization between the user's own devices. The app uses a distributed mechanism for this. In theory, it works seamlessly. In practice, problems arise when the devices are not on the same network or when one device is offline. Some users have reported that messages sent from one device do not appear on another device until much later. This is likely due to the DHT propagation delays. The app does not provide a way to force an immediate sync. Users are left to wait. This clash between the peer-to-peer architecture and multi-device support creates a frustrating experience. The app does not offer a central server to coordinate synchronization, which is the root cause of the issue.

Furthermore, the app's handling of group chats is also problematic. The forum posts indicate that group messages often get lost or do not synchronize properly. This is a significant limitation for users who rely on Jami for team communication. The original analysis here is that the app's architecture prioritizes privacy and decentralization over reliability and convenience. This is a deliberate design choice, but it comes with trade-offs. The user must accept these trade-offs to use the app. This is not apparent from reading the Play Store description, which emphasizes privacy and freedom but downplays the reliability issues.

Real-world performance and common issues

User reports from various platforms paint a mixed picture of the app's stability. Some users praise the app for its privacy features and the fact that it does not require a phone number or email. They appreciate the open-source nature and the cross-platform support. However, others report persistent issues with reliability. Several users have complained that messages are not received when the recipient is offline for a long time. This is a fundamental problem for a messaging app. The app does not provide a way to store messages on a server for offline delivery. This is a limitation of the peer-to-peer architecture. Some users have also reported that the app crashes frequently, particularly when loading the contact list or the call history. The crashes are not frequent, but they are disruptive. The app does not display a crash report or offer to send logs to the developer. It simply disappears and returns to the home screen. Restarting the app usually resolves the issue temporarily. On the positive side, the app's audio and video call quality is generally good when both parties have a stable internet connection. The calls are clear and the latency is low. The screen sharing feature also works well.

Another issue is the app's handling of account recovery. The app does not provide a way to recover an account if the password is lost or if the device is reset. The account is tied to the device, and there is no central server to restore it. This is a significant problem for users who switch devices frequently. The app also lacks a built-in backup feature. Users have to manually back up their data, which is not straightforward. This lack of account recovery and backup is a major limitation for many users. The app also has occasional issues with the auto-answer feature for video calls. Some users have reported that the auto-answer switch does not work, and they have to manually answer calls. This defeats the purpose of the feature.

Storage permission and the lack of a changelog

The app requires storage permission to send files and to store media. This is stated clearly during installation. However, the app does not explain why it needs this permission. Users are left to guess. The developer's changelog is not available on the Play Store. No specific bugs are named. No performance metrics are provided.