<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Browser AI on Dmitry Sheiko&#39;s Web Development Blog</title>
    <link>https://dsheiko.com/tags/browser-ai/</link>
    <description>Recent content in Browser AI on Dmitry Sheiko&#39;s Web Development Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dsheiko.com/tags/browser-ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Browser AI APIs in Practice: Building a Multilingual Support Inbox</title>
      <link>https://dsheiko.com/weblog/browser-ai-apis-multilingual-support-inbox/</link>
      <pubDate>Wed, 18 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/browser-ai-apis-multilingual-support-inbox/</guid>
      <description>While reading State of HTML 2026 I noticed that Browser AI APIs are already in use quite a bit. Are they good enough for real things, though? The models run on the user&amp;rsquo;s device, so there&amp;rsquo;s no API key and no bill per call. It&amp;rsquo;s free, at least for now. That brought back the customer support inbox we handled in PrestaShop many years ago. If we had to build something like that today, what could Browser AI APIs add to it?</description>
    </item>
  </channel>
</rss>
