<?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: Nikolaj Ivancic</title>
    <description>The latest articles on DEV Community by Nikolaj Ivancic (@adriatic).</description>
    <link>https://dev.to/adriatic</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%2F372573%2F070ae5fa-67b4-4554-9a2d-6874ceb43529.png</url>
      <title>DEV Community: Nikolaj Ivancic</title>
      <link>https://dev.to/adriatic</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adriatic"/>
    <language>en</language>
    <item>
      <title>Developing a Web App with Claude from an iPad (4): Switching from Remote Back to Local</title>
      <dc:creator>Nikolaj Ivancic</dc:creator>
      <pubDate>Thu, 05 Nov 2026 02:00:21 +0000</pubDate>
      <link>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-4-switching-from-remote-back-to-local-4cg</link>
      <guid>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-4-switching-from-remote-back-to-local-4cg</guid>
      <description>&lt;p&gt;While the work was remote, GitHub moved ahead of the Mac. The switch back to local development brings the Mac in step before any work starts on it.&lt;/p&gt;

&lt;p&gt;The third article described the switch to remote development. This article covers the switch back: what has to be brought back, how Claude Code is started in the Terminal, and the six steps of the switch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What has to be brought back
&lt;/h2&gt;

&lt;p&gt;Two things on the Mac are behind:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The local copy of the repository.&lt;/strong&gt; Branches were merged on GitHub, so the main branch on GitHub is newer than the main branch on the Mac.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The reports folder.&lt;/strong&gt; Reports written by remote sessions exist only in the reports repository.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The switch back brings both in step, before any work starts on the Mac.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup on the Mac
&lt;/h2&gt;

&lt;p&gt;Local development uses the Mac like this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Claude Code runs in the &lt;strong&gt;Terminal&lt;/strong&gt; app, started inside the folder that holds the repository.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The reports are saved in a folder on the Mac.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude, in the chat, reads that folder.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Starting Claude Code in the Terminal
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;The &lt;strong&gt;Terminal&lt;/strong&gt; app is opened.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The current folder is changed to the repository folder with &lt;code&gt;cd&lt;/code&gt;, followed by the path of the folder. For example: &lt;code&gt;cd work/&amp;lt;repository-name&amp;gt;&lt;/code&gt;, where the text in angle brackets stands for the name of the repository's folder. If the folder names are not remembered, &lt;code&gt;ls&lt;/code&gt; lists the folders in the current location. Return is pressed after each command.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The prompt is checked. It shows the name of the folder the Terminal is in. That name must be the repository's.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;claude&lt;/code&gt; is typed and Return is pressed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The first time Claude Code runs in a folder, it asks whether to trust the folder. The question shows the folder's path. The path must end with the repository's name. If it shows the home folder or any other folder, the answer is &lt;strong&gt;No&lt;/strong&gt;. Claude Code started in the home folder could see everything in it, and would not find the repository.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A folder that was trusted before is accepted without a question.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The switch back, step by step
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Mac on.&lt;/strong&gt; The Mac is switched on and given a few minutes for iCloud to finish syncing. The drop folder that held files from the iPad is checked in step 6.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;"back on the Mac".&lt;/strong&gt; These words are sent in the chat. Claude lists what waited.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Local housekeeping.&lt;/strong&gt; Claude writes one message for Claude Code. It is a short task with no branch and no pull request. It asks Claude Code to update the local repository from GitHub (switch to the main branch, pull) and report the commit now at the head of main; to copy every report that exists only in the reports repository into the reports folder on the Mac, without overwriting any file, and report the names and sizes; and to delete nothing. The message is pasted into Claude Code in the Terminal. Claude Code writes its own report in the reports folder, and Claude reads it there.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Postponed checks.&lt;/strong&gt; Any live check of Production that needed the Mac, and was postponed during the remote work, is done now.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Branches.&lt;/strong&gt; The developer checks that the finished branches were deleted on GitHub. This was the last step of the remote loop described in the third article. Branches that must be kept, for example one that holds saved work, stay.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Files from the iPad.&lt;/strong&gt; The drop folder in iCloud Drive is opened on the Mac. Files that came from the iPad during the remote work are moved to their place. An empty folder, or old files, need nothing.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What is not done
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Development work with Claude Code is not started on the Mac before the local repository is updated (step 3). Work done on a copy that is behind GitHub leads to two versions of the same file.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Reports are not copied by hand. Claude Code copies them, byte for byte, and checks the copies.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The home folder is never trusted in the Terminal.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;p&gt;Local work can begin when all of these are true:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The local repository is on the main branch, at the same commit as GitHub&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every report from the remote work is in the reports folder on the Mac&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude Code starts in the Terminal inside the repository folder&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The postponed checks were done&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The iCloud drop folder holds nothing that needs moving&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>claude</category>
    </item>
    <item>
      <title>Developing a Web App with Claude from an iPad (3): Switching from Local to Remote</title>
      <dc:creator>Nikolaj Ivancic</dc:creator>
      <pubDate>Thu, 05 Nov 2026 02:00:01 +0000</pubDate>
      <link>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-3-switching-from-local-to-remote-4594</link>
      <guid>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-3-switching-from-local-to-remote-4594</guid>
      <description>&lt;p&gt;The loop stays the same when the work moves to an iPad. Anything left only on the Mac is out of reach. The switch to remote development changes where Claude Code runs and where its records are kept. This article covers the one-time setup, the checks before leaving the Mac, and the loop as it runs from the iPad.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "remote" means
