<?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: vikram shetty</title>
    <description>The latest articles on DEV Community by vikram shetty (@vikram_shetty_902028700f7).</description>
    <link>https://dev.to/vikram_shetty_902028700f7</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%2F4176488%2F9f390435-8975-4b63-9260-233446caf0af.jpg</url>
      <title>DEV Community: vikram shetty</title>
      <link>https://dev.to/vikram_shetty_902028700f7</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vikram_shetty_902028700f7"/>
    <language>en</language>
    <item>
      <title>I Used an AI Assistant on My Phone as a Dev Tool for a Month. Here's the Honest Verdict.</title>
      <dc:creator>vikram shetty</dc:creator>
      <pubDate>Sun, 11 Oct 2026 06:55:12 +0000</pubDate>
      <link>https://dev.to/vikram_shetty_902028700f7/i-used-an-ai-assistant-on-my-phone-as-a-dev-tool-for-a-month-heres-the-honest-verdict-4pad</link>
      <guid>https://dev.to/vikram_shetty_902028700f7/i-used-an-ai-assistant-on-my-phone-as-a-dev-tool-for-a-month-heres-the-honest-verdict-4pad</guid>
      <description>&lt;p&gt;I've been coding for long enough to remember when "mobile development environment" meant SSH-ing into a server from a phone with a keyboard the size of a postage stamp. So when AI assistants started shipping proper phone apps, I was sceptical. I tried using one as my main "away from desk" dev tool for a month.&lt;/p&gt;

&lt;p&gt;Here's what actually worked, what didn't, and where I think this is heading.&lt;/p&gt;

&lt;h2&gt;
  
  
  What worked
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Rubber-ducking on the go.&lt;/strong&gt; Nine times out of ten, the bug I'm stuck on isn't a typing problem. It's a thinking problem. Explaining it out loud to an assistant on a walk solved more issues than I'd like to admit. The duck has finally learned to talk back.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reading unfamiliar code.&lt;/strong&gt; Pasting a gnarly function and asking "what does this actually do, step by step" is genuinely useful on a small screen. You don't need an IDE to understand something.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Drafting tickets and PR descriptions.&lt;/strong&gt; I'd dictate the rough idea, get a clean draft back, and tidy it later at my desk. Saved me maybe 20 minutes a day.&lt;/p&gt;

&lt;h2&gt;
  
  
  What didn't
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Writing real code.&lt;/strong&gt; Anything longer than ~30 lines on a phone is still miserable, AI or not. Reviewing a diff on a 6-inch screen is how bugs get shipped.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Context.&lt;/strong&gt; The assistant doesn't know your codebase unless you feed it. On mobile, feeding it is the hard part.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Trust.&lt;/strong&gt; It's confidently wrong sometimes. Rule of thumb: never merge anything you couldn't explain to a colleague.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it's heading
&lt;/h2&gt;

&lt;p&gt;The interesting shift isn't chat. It's agents that can take actions on your phone, not just answer questions. I read a decent non-hype breakdown of &lt;a href="https://genzhunt.in/claude-ai-agent-phone-just-changed-everything-here-s-why" rel="noopener noreferrer"&gt;what a Claude AI agent on a phone could actually change&lt;/a&gt;, and it matches what I saw: useful for small, well-defined tasks, not a replacement for sitting down and building.&lt;/p&gt;

&lt;p&gt;There's also a good plain-English piece on &lt;a href="https://genzhunt.in/claude-app-for-mobile-just-changed-ai-access-forever" rel="noopener noreferrer"&gt;how the Claude mobile app changes everyday AI access&lt;/a&gt; if you want the non-developer angle to send to a manager who keeps asking "should we be using this?"&lt;/p&gt;

&lt;h2&gt;
  
  
  My setup now
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Phone:&lt;/strong&gt; thinking, reading code, drafting text.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Laptop:&lt;/strong&gt; anything that touches a real repo.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rule:&lt;/strong&gt; if I catch myself writing a for-loop on my phone, I put the phone down and go for the walk I was supposed to be on.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Curious how others use AI on mobile. Is it part of your workflow, or still a novelty?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I keep up with this stuff mostly through plain-English explainers on &lt;a href="https://genzhunt.in/" rel="noopener noreferrer"&gt;GenzHunt&lt;/a&gt;, which covers trending tech without the launch-day hype.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>mobile</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
