twinme - private messenger

The setup reality: no phone number, but a QR code

The first screen asks for nothing. No phone number field, no email box, no "sign up with Google" button. Just a blank space with a button to generate a profile. Tap it, and the app creates a random numeric ID. That is your identity. You can add a name and a picture, but neither is required. The app does not ask for permission to access your contacts. It does not try to sync your address book. This is a deliberate choice. The app does not know who your friends are. It cannot discover them. To add someone, you must share your twincode. This is a QR code that the other person scans with their device. The process is entirely out-of-band. You send the code via SMS, email, or show it on your screen. The other person scans it, and the connection is established. There is no central server that maps your ID to a phone number or email. The relationship is direct and unique. Each contact gets a separate profile entry. You can customize what name and image they see. You can revoke access at any time. This setup is secure, but it is also cumbersome. Users accustomed to WhatsApp or Telegram will find the lack of automatic contact discovery frustrating. The app does not offer a "find friends" feature. You must manually invite each person.

The onboarding flow is minimal. After generating your profile, you land on an empty chat list. There are no tutorials, no welcome messages, no tips. The app assumes you know what to do. The main screen has a "+" button to add contacts, a chat list, and a menu for settings. The settings are sparse. You can change your name and picture, adjust notification sounds, and enable "zap" mode. Zap mode is a refresh function that clears the app's state without deleting data. It is useful when the app behaves unexpectedly. The app does not have a dark mode, which is a common complaint. The interface is functional but plain. It prioritizes speed over aesthetics. The chat screen is clean. Messages appear in bubbles. You can send text, images, videos, and files. The app does not support voice messages directly, but you can record audio and send it as a file. The call screen is straightforward. Large buttons for mute, speaker, and end call. The call quality is good on stable connections, but it degrades quickly on poor networks. The app uses WebRTC, which adapts to network conditions, but the peer-to-peer nature means both devices must have good connectivity.

How the twincode and peer-to-peer architecture work together

The twincode is more than just a QR code. It encodes a public key and a temporary session identifier. When you scan a twincode, your device initiates a direct WebRTC connection to the other device. This connection is established using a signaling server, but the server does not store any data. It only helps the two devices find each other. Once the connection is established, all communication is peer-to-peer. Messages, files, and call data travel directly between devices. There is no intermediary server that can log or intercept the content. This is the core privacy promise of twinme. However, this architecture has a practical limitation. If both devices are not online at the same time, messages cannot be delivered. There is no store-and-forward mechanism. The app does not use a cloud queue. If your contact is offline, your message stays on your device until they come online. This is different from most messaging apps, which use servers to store undelivered messages. Twinme's approach is more private but less reliable. Users have reported that messages can take minutes or even hours to deliver if the recipient's device is not active. The app also struggles with file transfers. The peer-to-peer connection is limited by the network conditions of both devices. In a test, a 144 MB video took over 10 minutes to transfer, while other apps achieved speeds of 10 MB/s. The developer acknowledged this limitation and stated they are working on improvements.

The interaction between the twincode and the peer-to-peer architecture creates a unique workflow. You cannot simply search for a contact by name or number. You must have a physical or digital interaction to exchange codes. This makes twinme ideal for close-knit groups where members meet in person. It is less suitable for large, distributed networks where you want to add people quickly. The app's "kids" feature leverages this limitation as a strength. Parents can set up a tablet with twinme and only allow contacts who scan the child's twincode in person. This prevents strangers from contacting the child. The app does not have a public directory, so there is no risk of unsolicited messages. This is a powerful safety feature, but it also means the app is not a replacement for mainstream messengers in most social contexts.

Real-world performance: ads, bugs, and smooth operation

The app is free and ad-free. There are no banner ads, no video ads, no promotional pop-ups. The developer states that because twinme does not collect personal data, it cannot be used for commercial purposes. This is a refreshing change from many free apps that rely on ad revenue. The trade-off is that the app's development is funded by the premium version, twinme+. The free version includes all core features, but group calls and some advanced options are limited to the premium tier. The app's performance is generally smooth on modern devices. The UI is responsive, and calls connect quickly. However, the app has a reputation for bugs. Users report occasional crashes, especially during video calls. The "zap" feature is a built-in workaround for these issues. It clears the app's cache and resets the connection state. This is a sign that the developer is aware of stability problems. The app's update frequency is moderate. New versions are released every few months. The changelog often mentions "various improvements and bug fixes," which is vague. The June 2026 update added the ability to allow contacts to connect you with their own contacts. This is a feature that expands the social graph without compromising privacy. It is a smart addition, but it also introduces complexity. Users must now manage two layers of contact relationships.

The app's support infrastructure is minimal. The website has a FAQ section, but some users report that the support site is non-functional. The developer responds to reviews on the Play Store, but the responses are often in Chinese or French. This language barrier can be frustrating for English-speaking users. The app does not have a built-in help section. You must visit the website for assistance. The app's permissions are extensive. It requests camera, microphone, storage, and the ability to run at startup. These are standard for a communication app, but the "run at startup" permission is notable. It allows the app to receive messages even when it is not actively running. This is necessary for the peer-to-peer architecture, as the app must be able to wake up to establish a connection. The app does not request location or contacts permissions, which aligns with its privacy philosophy.

The specific permission that makes the app work

The "run at startup" permission is the most critical. Without it, the app cannot receive messages or calls when it is not in the foreground. This permission allows the app to register a background service that listens for incoming connections. When a contact tries to send a message, the signaling server notifies your device, and the background service wakes up to establish the peer-to-peer connection. This is how twinme achieves its always-on functionality without using a central server. The permission is also used to maintain the WebRTC connection. WebRTC requires a persistent connection to negotiate media streams. If the app is killed by the system, the connection is lost, and messages may be delayed. The "prevent sleep" permission is used during calls to keep the device awake. This ensures that the call does not drop if the screen turns off. The "audio settings" permission allows the app to adjust volume and manage audio focus. These permissions are necessary for the app's core functionality, but they also have implications for battery life. The background service and WebRTC connections can drain battery if not managed properly. The app does not provide detailed information about its battery usage. Users on older devices may experience faster battery drain. The app's minimum Android version is 5.0, which is generous, but performance on older hardware is mixed. The app's file size is around 25-33 MB, which is reasonable for a feature-rich communication app.