&lt;/h2&gt;

&lt;p&gt;In local development, Claude Code runs in a terminal on the Mac, in a folder that holds the repository. Its reports are saved in a folder on the Mac.&lt;/p&gt;

&lt;p&gt;In remote development, Claude Code runs on the web, in the cloud. It works on a copy of the repository taken from GitHub. Everything it produces goes back to GitHub: branches, pull requests and reports.&lt;/p&gt;

&lt;p&gt;Remote work therefore rests on one rule: &lt;strong&gt;GitHub is the single source of truth.&lt;/strong&gt; Anything that exists only on the Mac is invisible to a remote session.&lt;/p&gt;

&lt;p&gt;The Mac can be shut down at a convenient time or left running. What matters is that nothing is changed in its local copy of the repository while the work is remote. That copy falls behind GitHub. A later article will describe the switch back to local development, which brings it in step again.&lt;/p&gt;

&lt;h2&gt;
  
  
  One-time setup, done at the Mac
&lt;/h2&gt;

&lt;p&gt;This setup is done once, while the Mac is still the working machine.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Create the reports repository.&lt;/strong&gt; It holds the reports that Claude Code writes, in a folder named &lt;code&gt;reports&lt;/code&gt;. In local development, the reports folder on the Mac plays this part.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Connect Claude to the repositories.&lt;/strong&gt; The Claude GitHub App is installed on the code repository and on the reports repository.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Create the cloud environment.&lt;/strong&gt; In Claude Code on the web, an environment is created and given a name. Every remote session starts in it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Write the working rules for cloud sessions into the repository.&lt;/strong&gt; They live in the file &lt;code&gt;CLAUDE.md&lt;/code&gt;, which Claude Code reads at the start of every session. The rules used here are:&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Every cloud task names its branch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every cloud task says whether a report is expected.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Packages are installed with &lt;code&gt;npm ci&lt;/code&gt;, never with &lt;code&gt;npm install&lt;/code&gt;, and &lt;code&gt;package-lock.json&lt;/code&gt; is never changed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude Code never holds the database service key, and never touches the Production database.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Passwords and keys are never typed into the chat or into a prompt. They live in the password manager and in the app's own key settings.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last part of the setup is the &lt;strong&gt;harmless test&lt;/strong&gt;, described below. It is run before the first real task.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before leaving the Mac
&lt;/h2&gt;

