ALLO Messenger
A messenger with encryption by default: chats, calls, and privacy. A fallback channel when filtering and allowlists cut off familiar apps.
Gosha
Designer
Anastasia
Project Manager
Vasya
Mobile Developer
Andrey
Mobile Developer
Stas
Mobile Developer
Yaroslav
Backend Developer
Vladislav
Backend Developer
Sasha
DevOps Engineer
Evgeniya
QA Engineer
A familiar messenger stops opening: filtering, an allowlist, or pressure to “just use the one official channel.” The question left is where to write and call — without ads and without hunting for security settings.
ALLO is the messenger WAPP is building as a working alternative. Encryption is on from the start. Chats and calls live in one app. The channel stays usable when the usual app stack becomes unpredictable.
The brief was not a checkbox clone. It was a fallback communication contour: protection by default, familiar flows, and control over what others see.
What the client needed
People should use the messenger in daily life and at work. No ad feed, no extra channels on top of chat, and no scavenger hunt for where to turn protection on.
In parallel — resilience when parts of the network are cut or only “approved” services remain. Users need a separate communication contour, not only a single state messenger by default.
Four things had to work from day one. Without them the product fails as an everyday tool:
- messaging and calls with protection on immediately, no manual setup;
- a familiar set: chats, groups, media, stories — so people are not asked to endure a stripped MVP;
- privacy under user control: number, last seen, devices, blocklist;
- human support: the product is young, and feedback feeds the roadmap.
The public product description is on allo.love. Below — how that looks in the interfaces already built.
How people reach chats
Onboarding goes straight to messaging: language, welcome, phone, code — then the app. Not ten settings screens before the first message.
Auth is a short path: welcome → phone → code → chats. No ads and no feed on top of sign-in.
Onboarding: Minutes to chats — not a hunt for where to enable protection.
How chats and groups work
Personal and group threads include files, reactions, replies, and search. A group is more than a message feed: members, settings, and admin rights sit next to the conversation. No jump to another app to add someone or change permissions.
Groups cover family, friends, and work teams: chat, group profile, and settings in one place.
Groups: Fewer switches — less chance of losing conversation context.
How contacts and profile work
Search and add contacts, a card with number and status, a profile screen. What others see is decided on clear screens — not in a buried menu of ten items.
Contacts and profile: who to add, how you appear, what to hide. No dozen tabs.
People: Contact list and data control in one contour.
How security and privacy work
End-to-end encryption for chats turns on automatically. Audio and video calls are protected from the start. Users can hide number, last seen, photo, and status. Device list and active sessions live in one place — easier to see who else is signed in.
What WAPP does on the project
WAPP runs product development: client apps, backend, calls, privacy flows, and releases. The studio’s job is to keep the loop “app works → people can write and call,” including after the public launch.
On the ALLO site the team says the path has only started, but support already replies. Ideas from feedback go into the roadmap. Features and stability grow release by release.
What keeps the channel resilient
A messenger is more than chat screens. Message delivery, media, device sessions, calls, and profile access rules all matter. The contour is built so that:
- protection and privacy are the default state, not an option “for paranoids”;
- calls and chats live in one product — no jump to third-party apps;
- the product can grow in iterations (stories, groups, screen share) without breaking “wrote → delivered → called.”
We do not publish the exact stack and internal diagrams in the open case. For the client, what matters is the user-side result and channel resilience.
What is already live
- Public product and site: allo.love.
- In the app and layouts: onboarding, chats and groups, contacts, profile, privacy.
- Next — features and stability under load and support feedback.
If you need a full messenger with encryption, calls, and privacy controls — especially as a fallback channel outside a single imposed app — the conversation starts with the user scenario and channel risks, not a slideshow of pretty screens.