<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Web Audio Api on VibePapa — Tech from the Boseong River</title>
    <link>https://boseonggang.com/tags/web-audio-api/</link>
    <description>Recent content in Web Audio Api on VibePapa — Tech from the Boseong River</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 18 Jul 2026 07:23:15 +0900</lastBuildDate>
    <atom:link href="https://boseonggang.com/tags/web-audio-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Two Features Walked Into My App. Only One Could Leave.</title>
      <link>https://boseonggang.com/posts/two-features-walked-into-my-app/</link>
      <pubDate>Sat, 18 Jul 2026 07:23:15 +0900</pubDate>
      <guid>https://boseonggang.com/posts/two-features-walked-into-my-app/</guid>
      <description>Speaker-audio recognition worked. Translated voice playback worked. They never worked at the same time, and fixing one always broke the other. The real fix wasn&amp;#39;t a bug fix at all, it was accepting that two good features couldn&amp;#39;t share one microphone, and building a switch instead of a workaround.</description>
    </item>
  </channel>
</rss>