&lt;p&gt;A checklist, in this order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;The chat shows no open question.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude Code has nothing running, and every report has been read.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Unfinished local work is saved on GitHub, for example as a branch, so that it also exists away from the Mac.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The sign-in check from the second article passes on the iPad, and the password manager unlocks.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The drop folder opens on the iPad.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In Claude Code on the web, a new session shows the cloud environment with a check mark, and the repository box lists both repositories, each with a check mark.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The words "going remote" are sent in the chat. Claude checks the points above. When it answers, "remote" is sent to confirm the switch. From then on the work is remote, and the local copy on the Mac is left alone.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What changes while the work is remote
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Local (Mac)&lt;/th&gt;
&lt;th&gt;Remote (iPad)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Where Claude Code runs&lt;/td&gt;
&lt;td&gt;Terminal on the Mac&lt;/td&gt;
&lt;td&gt;Claude Code on the web&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where reports are saved&lt;/td&gt;
&lt;td&gt;A folder on the Mac&lt;/td&gt;
&lt;td&gt;The reports repository on GitHub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How Claude learns that a task is done&lt;/td&gt;
&lt;td&gt;Claude reads the report in the folder&lt;/td&gt;
&lt;td&gt;The developer pastes the last line Claude Code wrote into the chat&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who reads the result of a task&lt;/td&gt;
&lt;td&gt;Claude, who says what it means&lt;/td&gt;
&lt;td&gt;The developer, on GitHub&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Branch deletion&lt;/td&gt;
&lt;td&gt;By the developer or Claude Code&lt;/td&gt;
&lt;td&gt;By the developer, on GitHub's website&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Live checks that need the Mac&lt;/td&gt;
&lt;td&gt;Done at once&lt;/td&gt;
&lt;td&gt;Postponed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;While the work is remote, the developer reads the result of each task on GitHub: the pull request page with its checks and preview, and the report when one is expected. The line pasted from Claude Code tells Claude that the task is finished.&lt;/p&gt;

&lt;p&gt;Each remote task also follows the rules in &lt;code&gt;CLAUDE.md&lt;/code&gt;: it names the branch and says whether a report is expected. The prompt is one paragraph, as the second article described.&lt;/p&gt;

&lt;h2&gt;
  
  
  The remote loop
&lt;/h2&gt;

&lt;p&gt;Every task follows the same steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;A message for Claude Code is copied from the chat with its copy icon.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In Claude Code on the web, a &lt;strong&gt;New&lt;/strong&gt; session is started in the cloud environment, with both repositories selected. The message is pasted and sent.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude Code builds on its branch, opens a pull request and waits. It does not merge.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GitHub runs its checks and Vercel builds the preview. The developer reads both on the pull request page.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The developer copies the last line that Claude Code wrote and pastes it into the chat. Claude takes it as the signal that the task is finished, and asks whether the merge is ordered. If it is, Claude gives the developer a second, short message that tells Claude Code to merge. The developer pastes it into Claude Code.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The merge deploys Production automatically. Claude Code reports the commit and the deployment result.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;When a report is expected, it appears in the reports repository.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;At the end of the day, the developer deletes the finished branches on GitHub.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The summary of the suggested steps
&lt;/h2&gt;

&lt;p&gt;The second article described the page in tab 4: the summary of the suggested steps. Claude creates it on request, for example: "Keep one page called Summary of the suggested steps, with only what I must do now, and update the same page each time."&lt;/p&gt;

&lt;p&gt;Claude updates that page in place. The developer opens it in its own Chrome tab and no longer scrolls the chat.&lt;/p&gt;

&lt;h2&gt;
  
  
  The harmless test
&lt;/h2&gt;

