<?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: inuken</title>
    <description>The latest articles on DEV Community by inuken (@inuken).</description>
    <link>https://dev.to/inuken</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%2F4235012%2Fae3f1ee4-30ca-4adc-88e8-583d538cb54a.jpeg</url>
      <title>DEV Community: inuken</title>
      <link>https://dev.to/inuken</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/inuken"/>
    <language>en</language>
    <item>
      <title>I'm not a programmer. I built and launched an app from my iPhone with Claude Code.</title>
      <dc:creator>inuken</dc:creator>
      <pubDate>Mon, 09 Nov 2026 11:39:52 +0000</pubDate>
      <link>https://dev.to/inuken/im-not-a-programmer-i-built-and-launched-an-app-from-my-iphone-with-claude-code-59mb</link>
      <guid>https://dev.to/inuken/im-not-a-programmer-i-built-and-launched-an-app-from-my-iphone-with-claude-code-59mb</guid>
      <description>&lt;p&gt;I'm an office worker in Japan. I've never learned to program, and I don't have time to start now.&lt;/p&gt;

&lt;p&gt;But I wanted something simple: a list of every shochu I drink, like a collection. (Shochu is a traditional Japanese distilled spirit.)&lt;/p&gt;

&lt;p&gt;So in late August 2026, I opened Claude Code for the first time. Four weeks later, my friends were using my app. I spent about an hour a day on it, and did almost all of the work on my iPhone.&lt;/p&gt;

&lt;p&gt;I didn't write a single line of code myself. Here's what actually made it work, and two things you can try today.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;A personal shochu notebook that runs in Safari and sits on my home screen like an app:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Log each bottle with a photo, and look back on a calendar&lt;/li&gt;
&lt;li&gt;Browse 300 shochu distilleries across Japan on a map&lt;/li&gt;
&lt;li&gt;Keep a wish list&lt;/li&gt;
&lt;li&gt;Share records with friends I invite&lt;/li&gt;
&lt;/ul&gt;

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

&lt;ul&gt;
&lt;li&gt;iPhone: the one I already had&lt;/li&gt;
&lt;li&gt;Claude, paid plan: $20/month (plus tax in some countries)&lt;/li&gt;
&lt;li&gt;GitHub (where the project is stored): free&lt;/li&gt;
&lt;li&gt;Vercel (puts the app on the internet): free plan&lt;/li&gt;
&lt;li&gt;Supabase (sign-in and saving data): free plan&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Apart from the AI subscription, it has cost me $0 so far.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem nobody warned me about
&lt;/h2&gt;

&lt;p&gt;The most important thing turned out not to be programming knowledge.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The AI forgets everything when you start a new conversation.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At first, I explained my app from scratch every single time: "This is an app for logging shochu…" And every time, I got something slightly different. Things I'd fixed the day before came back broken.&lt;/p&gt;

&lt;p&gt;What changed everything was two small files that Claude Code reads every time:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A rules file (CLAUDE.md).&lt;/strong&gt; Things I want it to follow every time, like "Don't use technical jargon" and "Always ask me before publishing."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Progress notes (PROGRESS.md).&lt;/strong&gt; "What's done" and "What's next." The AI updates this itself after each piece of work.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Now I open a new conversation on my iPhone, say "Read PROGRESS.md and continue," and I'm right back where I left off.&lt;/p&gt;

&lt;p&gt;My rules file grew one line at a time, every time something went wrong. It's in Japanese, and Claude Code follows it just fine. You can write yours in whatever language you think in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try this today #1: don't say "build it"
&lt;/h2&gt;

&lt;p&gt;My biggest early mistake was asking the AI to just build the app. It fills in everything you didn't say, and you get something different from what you pictured.&lt;/p&gt;

&lt;p&gt;Instead, I ask it to ask &lt;em&gt;me&lt;/em&gt; first. The key parts of my first message look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I want to build an app just for me. I have no programming experience.

■ Must-haves (3 at most)
1. ...
2. ...
3. ...

■ Please
- Before you start building, ask me what we need to decide. Give me numbered choices, all in one message.
- Don't use anything that costs money. Choose free services.
- Start by building just the screens, and show me.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three things matter here:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Three must-haves, no more.&lt;/strong&gt; List ten, and all ten end up half-done. My app started with just "log a bottle" and "see it on a calendar."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Questions as numbered choices.&lt;/strong&gt; As a beginner, I can't answer "What would you like to do?" But I can reply "1."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Screens first.&lt;/strong&gt; One look at a screen and you instantly know "No, not like that."&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try this today #2: one screenshot, three lines
&lt;/h2&gt;

&lt;p&gt;When something looks wrong, I send one screenshot and three lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;- Which screen:
- What's happening:
- What I want instead:
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Real example: my own photos were showing up blurred in my records list. I sent a screenshot with "Which screen: the records list / What's happening: my own photos are blurred / What I want instead: show the whole photo without blurring." That got it fixed.&lt;/p&gt;

&lt;p&gt;The third line is the important one. If you only say "this looks wrong," the AI decides how to fix it, and that's often another round.&lt;/p&gt;

&lt;p&gt;And when a friend tells you something is hard to use, pass on their exact words. A friend told me "the dots on the map are hard to tap." I sent that sentence as-is, and it was fixed and live the same day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where I still needed a computer
&lt;/h2&gt;

&lt;p&gt;To be honest: one kind of task didn't work on my iPhone. Some database settings need you to paste a long piece of text into a web dashboard, and that wouldn't paste properly in Safari. I open my laptop only on the days I do that kind of setup.&lt;/p&gt;

&lt;p&gt;Everything else, I do from my phone.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you want to start
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; how I use a second AI to check everything before I publish, with a prompt and a copy-and-paste template → &lt;a href="https://inuken.gumroad.com/l/checker" rel="noopener noreferrer"&gt;https://inuken.gumroad.com/l/checker&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;$7:&lt;/strong&gt; my full guide. Setup on an iPhone tap by tap, both file templates, free publishing, every place I got stuck, and a real example of adding a feature → &lt;a href="https://inuken.gumroad.com/l/iphone-claude-code" rel="noopener noreferrer"&gt;https://inuken.gumroad.com/l/iphone-claude-code&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you try it and get stuck, send me a message on X: @inuken_code. I mostly post in Japanese, but English is fine.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I wrote this in Japanese and translated it into English with help from Claude.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>nocode</category>
      <category>beginners</category>
      <category>ios</category>
    </item>
  </channel>
</rss>
