<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Austin Johnson</title>
    <description>The latest articles on DEV Community by Austin Johnson (@buoygg).</description>
    <link>https://dev.to/buoygg</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4148051%2Fd5c3c2f1-2aeb-48aa-9d43-70e04a161d32.jpg</url>
      <title>DEV Community: Austin Johnson</title>
      <link>https://dev.to/buoygg</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/buoygg"/>
    <language>en</language>
    <item>
      <title>Introducing Buoy.gg — in-app tools for mobile + web apps</title>
      <dc:creator>Austin Johnson</dc:creator>
      <pubDate>Mon, 28 Sep 2026 21:26:50 +0000</pubDate>
      <link>https://dev.to/buoygg/introducing-buoygg-in-app-tools-for-mobile-web-apps-5do5</link>
      <guid>https://dev.to/buoygg/introducing-buoygg-in-app-tools-for-mobile-web-apps-5do5</guid>
      <description>&lt;p&gt;When something breaks in production, the usual loop is slow: reproduce locally, dig through logs, guess at what the user saw, then ship a fix and hope.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Buoy&lt;/strong&gt; is built to shrink that loop. It’s a toolkit of in-app tools for mobile and web apps — aimed at people who ship and support products day to day: developers, QA, and support.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it is
&lt;/h2&gt;

&lt;p&gt;Buoy helps you &lt;strong&gt;see what your app actually did&lt;/strong&gt; — not just what you think it did. The idea is simple: put the right diagnostics and tooling &lt;em&gt;inside&lt;/em&gt; the product experience so you can understand real sessions faster.&lt;/p&gt;

&lt;p&gt;We’re building for teams who care about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Faster debugging when users hit weird states&lt;/li&gt;
&lt;li&gt;Clearer signal for QA and support without a full engineer dig&lt;/li&gt;
&lt;li&gt;Better visibility into performance and behavior on real devices&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Who it’s for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Indie hackers and small teams&lt;/strong&gt; shipping React Native / mobile / web apps&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dev and QA&lt;/strong&gt; who need faster feedback loops&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Support&lt;/strong&gt; who want better context when something goes wrong&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Website: &lt;a href="https://buoy.gg" rel="noopener noreferrer"&gt;https://buoy.gg&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you’re building mobile or web apps and want fewer “works on my machine” mysteries, take a look and tell us what would help most.&lt;/p&gt;

&lt;p&gt;We’re building in public — feedback welcome.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>reactnative</category>
      <category>mobile</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