&lt;p&gt;Before the first real task, a short sequence confirms that every link in the chain works. The test uses a small text change on a page, so that nothing that matters is at risk:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;A one-line message to Claude Code on the web, to confirm the connection.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A browser test inside the cloud session, to confirm that the cloud environment can run one.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Pushing a harmless branch, to confirm that the cloud session can write to the repository.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A pull request with its checks and preview.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Merging it, and watching Production deploy.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If all five pass, the setup is ready for real work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;p&gt;Remote work can begin when all of these are true:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The GitHub App is installed on both repositories&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The cloud environment exists and shows a check mark in a new session&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The working rules for cloud sessions are in &lt;code&gt;CLAUDE.md&lt;/code&gt; on the main branch&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The harmless test passed, all five parts&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Unfinished local work is saved on GitHub&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;"going remote" and "remote" were exchanged in the chat&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>claude</category>
    </item>
    <item>
      <title>Developing a Web App with Claude from an iPad (2): The Five-Tab Setup</title>
      <dc:creator>Nikolaj Ivancic</dc:creator>
      <pubDate>Thu, 05 Nov 2026 01:59:33 +0000</pubDate>
      <link>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-2-the-five-tab-setup-191c</link>
      <guid>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-2-the-five-tab-setup-191c</guid>
      <description>&lt;p&gt;To run on an iPad, the MacBook workflow has to be arranged for one screen. The first article named the parts of that workflow. This article describes the setup that keeps the same loop running: the tools, a fixed set of Chrome tabs, and a few gestures that replace the mouse.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tools needed
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;iPad:&lt;/strong&gt; a recent model, with iPadOS up to date.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Keyboard case with a trackpad:&lt;/strong&gt; the Logitech Combo Touch. Any keyboard case with a trackpad should work, but only this one was tested.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Browser:&lt;/strong&gt; Chrome for iPad. All the web tools below run in it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Claude&lt;/strong&gt;, with &lt;strong&gt;Claude Code on the web&lt;/strong&gt; (claude.ai/code).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; an account and a repository for the app.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Vercel:&lt;/strong&gt; hosting and preview deployments, connected to the GitHub repository.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Supabase:&lt;/strong&gt; the database, for apps that need one.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Bitwarden:&lt;/strong&gt; the password manager. It must unlock on the iPad. Keys and passwords are kept only there.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;iCloud Drive and the Files app:&lt;/strong&gt; only when files move between the iPad and a Mac.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The single-screen problem
&lt;/h2&gt;

&lt;p&gt;An iPad normally shows one app at a time. On a MacBook, the chat, Claude Code and GitHub sit in separate windows. On the iPad, a day of work becomes a day of scrolling the chat to find instructions, unless the work is planned around one screen.&lt;/p&gt;

&lt;p&gt;The remedy is a fixed set of Chrome tabs, opened at the start of each session, in this order, and left open:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The app:&lt;/strong&gt; the live site, to look at what has been built&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The chat with Claude&lt;/strong&gt; (claude.ai): planning, review and approval&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Claude Code&lt;/strong&gt; (claude.ai/code): the building&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Summary of the suggested steps:&lt;/strong&gt; one browser page that always holds only what must be done now. Claude publishes it as a separate page, with its own address, and updates that page in place, so nothing has to be found by scrolling. It is opened in its own tab, from the link in the chat&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; the repository, with its pull requests and branches pages&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Switching is done with the tab bar. Instructions are read in tab 4 rather than found by scrolling through tab 2.&lt;/p&gt;

&lt;h2&gt;
  
  
  Entering development mode
&lt;/h2&gt;

&lt;p&gt;An iPad is also a media device, so Chrome may hold other tabs, or none of the five. The five tabs are therefore opened again each time development starts, from a launcher.&lt;/p&gt;

&lt;p&gt;The launcher is a page that Claude publishes, in the same way as the summary of the suggested steps. It has five large buttons, one for each tab, in the order above. Each button is a plain link that opens in its own tab. Chrome switches to the new tab after each tap, so the launcher tab must be selected again before the next tap. The launcher stays open as a sixth tab. The page is bookmarked in Chrome, so it is one tap away. The five addresses are given to Claude once, and Claude builds the page.&lt;/p&gt;

