---
title: "Discussion on \"What we learned building two-way voice translation for Google Meet\" | Hashnode"
description: "Discussion on \"What we learned building two-way voice translation for Google Meet\". Engineering lessons from two-way meeting translation: audio routing, extension and desktop ownership, playback queues, and session cleanup."
url: "https://hashnode.com/posts/what-we-learned-building-two-way-voice-translation-for-google-meet/6ad4bdda9497ce6f27a85324"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [What we learned building two-way voice translation for Google Meet](https://meetvoice.hashnode.dev/what-we-learned-building-two-way-voice-translation-for-google-meet?utm_source=hashnode&utm_medium=feed)

Engineering lessons from two-way meeting translation: audio routing, extension and desktop ownership, playback queues, and session cleanup.

Oct 18 · 6 min read · meetvoice.hashnode.dev  
Read the article

-   [#browser-extension](https://hashnode.com/tag/browser-extension)
-   [#audio-processing](https://hashnode.com/tag/audio-processing)
-   [#software-architecture](https://hashnode.com/tag/software-architecture)

## Written by

[Oleksii Herasymchuk](https://hashnode.com/@alexeyyy)

@alexeyyy · Plovdiv

  
[View profile](https://hashnode.com/@alexeyyy)

Building MeetVoice, a tool for two-way voice translation in Google Meet. Writing about browser extensions, audio, and multilingual meetings.

I work on MeetVoice, a Chrome extension and desktop app for two-way voice translation in Google Meet. Here I share practical lessons from building browser extensions, working with meeting audio, and making multilingual calls easier to follow. MeetVoice: https://meetvoice.app/

## Responses

Markdown supported · ⌘↵ to post

No responses yet.