When WhatsApp’s threaded replies first appeared, in an iOS beta distributed to a small group of TestFlight users, the feature was a bare arrow beside a message that collected the replies to it. The Android build now reaching testers is a more finished thing, and the difference is worth reading closely, because it tells you what WhatsApp decided threads are for.
What the Android beta does
In version 2.25.25.7, distributed through the Play Store beta programme, a message that has been replied to carries a reply indicator inside its own bubble, showing the number of replies attached to it. Tapping the indicator opens a dedicated thread view containing those replies in order.
Two details in that sentence matter more than they look. The first is the counter: a number on the bubble turns a thread from something you have to go looking for into something that announces itself. The second is that the indicator lives inside the message bubble rather than beside it, which means the thread belongs to the message, not to the chat — the same structural choice Slack made in 2017 and Discord made in 2022.
Inside a thread, replying is a two-step decision rather than one. You can answer the most recent message, or pick an earlier message in the thread and answer that. Testers report that a reply aimed at a specific earlier message arrives carrying a “Follow-up reply” label, which is WhatsApp’s way of keeping a thread from needing threads of its own.
Where it will appear
The scope is wider than the group-chat problem threads are usually sold as fixing. Reporting on the beta describes the feature covering one-to-one chats, group chats, communities and channels. Channels are the interesting one: a channel is a broadcast, often with tens of thousands of followers, and until now the reaction space under a channel post has been an undifferentiated pile. Threads give a channel the comment structure that broadcast-style messaging has always lacked, which is a product change of a different order from tidying up a family group.
What Slack already learned
Threads are not a free improvement, and the platform that has run them longest is the best evidence. Slack shipped threaded replies in 2017 to solve exactly WhatsApp’s problem: answers to a question scattered through unrelated traffic. It worked. It also created a new failure, which is that a reply inside a thread is easy to never see. Slack’s own answer was to add a checkbox — also send to channel — that undoes the threading for any reply important enough to need everyone’s eyes. Discord arrived at a similar place by giving threads a lifespan and surfacing unread ones separately.
The lesson is that threads move work rather than removing it. Before threads, the person collecting answers does the work of scrolling back. After threads, the person sending an answer does the work of deciding whether it belongs in the thread or the room, and the people who skim do the work of checking both. On a work tool where everyone has agreed to the convention, that trade is clearly worth making. On a messaging app shared with relatives who will tap whatever is nearest, the trade is less obvious, and WhatsApp’s design — replies still visible in the main conversation, the thread as an additional reading view rather than a hiding place — reads as an attempt to take the benefit without the cost.
When you can expect it
This is a beta, and a staged one: not every tester on 2.25.25.7 has the feature, because WhatsApp gates it server-side. The iOS version is reported to be in development so the two platforms match at launch. WhatsApp’s recent pattern with comparable features — group Events, the Meta AI entry point, default HD photos — has been a limited beta, then a wider beta, then a gradual worldwide rollout measured in months rather than weeks. Nothing has been announced.
If you want it early, WhatsApp’s beta programme is opt-in through the Play Store listing and is usually full; places open when existing testers leave. If you do not, the thing to know is that nothing you currently do will break. Quote-reply is not going away, and a chat whose participants never tap the counter will behave exactly as it does today.