&lt;p&gt;To start development mode:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Close the tabs left from the earlier session, so that no tab is opened twice.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Open the launcher from the bookmark.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Tap the five buttons in order, once each, returning to the launcher tab after each tap.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Sign-in check
&lt;/h2&gt;

&lt;p&gt;Open each service once, each in its own tab: claude.ai, GitHub, Supabase and Vercel. Check that each opens without asking for anything. Then unlock Bitwarden. Any sign-in request is dealt with now, not in the middle of a task.&lt;/p&gt;

&lt;h2&gt;
  
  
  Gestures
&lt;/h2&gt;

&lt;p&gt;These gestures were confirmed on an iPad with the keyboard case attached. Other iPads may differ.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Copy a block of text or a prompt:&lt;/strong&gt; tap the copy icon on the block. This is better than selecting text, which is hard to do precisely with a finger.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Select part of a text and copy it:&lt;/strong&gt; the trackpad and the screen are used together. Move to the starting point of the selection with the arrow keys, click the trackpad, and touch the screen once to bring up the selection controls. Drag the selection rectangle over the wanted text, then touch the screen again to bring up the copy prompt. This works in typing boxes and in page text that can be selected.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Paste:&lt;/strong&gt; touch the typing box once with a finger, then tap &lt;strong&gt;Paste&lt;/strong&gt;. Cmd+V on the keyboard also works.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Send:&lt;/strong&gt; the return key sends. A prompt with several lines is cut at the first line break, so prompts for Claude Code are written as one paragraph.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Screenshot:&lt;/strong&gt; press the volume-up button and the power button together. The keyboard case has a screenshot key (in the row above the numbers, above the 5) that does the same.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Attach a screenshot or photo to the chat:&lt;/strong&gt; the plus or paperclip next to the typing box.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Files app
&lt;/h2&gt;

&lt;p&gt;When files move between the iPad and a Mac, one folder in iCloud Drive serves as the drop point, with a subfolder for incoming files.&lt;/p&gt;

&lt;p&gt;Exporting a file from the app opens the iPad's share sheet. Tapping &lt;strong&gt;Save to Files&lt;/strong&gt; opens the Files chooser. There, iCloud Drive is selected, then the drop folder, then its subfolder for incoming files. Finally, &lt;strong&gt;Save&lt;/strong&gt; is tapped. The folder must open in the Files app without asking for anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Known weak points
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Selecting text still needs the screen.&lt;/strong&gt; The trackpad and the arrow keys place the starting point, but the selection controls appear only after a touch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The shortcuts bar can cover the typing box.&lt;/strong&gt; With a keyboard case attached, iPadOS shows a bar with formatting buttons and a microphone at the bottom of the screen. In the chat, it can sit over the typing box. It is hidden in Settings, under General, then Keyboard, with the &lt;strong&gt;Shortcuts&lt;/strong&gt; switch.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;p&gt;The setup is complete when all of these are true:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The launcher page opens the five tabs, and each opens signed in&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The five tabs are open and switching between them works&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every service opens without asking for a sign-in&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Bitwarden unlocks&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A block can be copied with its copy icon and pasted into another tab&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A part of a text can be selected with the trackpad and a touch, and copied&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A screenshot can be taken and attached in the chat&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The typing box in the chat is not covered by the shortcuts bar&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The iCloud Drive drop folder opens in the Files app&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>claude</category>
    </item>
    <item>
      <title>Developing a Web App with Claude from an iPad (1): The MacBook Workflow</title>
      <dc:creator>Nikolaj Ivancic</dc:creator>
      <pubDate>Thu, 05 Nov 2026 01:57:43 +0000</pubDate>
      <link>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-1-the-macbook-workflow-lj3</link>
      <guid>https://dev.to/adriatic/developing-a-web-app-with-claude-from-an-ipad-1-the-macbook-workflow-lj3</guid>
      <description>&lt;h2&gt;
  
  
  What this series is about
