How it works
A session host publishes translated turns; joined devices subscribe and render in their own language. Discontinued in Microsoft Translator, still core to apps like PolyPort.
What is device-to-device translation?
Device-to-device translation lets several phones or tablets connect to a shared conversation. One person speaks, and every other device shows or plays the translation in its own language.
This is different from handing one phone back and forth. Each participant keeps their own screen and language.
How Microsoft Translator used to do it
Microsoft Translator once offered a popular conversation feature where participants joined by scanning a QR code or entering a conversation code. It worked well for classrooms and small meetings.
Microsoft later scaled back and removed the multi-device conversation feature from consumer versions, focusing instead on enterprise and API integrations.
Why it was discontinued
Consumer multi-device features are expensive to maintain: they need real-time servers, abuse prevention, and cross-platform sync. Microsoft prioritized its Azure Translator service and enterprise customers over the free consumer app.
Alternatives today
Apps like PolyPort.chat and some classroom-focused tools still offer device-to-device sync. Google Translate has a limited conversation mode. For large events, dedicated conference translation systems are usually more reliable.
Frequently asked questions
Do I need an internet connection?
Most device-to-device modes need the internet to coordinate participants and run cloud translation. Some specialized classroom systems can work over local Wi-Fi.
Is it private?
Privacy depends on the app. End-to-end encrypted solutions are rare; most cloud-based systems process audio on their servers. Check the provider's privacy policy before discussing sensitive topics.
