<?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: Mateo AI</title>
    <description>The latest articles on DEV Community by Mateo AI (@mateohq).</description>
    <link>https://dev.to/mateohq</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%2F4255311%2F8ca028f4-0582-459d-b278-1325615b1f13.png</url>
      <title>DEV Community: Mateo AI</title>
      <link>https://dev.to/mateohq</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mateohq"/>
    <language>en</language>
    <item>
      <title>Why Cloud Browser Agents Keep Hitting Walls on Everyday Tasks (And Why We Moved On-Device on Android)</title>
      <dc:creator>Mateo AI</dc:creator>
      <pubDate>Fri, 20 Nov 2026 10:31:11 +0000</pubDate>
      <link>https://dev.to/mateohq/why-cloud-browser-agents-keep-hitting-walls-on-everyday-tasks-and-why-we-moved-on-device-on-417l</link>
      <guid>https://dev.to/mateohq/why-cloud-browser-agents-keep-hitting-walls-on-everyday-tasks-and-why-we-moved-on-device-on-417l</guid>
      <description>&lt;p&gt;Most "personal AI agents" today still get stuck in the same two dead ends.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Dead end #1: API-only connectors.&lt;/strong&gt; They work great when a service offers a clean integration. The problem is that 90% of annoying everyday errands—canceling a buried subscription, starting a return, booking a table, ordering dinner—live inside consumer apps that will never expose an AI API for that flow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Dead end #2: Cloud browser bots.&lt;/strong&gt; Spinning up a remote server browser sounds clean until you try to touch real accounts. You immediately run into login friction, anti-bot walls, and the bigger reality: half the services people actually use live inside mobile-only Android apps, not desktop web forms.&lt;/p&gt;

&lt;p&gt;And early on-device phone agents had a different usability flaw: &lt;strong&gt;they hijack your foreground screen&lt;/strong&gt;. Watching an agent slowly tap through your phone for two minutes while you can't even reply to a text doesn't feel like delegation—it feels like babysitting.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we built instead
&lt;/h2&gt;

&lt;p&gt;We're building &lt;strong&gt;Mateo&lt;/strong&gt;, a personal AI agent on Android that runs real apps on your own phone inside an isolated background &lt;code&gt;VirtualDisplay&lt;/code&gt;—so your phone stays free while the task finishes quietly in the corner.&lt;/p&gt;

&lt;p&gt;Here is a 4-frame capture from an uncut Android device run (foreground Chrome stays completely usable while Mateo handles a restaurant lookup in the top-right corner):&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgn6oy3l6sn2h90o82ypj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgn6oy3l6sn2h90o82ypj.png" alt="Mateo uncut Android background execution" width="800" height="336"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Three engineering trade-offs we had to be honest about
&lt;/h2&gt;

&lt;p&gt;If you've ever built Android automation, you know the edge cases matter more than the demo. Here is where our architecture draws clear lines:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;On-device sessions, not cloud cookie shipping.&lt;/strong&gt; Because Mateo executes directly inside the apps you're already signed into on your own phone, we don't export your cookies into a remote server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single-instance per app package.&lt;/strong&gt; Mateo can run tasks across distinct apps, but we don't try to force simultaneous multi-instance execution of the exact same Android app package.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Respecting &lt;code&gt;FLAG_SECURE&lt;/code&gt; and system boundaries.&lt;/strong&gt; Android intentionally blocks virtual screen capture on DRM and sensitive protected surfaces (&lt;code&gt;FLAG_SECURE&lt;/code&gt;). We don't try to bypass Android's security model—Mateo focuses on everyday multi-step tasks that can complete cleanly within system rules.&lt;/li&gt;
&lt;/ol&gt;

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

&lt;p&gt;You can grab the Android app via Google Play from &lt;strong&gt;&lt;a href="https://mateohq.com/phone-use" rel="noopener noreferrer"&gt;mateohq.com/phone-use&lt;/a&gt;&lt;/strong&gt; (once installed, the app walks you into enabling the background phone-use Beta build; Web/iMessage entry is also available there for non-Android flows).&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Curious where other builders here land on two things:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;If an agent runs quietly on your phone without taking over your screen, what is the first repetitive multi-step errand you'd actually hand off to it?&lt;/li&gt;
&lt;li&gt;For Android devs who have worked with &lt;code&gt;VirtualDisplay&lt;/code&gt; in production—which OEM skins (One UI, HyperOS, ColorOS) gave you the weirdest lifecycle or input quirks? Would love to compare notes in the comments.&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>discuss</category>
      <category>ai</category>
      <category>android</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