&lt;/h2&gt;

&lt;p&gt;The MacBook is not available. Can the development of a web app with Claude continue from an iPad?&lt;/p&gt;

&lt;p&gt;This series answers that question. It does not argue that an iPad should replace an everyday machine. It describes how the work can continue during a trip, a meeting lasting several days, or a visit.&lt;/p&gt;

&lt;p&gt;Developers on MacBook, Windows and Linux machines develop web apps with the help of Claude. The developer talks to Claude in a chat, runs Claude Code in a terminal, and watches a hosting service build the result.&lt;/p&gt;

&lt;p&gt;The series starts with the MacBook workflow, then shows how the same work is done from an iPad. Windows and Linux may be covered in later articles.&lt;/p&gt;

&lt;p&gt;This first article gives an overview of the MacBook workflow and names its parts. Later articles use these names so that each detail, such as the setup of a browser on an iPad, can be traced to its place in the workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three roles
&lt;/h2&gt;

&lt;p&gt;The work is shared between three roles. These roles are an anchor of the series: later articles refer back to them.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The developer decides.&lt;/strong&gt; The developer approves every plan, every change and every merge, and is the only person who touches keys and passwords.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Claude&lt;/strong&gt;, in the chat, &lt;strong&gt;plans and reviews.&lt;/strong&gt; Claude writes the specification of each task, reads each report, and tells the developer what is waiting.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Claude Code builds and checks.&lt;/strong&gt; It writes the code, runs the tests, opens the pull request, and writes the report.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are responsibilities assigned in this workflow, not limits of the tools. Claude Code can make many decisions about code, but it does not decide what is built or merged. Claude explains what the reports mean, and the developer remains responsible for every approval.&lt;/p&gt;

&lt;p&gt;The aim is that the developer can follow progress without reading every line of code. Reports and explanations support that judgment. They do not guarantee that a change is correct.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parts of the workflow
&lt;/h2&gt;

&lt;p&gt;These are the anchors. Each has one meaning throughout the series.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Planning and coordination&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Chat:&lt;/strong&gt; the conversation with Claude (claude.ai).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Task:&lt;/strong&gt; one numbered unit of work.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Specification:&lt;/strong&gt; the written description of a task, produced by Claude and approved by the developer.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Summary of the suggested steps:&lt;/strong&gt; one browser page, kept by Claude, with only the steps the developer must do now.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Implementation and review&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Claude Code:&lt;/strong&gt; the tool that builds. On the MacBook it runs in the Terminal app, inside the repository folder.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Repository:&lt;/strong&gt; the home of the app's code and its history on GitHub.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Branch:&lt;/strong&gt; the place where Claude Code builds a task, away from the main branch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Pull request:&lt;/strong&gt; a proposal to merge a branch into the main branch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Checks:&lt;/strong&gt; the automatic tests that GitHub runs on a pull request.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Preview:&lt;/strong&gt; a temporary copy of the app, built from the pull request by the hosting service, where the change can be looked at before it is merged.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Report:&lt;/strong&gt; the summary Claude Code writes after each task. On the MacBook it is saved in a reports folder, where Claude reads it.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Release&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Merge:&lt;/strong&gt; the step that adds the branch to the main branch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Production:&lt;/strong&gt; the live app. It is deployed automatically when a merge reaches the main branch.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The loop
&lt;/h2&gt;

&lt;p&gt;Every task, large or small, follows the same ten steps.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;The developer tells Claude what is wanted, in plain words.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude writes the specification and the developer approves it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude gives the developer one short message for Claude Code.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The developer pastes the message into Claude Code.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude Code builds on a branch, runs the tests, and opens a pull request. It does not merge.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GitHub runs the checks and the hosting service builds the preview. The developer looks at both.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude reads Claude Code's report and the result of the checks, and says whether the task is ready.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The developer approves, and a second short message tells Claude Code to merge.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Claude Code merges, which deploys Production, and reports the result.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The developer deletes the finished branch.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Only one task is in the loop at a time. The next one starts when the current one is done.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rules that keep it safe
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Keep secrets out of prompts.&lt;/strong&gt; Keys and passwords never go into the chat or into a message to Claude Code. They live in a password manager and in the app's own key settings.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Keep production database access with the developer.&lt;/strong&gt; Claude Code never holds the database's service key, and never touches the Production database. When a database change is needed, Claude reviews it and the developer runs it by hand.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Require approval before merging.&lt;/strong&gt; Nothing is merged without the developer's word.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Review every report.&lt;/strong&gt; Every report is read by Claude, and what the developer must do is stated in plain steps.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These rules depend on how permissions and settings are configured, not only on instructions given to the tools. The later articles cover that configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the MacBook is not available
&lt;/h2&gt;

&lt;p&gt;On an iPad, the loop stays the same. What changes is where the work runs and where its records are kept.&lt;/p&gt;

&lt;p&gt;Claude Code runs in the browser, in a remote environment, instead of in the Terminal. The reports are written to a repository instead of to a folder on the MacBook. The code and the reports are kept on GitHub. Secrets stay in their secure settings and never go into the repository.&lt;/p&gt;

&lt;p&gt;The later articles describe the iPad setup, the switch from the MacBook to the iPad, and the switch back, step by step. They end with a complete sample app built from an iPad. The detailed steps come after the workflow and its parts are familiar.&lt;/p&gt;

&lt;p&gt;An iPad is usually also a media device. The setup therefore treats the iPad as having two modes, media and development. It gives a way to enter development mode each time, without assuming that the browser has kept its tabs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What comes next
&lt;/h2&gt;

&lt;p&gt;Would this be useful when the primary development machine is not available? Which part should the next article cover? The comments decide whether the series continues.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>claude</category>
    </item>
    <item>
      <title>Nvidia free AI course - what about MacOS?</title>
      <dc:creator>Nikolaj Ivancic</dc:creator>
      <pubDate>Sat, 30 Mar 2024 16:45:35 +0000</pubDate>
      <link>https://dev.to/adriatic/nvidia-free-ai-course-what-about-macos-2hgn</link>
      <guid>https://dev.to/adriatic/nvidia-free-ai-course-what-about-macos-2hgn</guid>
      <description>&lt;p&gt;After spending most of my time as a developer on Windows platform, I was advised to have a look at a Mac as the development platform. This happened some 10 years ago and I converted to MacOS completely.&lt;/p&gt;

&lt;p&gt;Now, discovering Nvidia AI course, I am wondering how to use it without having to use Windows again (maybe Linux??). &lt;/p&gt;

&lt;p&gt;Can someone explain to me why does Nvidia ignore MacOS?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>rag</category>
      <category>macos</category>
      <category>windows</category>
    </item>
    <item>
      <title>Is anyone worried about Gatsby vulnerabilities?</title>
      <dc:creator>Nikolaj Ivancic</dc:creator>
      <pubDate>Tue, 22 Jun 2021 19:31:38 +0000</pubDate>
      <link>https://dev.to/adriatic/is-anyone-worried-about-gatsby-vulnerabilities-2635</link>
      <guid>https://dev.to/adriatic/is-anyone-worried-about-gatsby-vulnerabilities-2635</guid>
      <description>&lt;p&gt;I understand that Gatsby is not the offender here and even more nobody owns this issue, so why does it seem to me that I am the only one constantly concerned about this?&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;gatsby cd gatsby-starter-blog 
gatsby-starter-blog git:(master) npm install

up to date, audited 2324 packages in 5s

41 vulnerabilities (10 moderate, 31 high)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>help</category>
    </item>
  </channel>
</rss>
