<?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: Kirill Lukyanov</title>
    <description>The latest articles on DEV Community by Kirill Lukyanov (@klukyanov).</description>
    <link>https://dev.to/klukyanov</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%2F4092798%2F719db81c-244e-4965-a433-0662ed094a53.png</url>
      <title>DEV Community: Kirill Lukyanov</title>
      <link>https://dev.to/klukyanov</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/klukyanov"/>
    <language>en</language>
    <item>
      <title>How to build a Garmin watch app: our Clay Sniper story and a Connect IQ tutorial</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Thu, 12 Nov 2026 08:22:35 +0000</pubDate>
      <link>https://dev.to/klukyanov/how-to-build-a-garmin-watch-app-our-clay-sniper-story-and-a-connect-iq-tutorial-46ke</link>
      <guid>https://dev.to/klukyanov/how-to-build-a-garmin-watch-app-our-clay-sniper-story-and-a-connect-iq-tutorial-46ke</guid>
      <description>&lt;p&gt;Garmin has its own programming language, its own toolchain and its own app store, and most tutorials about it are either years old or stop at "hello world". We just shipped Clay Sniper for Garmin watches, a training app for clay shooters, and went from the first commit to a store submission in two days. Here is how it is built, and a practical walkthrough for building your own Connect IQ app.&lt;/p&gt;

&lt;p&gt;This is part 1 of a series. Part 2 will be about watch faces.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;Garmin apps are written in &lt;strong&gt;Monkey C&lt;/strong&gt; with the free &lt;strong&gt;Connect IQ SDK&lt;/strong&gt;. The easiest editor is &lt;strong&gt;VS Code with Garmin's official Monkey C extension&lt;/strong&gt;. You test in the bundled simulator, sideload a &lt;code&gt;.prg&lt;/code&gt; file to your own watch over USB, and publish a signed &lt;code&gt;.iq&lt;/code&gt; package through Garmin's web portal. If you know Java, JavaScript or Swift, your first app will run in the simulator in an evening. The hard parts come later: dozens of watch models with different screens and sensors, and a manual publishing process with no API.&lt;/p&gt;

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

&lt;p&gt;&lt;a href="https://apps.apple.com/app/clay-sniper/id6774298651" rel="noopener noreferrer"&gt;Clay Sniper&lt;/a&gt; is an iPhone journal for clay shooting (sporting, trap, skeet). It has always had an Apple Watch app: you stand on the station and tap hit or miss after every target. Many shooters wear Garmin, so we ported the same logic.&lt;/p&gt;

&lt;p&gt;The Garmin version:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Buttons, not taps.&lt;/strong&gt; UP is a hit, DOWN is a miss, BACK undoes the last shot. A single vibration confirms a hit, a double one a miss, so you never look at the screen with a gun in your hands.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Series and disciplines.&lt;/strong&gt; Official programs including 5-Stand; the watch shows the next station and target type, and closes the series on the last target.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Heart rate&lt;/strong&gt;, split into "during series" and "between series".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Garmin Connect activity.&lt;/strong&gt; The workout is saved as a regular "Shooting" activity with custom FIT fields: hits, misses, hit rate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sync to iPhone&lt;/strong&gt;, where the full stats live.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Competition mode.&lt;/strong&gt; The phone sends today's competitions and station schedule to the watch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The first commit was on October 13, version 1.0.0 went to the Connect IQ Store on October 15. Version 1.1.0 is &lt;a href="https://apps.garmin.com/apps/4f1c3354-0706-4216-abb4-0b32ffcaf80f" rel="noopener noreferrer"&gt;live in the store&lt;/a&gt;, 1.2.0 is in review.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it is built
&lt;/h2&gt;

&lt;p&gt;About 2,000 lines of Monkey C in 12 files, ~400 of them tests. Three layers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Core.&lt;/strong&gt; Workout state, a list of actions (hit, miss, undo, pause, heart rate) and a reducer. This is the same Flux pattern as our iOS apps and the same rules as the Apple Watch version. The reducer knows nothing about the screen or sensors, so it is trivial to test.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Store.&lt;/strong&gt; The only place where state changes, and where side effects live: &lt;code&gt;ActivityRecording&lt;/code&gt;, custom FIT fields via &lt;code&gt;FitContributor&lt;/code&gt;, vibration, settings in &lt;code&gt;Application.Storage&lt;/code&gt;, the outbox for the phone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Views.&lt;/strong&gt; &lt;code&gt;Menu2&lt;/code&gt; settings, the shot screen, a controls menu and a summary. Views only draw state and turn button presses into actions.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One difference from Swift: Monkey C has no cheap value copies and the app has tens of kilobytes of memory, so the reducer mutates state in place instead of returning a new copy. "State changes only through &lt;code&gt;dispatch&lt;/code&gt;" still holds.&lt;/p&gt;

&lt;h3&gt;
  
  
  Watch to iPhone
&lt;/h3&gt;

&lt;p&gt;There is no direct channel between your watch app and your phone app. Messages go through the Garmin Connect app. On the watch you use &lt;code&gt;Communications&lt;/code&gt;, on iOS the Connect IQ Mobile SDK (we added it via Swift Package Manager).&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The user taps "Connect watch" once, picks the watch in Garmin Connect, and is sent back to our app via a URL scheme.&lt;/li&gt;
&lt;li&gt;After a workout the watch puts it in a persistent outbox and sends it in parts via &lt;code&gt;Communications.transmit&lt;/code&gt;. An hour of heart rate is hundreds of samples, so it is chunked 100 pairs per part.&lt;/li&gt;
&lt;li&gt;The phone reassembles the parts, saves the workout and replies with an ack. Only then does the watch drop it from the outbox.&lt;/li&gt;
&lt;li&gt;No phone nearby? The workout waits and is resent on the next app start or when the phone asks for a sync.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Messages are plain dictionaries with short keys, versioned, and new fields are always optional, so an older phone app still accepts workouts from a newer watch app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Connect IQ app types
&lt;/h2&gt;

&lt;p&gt;Pick the type first. It is declared in the manifest and decides what your code is allowed to do.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Manifest&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Watch face&lt;/td&gt;
&lt;td&gt;&lt;code&gt;watchface&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;the main screen, always visible; no button input, updates once a minute in low-power mode&lt;/td&gt;
&lt;td&gt;Clay Sniper Range (part 2)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Device app&lt;/td&gt;
&lt;td&gt;&lt;code&gt;watch-app&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;launched from the activity list, full screen, buttons and sensors, records its own activity&lt;/td&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data field&lt;/td&gt;
&lt;td&gt;&lt;code&gt;datafield&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;one cell on a built-in activity screen (run, bike)&lt;/td&gt;
&lt;td&gt;custom power or pace&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Widget&lt;/td&gt;
&lt;td&gt;&lt;code&gt;widget&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;a quick summary scrolled from the watch face; shown as a glance on newer watches&lt;/td&gt;
&lt;td&gt;weather, calendar&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Music&lt;/td&gt;
&lt;td&gt;&lt;code&gt;audio-content-provider&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;syncs tracks from a streaming service&lt;/td&gt;
&lt;td&gt;music apps&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If all you need is one number during a run, build a data field. We needed buttons, the HR sensor and activity recording, so &lt;code&gt;watch-app&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;p&gt;Everything is free: no developer fee, no paid SDK. Works on macOS, Windows and Linux.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A Garmin account&lt;/strong&gt; for the SDK Manager and the developer portal (apps-developer.garmin.com).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Connect IQ SDK Manager&lt;/strong&gt; from developer.garmin.com/connect-iq (on a Mac also &lt;code&gt;brew install --cask connectiq-sdk-manager&lt;/code&gt;). Pick an SDK version and download device definitions: the compiler cannot build for a model it has no definition for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;VS Code + the Monkey C extension&lt;/strong&gt;: highlighting, completion, project templates, simulator and debugger.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A developer key.&lt;/strong&gt; Every build is signed with it, and updates in the store must be signed with the same key. Don't lose it.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;openssl genrsa -out developer_key.pem 4096
openssl pkcs8 -topk8 -inform PEM -outform DER \
  -in developer_key.pem -out developer_key.der -nocrypt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or run "Monkey C: Generate a Developer Key" in VS Code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Monkey C in five minutes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Types are optional, turn them on.&lt;/strong&gt; Build with strict type checking (&lt;code&gt;-l 3&lt;/code&gt;): errors that would otherwise crash on the watch are caught at compile time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The API lives in &lt;code&gt;Toybox&lt;/code&gt;&lt;/strong&gt;: &lt;code&gt;WatchUi&lt;/code&gt;, &lt;code&gt;Graphics&lt;/code&gt;, &lt;code&gt;Sensor&lt;/code&gt;, &lt;code&gt;Position&lt;/code&gt;, &lt;code&gt;ActivityRecording&lt;/code&gt;, &lt;code&gt;Communications&lt;/code&gt;, &lt;code&gt;Application.Storage&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check capabilities with &lt;code&gt;has&lt;/code&gt;.&lt;/strong&gt; &lt;code&gt;if (info has :meanSeaLevelPressure)&lt;/code&gt;. The API surface depends on the model, and this is the number one source of crashes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory is tens of kilobytes.&lt;/strong&gt; Our watch face uses 17 KB of the 124 KB available on a Fenix 6X Pro.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Resources are separate&lt;/strong&gt;: strings, icons and menus in XML, translations in &lt;code&gt;resources-rus&lt;/code&gt;, &lt;code&gt;resources-deu&lt;/code&gt; and so on.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Your first app: a hit counter
&lt;/h2&gt;

&lt;p&gt;A simplified Clay Sniper core: UP is a hit, DOWN is a miss, the screen shows hits/shots. Create the project with "Monkey C: New Project" and you get:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;hit-counter/
  manifest.xml
  monkey.jungle         project.manifest = manifest.xml
  resources/drawables/  launcher icon
  resources/strings/    app name
  source/HitApp.mc
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The manifest:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;iq:manifest&lt;/span&gt; &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"3"&lt;/span&gt; &lt;span class="na"&gt;xmlns:iq&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"http://www.garmin.com/xml/connectiq"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;iq:application&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"your-uuid"&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"watch-app"&lt;/span&gt; &lt;span class="na"&gt;entry&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"HitApp"&lt;/span&gt;
      &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"@Strings.AppName"&lt;/span&gt; &lt;span class="na"&gt;launcherIcon&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"@Drawables.LauncherIcon"&lt;/span&gt;
      &lt;span class="na"&gt;minApiLevel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"3.4.0"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;iq:products&amp;gt;&lt;/span&gt;
      &lt;span class="nt"&gt;&amp;lt;iq:product&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"fenix6xpro"&lt;/span&gt;&lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="nt"&gt;&amp;lt;iq:product&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"fenix847mm"&lt;/span&gt;&lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="nt"&gt;&amp;lt;iq:product&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"fr55"&lt;/span&gt;&lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;/iq:products&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;iq:permissions/&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;iq:languages&amp;gt;&amp;lt;iq:language&amp;gt;&lt;/span&gt;eng&lt;span class="nt"&gt;&amp;lt;/iq:language&amp;gt;&amp;lt;/iq:languages&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;iq:barrels/&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/iq:application&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/iq:manifest&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The UUID cannot change after publishing. &lt;code&gt;minApiLevel="3.4.0"&lt;/code&gt; means roughly Fenix 6 generation and newer.&lt;/p&gt;

&lt;p&gt;The code:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight brightscript"&gt;&lt;code&gt;&lt;span class="n"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Toybox&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Application&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Toybox&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Toybox&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Lang&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Toybox&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;HitApp&lt;/span&gt; &lt;span class="n"&gt;extends&lt;/span&gt; &lt;span class="nc"&gt;Application&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;AppBase&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;AppBase&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;getInitialView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Views&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="k"&gt;or&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Views&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;InputDelegates&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;var&lt;/span&gt; &lt;span class="n"&gt;view&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;HitView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;view&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;HitDelegate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;view&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;HitView&lt;/span&gt; &lt;span class="n"&gt;extends&lt;/span&gt; &lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;View&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;var&lt;/span&gt; &lt;span class="n"&gt;hits&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;Number&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="n"&gt;var&lt;/span&gt; &lt;span class="n"&gt;shots&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;Number&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;View&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;onUpdate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;dc&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Dc&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;Void&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;dc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setColor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;COLOR_WHITE&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;COLOR_BLACK&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="n"&gt;dc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;clear&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="n"&gt;dc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;drawText&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;dc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getWidth&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;dc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getHeight&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;FONT_NUMBER_MEDIUM&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="n"&gt;hits&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="s2"&gt;"/"&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;shots&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;TEXT_JUSTIFY_CENTER&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="nc"&gt;Graphics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;TEXT_JUSTIFY_VCENTER&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;HitDelegate&lt;/span&gt; &lt;span class="n"&gt;extends&lt;/span&gt; &lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;BehaviorDelegate&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;var&lt;/span&gt; &lt;span class="n"&gt;view&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;HitView&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;v&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nc"&gt;HitView&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nc"&gt;BehaviorDelegate&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;initialize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="n"&gt;view&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;v&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;onPreviousPage&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="kt"&gt;Boolean&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;shot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;onNextPage&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="kt"&gt;Boolean&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;shot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="k"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;shot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hit&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="kt"&gt;Boolean&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="kt"&gt;Boolean&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;view&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;shots&lt;/span&gt; &lt;span class="o"&gt;+=&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;hit&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;view&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;hits&lt;/span&gt; &lt;span class="o"&gt;+=&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
        &lt;span class="nc"&gt;WatchUi&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;requestUpdate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;BehaviorDelegate&lt;/code&gt; maps input to behaviors, not physical buttons: UP/DOWN on button watches, swipes on touch ones. One app, every model. (In Clay Sniper we actually swallow swipes on the shot screen so an accidental touch doesn't record a miss.)&lt;/p&gt;

&lt;p&gt;From here it grows the way Clay Sniper did: &lt;code&gt;Attention.vibrate&lt;/code&gt;, &lt;code&gt;Sensor.enableSensorEvents&lt;/code&gt; for heart rate, &lt;code&gt;ActivityRecording.createSession&lt;/code&gt; with &lt;code&gt;SPORT_SHOOTING&lt;/code&gt;, &lt;code&gt;FitContributor&lt;/code&gt; for custom fields — each with its permission in the manifest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build, simulate, test
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;monkeyc -f monkey.jungle -d fenix847mm -y developer_key.der -l 3 -o bin/HitCounter.prg
connectiq &lt;span class="o"&gt;&amp;amp;&lt;/span&gt;
monkeydo bin/HitCounter.prg fenix847mm

monkeyc -f monkey.jungle -d fenix847mm -y developer_key.der --unit-test -o bin/test.prg
monkeydo bin/test.prg fenix847mm -t

monkeyc -f monkey.jungle -y developer_key.der -e -r -o bin/HitCounter.iq   &lt;span class="c"&gt;# store package&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A test is a function annotated &lt;code&gt;(:test)&lt;/code&gt; that returns &lt;code&gt;true&lt;/code&gt;; it is stripped from release builds. A real one from Clay Sniper:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;(:test)
function lastShotClosesSeries(logger as Test.Logger) as Boolean {
    var s = TestSupport.started(3);
    WorkoutReducer.reduce(s, A_HIT, null);
    WorkoutReducer.reduce(s, A_MISS, null);
    WorkoutReducer.reduce(s, A_HIT, null);
    Test.assertEqual(s.completedSeries.size(), 1);
    return s.totalHits() == 2 &amp;amp;&amp;amp; s.totalShots() == 3 &amp;amp;&amp;amp; s.seriesNumber() == 2;
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Test at least three models: a big screen (Fenix 8), an old one (Fenix 6) and a small one (Forerunner 55). Almost all of our layout bugs showed up on the small one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sideloading to your own watch
&lt;/h2&gt;

&lt;p&gt;Build a &lt;code&gt;.prg&lt;/code&gt; for your model, plug the watch in, and copy the file into &lt;code&gt;GARMIN/APPS&lt;/code&gt; (not the root — the watch won't see it there). On a Mac the watch is an MTP device, so you need something like OpenMTP.&lt;/p&gt;

&lt;h2&gt;
  
  
  Publishing to the Connect IQ Store
&lt;/h2&gt;

&lt;p&gt;There is no CLI or API, only the web portal.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Build the &lt;code&gt;.iq&lt;/code&gt; package (our package covered 90 models).&lt;/li&gt;
&lt;li&gt;Upload it and type the version number (it isn't stored in the project).&lt;/li&gt;
&lt;li&gt;Fill in the listing: name, description, category, a 500×500 cover under 300 KB, screenshots under 150 KB each.&lt;/li&gt;
&lt;li&gt;Answer whether the app collects data and has paid features.&lt;/li&gt;
&lt;li&gt;Wait for review. Garmin promises up to three business days; before approval the public page returns 404.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Gotchas we hit
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What happened&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;th&gt;Fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A build sideloaded over USB never synced workouts to the iPhone&lt;/td&gt;
&lt;td&gt;Messages go through Garmin Connect; our explanation is that it doesn't relay messages for an app installed outside the store&lt;/td&gt;
&lt;td&gt;Test watch-to-phone sync only on a store install; it works there. Keep USB builds for screens and buttons&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Crash on Forerunner 55: Symbol Not Found&lt;/td&gt;
&lt;td&gt;No barometer, so &lt;code&gt;meanSeaLevelPressure&lt;/code&gt; doesn't exist; strict typing doesn't catch it&lt;/td&gt;
&lt;td&gt;Read every optional field behind &lt;code&gt;has&lt;/code&gt;, show a dash when missing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Copied app didn't show up&lt;/td&gt;
&lt;td&gt;File was in the device root&lt;/td&gt;
&lt;td&gt;Use &lt;code&gt;GARMIN/APPS&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time overlapped labels on a 208 px screen&lt;/td&gt;
&lt;td&gt;Layout was designed on a big Fenix&lt;/td&gt;
&lt;td&gt;Pick font size and line count from the measured screen&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;First review took longer than promised&lt;/td&gt;
&lt;td&gt;Still "Pending" on day five&lt;/td&gt;
&lt;td&gt;Budget a week, don't edit the listing during review&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Portal rejected a developer name with a space&lt;/td&gt;
&lt;td&gt;Form restriction&lt;/td&gt;
&lt;td&gt;We are "KLukyanov.ru"&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The first one is the nasty one. Everything looks like a bug in your own code: the workout sits in the outbox, the phone stays silent, and the real cause is how the app was installed.&lt;/p&gt;

&lt;h2&gt;
  
  
  By the numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;2 days from first commit to store submission&lt;/li&gt;
&lt;li&gt;~2,000 lines of Monkey C, 29 unit tests&lt;/li&gt;
&lt;li&gt;90 watch models, Connect IQ 3.4+ (Fenix 6 and newer)&lt;/li&gt;
&lt;li&gt;6 UI languages&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The code was written with an AI coding agent. It knows Monkey C worse than Swift, but it is very good at porting existing logic between languages, and the Apple Watch reducer was the spec. That is how two weeks became two days.&lt;/p&gt;

&lt;h2&gt;
  
  
  Next: watch faces
&lt;/h2&gt;

&lt;p&gt;Our first watch face, Clay Sniper Range, is already submitted: a compass ring with the sun and a wind arrow, and everything a shooter checks before stepping onto the station — sunrise and sunset, daylight left, heart rate, temperature and pressure. A second one is in the works. Part 2 is about both.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/garmin-connect-iq-app/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>garmin</category>
      <category>tutorial</category>
      <category>ios</category>
      <category>swift</category>
    </item>
    <item>
      <title>I built a one-click launcher for local LLMs on the Mac (llama.cpp + Qwen3 + OpenCode)</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Wed, 04 Nov 2026 19:39:23 +0000</pubDate>
      <link>https://dev.to/klukyanov/i-built-a-one-click-launcher-for-local-llms-on-the-mac-llamacpp-qwen3-opencode-1fpo</link>
      <guid>https://dev.to/klukyanov/i-built-a-one-click-launcher-for-local-llms-on-the-mac-llamacpp-qwen3-opencode-1fpo</guid>
      <description>&lt;p&gt;Most people who try local LLMs on a Mac don't get stuck on installation. They get stuck on the questions that come before it: which model, which quantization, how much context, will it fit in my RAM, and how do I hook an agent up to it?&lt;/p&gt;

&lt;p&gt;After my write-up on running LLMs locally on Apple Silicon, that was the most common message I got: "I understand what fits my Mac, but I don't want to read docs to set it up." So I built &lt;strong&gt;Local AI Starter&lt;/strong&gt;, a small open-source wizard that answers those questions for you. One double-click, and your Mac runs an AI assistant: the OpenCode agent in the terminal and a web chat in the browser, both on a local model.&lt;/p&gt;

&lt;p&gt;Code and release: &lt;a href="https://github.com/kiri11ko/local-ai-starter/releases/tag/v2.0.0" rel="noopener noreferrer"&gt;github.com/kiri11ko/local-ai-starter&lt;/a&gt; (MIT).&lt;/p&gt;

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

&lt;p&gt;Double-click &lt;code&gt;RunMe.command&lt;/code&gt; (the first time: right-click → Open, so Gatekeeper lets a downloaded script run). The wizard speaks English or Russian, depending on your system language. Pick options with ↑/↓ and Enter; plain Enter always takes the recommended one.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Machine check.&lt;/strong&gt; It reads your RAM and free disk space and suggests a model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plan and "Start?"&lt;/strong&gt; You see every download with its size. Nothing is fetched until you say yes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network check and download.&lt;/strong&gt; It checks that GitHub and Hugging Face are reachable, then downloads the engine, the model and OpenCode with progress, speed and ETA. Stalled downloads retry and resume.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A real test.&lt;/strong&gt; It starts &lt;code&gt;llama-server&lt;/code&gt;, waits for it, and &lt;strong&gt;asks the model a test question&lt;/strong&gt;. Only after a real answer does it say "All set".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OpenCode opens&lt;/strong&gt; in a sandbox folder, &lt;code&gt;local-ai/workspace&lt;/code&gt;, with a practice &lt;code&gt;index.html&lt;/code&gt;. Type a task like "Change the heading in index.html and add a dark theme toggle".&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;After &lt;code&gt;/exit&lt;/code&gt; you get a menu: stop the server, keep it running, back to OpenCode, open the web chat, switch model, models on disk, status and log, delete everything. Later runs download nothing and go straight to OpenCode.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why another installer
&lt;/h2&gt;

&lt;p&gt;Ollama and LM Studio are great, and if you already use them, keep using them. Local AI Starter solves a narrower problem: removing the decisions.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A pinned, verified stack.&lt;/strong&gt; llama.cpp build b12110, OpenCode v1.19.5 and a specific model file, each checked against its SHA-256.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Done" means "answered".&lt;/strong&gt; No success message just because a file exists. If the server dies, you see the last log line, not a blank window.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network errors you can act on.&lt;/strong&gt; If a host is blocked, the wizard tells you which one and why (timeout, DNS, refused, TLS interception, HTTP error) and suggests another network, a VPN or &lt;code&gt;HTTPS_PROXY&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One folder, nothing else.&lt;/strong&gt; Everything lives in &lt;code&gt;local-ai/&lt;/code&gt; next to the script. PATH, shell configs and your global OpenCode settings are never touched. Uninstall = delete the folder.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Models
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Download&lt;/th&gt;
&lt;th&gt;Mac RAM&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Qwen3 8B Q4_K_M (recommended)&lt;/td&gt;
&lt;td&gt;~4.7 GB&lt;/td&gt;
&lt;td&gt;12 GB+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen3 4B Q4_K_M&lt;/td&gt;
&lt;td&gt;~2.3 GB&lt;/td&gt;
&lt;td&gt;8 GB+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen2.5 Coder 7B Q4_K_M&lt;/td&gt;
&lt;td&gt;~4.4 GB&lt;/td&gt;
&lt;td&gt;12 GB+&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All run with a 32K context (16K under 12 GB of RAM): OpenCode's system instructions alone take about 10K tokens. I recommend Qwen3 8B even for code, because Qwen3's tool calling via &lt;code&gt;--jinja&lt;/code&gt; is more reliable, and an agent that can't call tools can't read or edit files.&lt;/p&gt;

&lt;p&gt;Honest limits: a 4–8B model handles small edits. It doesn't replace a cloud agent on a real codebase, which is exactly why it starts in a sandbox, not in your repo.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is the archive safe?
&lt;/h2&gt;

&lt;p&gt;Running a script from the internet deserves caution, so there are three independent checks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;VirusTotal:&lt;/strong&gt; 0 of 65 engines flagged the v2.0.0 archive. &lt;a href="https://www.virustotal.com/gui/file/87d134e162170bf73c226c8e3674e71427160619232d16446c205538ee3ed29e" rel="noopener noreferrer"&gt;Public report&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SHA-256:&lt;/strong&gt; &lt;code&gt;87d134e162170bf73c226c8e3674e71427160619232d16446c205538ee3ed29e&lt;/code&gt;. Verify with &lt;code&gt;shasum -a 256 Local-AI-Starter-v2.0.0.zip&lt;/code&gt;. The same hash is in the GitHub release.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open source:&lt;/strong&gt; one readable Python file using only the standard library, plus three tiny launch scripts. No admin password, no disabling system protection.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Privacy
&lt;/h2&gt;

&lt;p&gt;The server listens on &lt;code&gt;127.0.0.1&lt;/code&gt; only, so nothing on your LAN or the internet can reach it. Your prompts never leave the machine. The script goes online only to fetch the engine and OpenCode (GitHub releases) and the model (Hugging Face). No telemetry.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Mac on Apple Silicon is the main target (Metal). Intel Macs work, slower.&lt;/li&gt;
&lt;li&gt;Python 3.9+. On a clean Mac, the first &lt;code&gt;python3&lt;/code&gt; call offers Apple's developer tools; that's the normal macOS dialog.&lt;/li&gt;
&lt;li&gt;Windows (&lt;code&gt;RunMe.bat&lt;/code&gt;) and Linux (&lt;code&gt;RunMe.sh&lt;/code&gt;) builds exist but are CPU-only for now.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you try it, I'd love to hear which Mac you ran it on and whether the model handled the first task.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/en/notes/local-ai-starter/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) are on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;. The launcher archive and its updates are pinned there.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>macos</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I added Storj to my iOS backup app. Here's when it actually beats iCloud</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Sat, 31 Oct 2026 14:12:43 +0000</pubDate>
      <link>https://dev.to/klukyanov/i-added-storj-to-my-ios-backup-app-heres-when-it-actually-beats-icloud-1apb</link>
      <guid>https://dev.to/klukyanov/i-added-storj-to-my-ios-backup-app-heres-when-it-actually-beats-icloud-1apb</guid>
      <description>&lt;p&gt;I assumed decentralized storage would obviously beat iCloud on price. Then I added Storj to my iOS app and did the maths. On full iCloud plans it doesn't. Between those plans, it often does.&lt;/p&gt;

&lt;p&gt;The app is &lt;a href="https://plunload.ru/en/" rel="noopener noreferrer"&gt;CopyProof&lt;/a&gt;. It copies photos and videos from iPhone and iPad to USB drives, SSDs and SD cards, and verifies every file with SHA-256. I have been fighting for this app for most of 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  A year on one app
&lt;/h2&gt;

&lt;p&gt;I started on February 2. The idea was broad: photo backup, library cleanup, duplicate search, tidying contacts and calendars. In spring I moved it to a new architecture, module by module. TestFlight builds started in late May, because a real library on a real iPhone shows what twenty test photos never will.&lt;/p&gt;

&lt;p&gt;The longest part wasn't the code. It was App Review. The app was rejected several times. Some issues concerned the name and presentation, and those took an evening to fix. The main one didn't: Apple felt the app was not unique enough. There is no quick patch for that, so I had to rethink the product.&lt;/p&gt;

&lt;p&gt;I reworked it several times, renamed it from iPhoto Cleaner to Photo Backup and Clean and then to CopyProof, and cut everything secondary. What remained is the part it does better than others: copying with verification of every file. Build 19 finally reached the store, and CopyProof launched on October 6.&lt;/p&gt;

&lt;p&gt;After that, plans that had been stuck behind review for months started moving. Four updates shipped in three weeks, the latest on October 29 with direct backup to your own Storj bucket. The project now has 353 commits, about 24,000 lines of Swift and 606 tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the Storj integration works
&lt;/h2&gt;

&lt;p&gt;There is no server of mine in the middle. You create a Storj account, a bucket and S3 credentials, then paste them into the app. Credentials stay in the device Keychain, and photos travel from the iPhone through &lt;code&gt;gateway.storjshare.io&lt;/code&gt; into your bucket.&lt;/p&gt;

&lt;p&gt;One honest caveat: with the hosted gateway, encryption happens at the gateway, not on the phone. If Storj must be technically unable to read a file, encrypt it yourself before uploading.&lt;/p&gt;

&lt;p&gt;I wrote the S3 client myself, with no SDK: SigV4 on CryptoKit, plus multipart upload in 64 MB parts for large videos. Verification works like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The request body is signed with a real SHA-256 and sent with &lt;code&gt;Content-MD5&lt;/code&gt;, so the gateway rejects corrupted data.&lt;/li&gt;
&lt;li&gt;The SHA-256 of the source file goes into object metadata as &lt;code&gt;x-amz-meta-sha256&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;After upload, a &lt;code&gt;HEAD&lt;/code&gt; request compares size and hash. Only then does the file count as copied.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This confirms the copy without downloading it back, which matters because Storj egress is paid.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs: Storj vs iCloud+
&lt;/h2&gt;

&lt;p&gt;iCloud+ is sold in steps, and you pay for the whole plan even if you use half of it. Storj is linear: $7 per TB per month, with a $5 account minimum. Prices are US prices as of October 31, 2026, on the Storj Standard tier.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Archive size&lt;/th&gt;
&lt;th&gt;iCloud+ plan needed&lt;/th&gt;
&lt;th&gt;iCloud+ $/mo&lt;/th&gt;
&lt;th&gt;Storj $/mo&lt;/th&gt;
&lt;th&gt;Cheaper&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;100 GB&lt;/td&gt;
&lt;td&gt;200 GB&lt;/td&gt;
&lt;td&gt;2.99&lt;/td&gt;
&lt;td&gt;5.00&lt;/td&gt;
&lt;td&gt;iCloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;500 GB&lt;/td&gt;
&lt;td&gt;2 TB&lt;/td&gt;
&lt;td&gt;9.99&lt;/td&gt;
&lt;td&gt;5.00&lt;/td&gt;
&lt;td&gt;Storj&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1 TB&lt;/td&gt;
&lt;td&gt;2 TB&lt;/td&gt;
&lt;td&gt;9.99&lt;/td&gt;
&lt;td&gt;7.00&lt;/td&gt;
&lt;td&gt;Storj&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2 TB&lt;/td&gt;
&lt;td&gt;2 TB&lt;/td&gt;
&lt;td&gt;9.99&lt;/td&gt;
&lt;td&gt;14.00&lt;/td&gt;
&lt;td&gt;iCloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3 TB&lt;/td&gt;
&lt;td&gt;6 TB&lt;/td&gt;
&lt;td&gt;29.99&lt;/td&gt;
&lt;td&gt;21.00&lt;/td&gt;
&lt;td&gt;Storj&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4 TB&lt;/td&gt;
&lt;td&gt;6 TB&lt;/td&gt;
&lt;td&gt;29.99&lt;/td&gt;
&lt;td&gt;28.00&lt;/td&gt;
&lt;td&gt;Storj&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6 TB&lt;/td&gt;
&lt;td&gt;6 TB&lt;/td&gt;
&lt;td&gt;29.99&lt;/td&gt;
&lt;td&gt;42.00&lt;/td&gt;
&lt;td&gt;iCloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8 TB&lt;/td&gt;
&lt;td&gt;12 TB&lt;/td&gt;
&lt;td&gt;59.99&lt;/td&gt;
&lt;td&gt;56.00&lt;/td&gt;
&lt;td&gt;Storj&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;12 TB&lt;/td&gt;
&lt;td&gt;12 TB&lt;/td&gt;
&lt;td&gt;59.99&lt;/td&gt;
&lt;td&gt;84.00&lt;/td&gt;
&lt;td&gt;iCloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;15 TB&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;n/a&lt;/td&gt;
&lt;td&gt;105.00&lt;/td&gt;
&lt;td&gt;Storj only&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Storj wins in three bands: roughly 200 GB to 1.4 TB, 2 to 4.3 TB and 6 to 8.5 TB. The biggest relative gap is under 700 GB, at $5 against $9.99. Above 12 TB, Apple has no plan at all.&lt;/p&gt;

&lt;p&gt;That suggests a practical trick. With a 2.5 TB library, Apple charges $29.99 for the 6 TB plan. Move 1 TB of old photos to Storj, drop back to the 2 TB plan, and you pay $16.99. That saves $156 a year.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fine print
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The $5 minimum&lt;/strong&gt; covers about 700 GB. Accounts paying in USDC are exempt.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Egress is paid:&lt;/strong&gt; $7 per TB, so restoring 1 TB costs about one extra month of storage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Minimum retention is 30 days.&lt;/strong&gt; That doesn't matter for an archive.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CopyProof tokens are a one-time cost:&lt;/strong&gt; one file is one token, and 1,000 tokens are free. Packs cost $0.99 for 100, $3.99 for 500 and $6.99 for 1,000. On a library with tens of thousands of files this adds up, so include it in your sums.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storj does not replace iCloud.&lt;/strong&gt; It doesn't sync devices or back up the iPhone. It is an archive, but deleting a photo on your phone won't remove it from the bucket.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storj Labs filed for Chapter 11 reorganization&lt;/strong&gt; on July 26, 2026. The company says the network keeps running and expects no interruptions. Either way, a single cloud should never hold your only copy, so CopyProof lets you back up to a drive and a bucket.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Roadmap
&lt;/h2&gt;

&lt;p&gt;The copy pipeline already talks to a storage protocol, so each new destination is a new implementation rather than a rewrite. They ship one at a time, with no dates, and the order may change.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stage&lt;/th&gt;
&lt;th&gt;Storage&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Done&lt;/td&gt;
&lt;td&gt;USB, SSD, SD card, Files folder, Storj&lt;/td&gt;
&lt;td&gt;in the App Store&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Home NAS&lt;/td&gt;
&lt;td&gt;QNAP, Synology, UGREEN, TrueNAS, Asustor, WD My Cloud, Nextcloud&lt;/td&gt;
&lt;td&gt;planned&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Major clouds&lt;/td&gt;
&lt;td&gt;Google Drive, Dropbox, OneDrive, Yandex Disk&lt;/td&gt;
&lt;td&gt;planned&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Low-cost and decentralized&lt;/td&gt;
&lt;td&gt;Sia, Backblaze B2, Wasabi, Cloudflare R2&lt;/td&gt;
&lt;td&gt;exploring&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The last row is where real savings live. &lt;a href="https://sia.storage/" rel="noopener noreferrer"&gt;Sia Storage&lt;/a&gt; lists 5 TB at $14.99 a month and 10 TB at $19.99. &lt;a href="https://www.backblaze.com/cloud-storage/pricing" rel="noopener noreferrer"&gt;Backblaze B2&lt;/a&gt; starts at $6.95 per TB with no minimum fee. The existing S3 client should work with B2, Wasabi and R2 with few changes, while Sia still needs testing through its s3d gateway. So for now it is "exploring", not a promise.&lt;/p&gt;

&lt;p&gt;The current queue is always at &lt;a href="https://plunload.ru/en/#plan" rel="noopener noreferrer"&gt;plunload.ru&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Which storage would you want in a photo backup app first?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/copyproof-storj/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>swift</category>
      <category>cloud</category>
      <category>storage</category>
    </item>
    <item>
      <title>How much RAM does a local LLM need on a Mac? Measurements on 16 GB and a 16–128 GB sizing table</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Wed, 28 Oct 2026 08:28:00 +0000</pubDate>
      <link>https://dev.to/klukyanov/how-much-ram-does-a-local-llm-need-on-a-mac-measurements-on-16-gb-and-a-16-128-gb-sizing-table-4lfi</link>
      <guid>https://dev.to/klukyanov/how-much-ram-does-a-local-llm-need-on-a-mac-measurements-on-16-gb-and-a-16-128-gb-sizing-table-4lfi</guid>
      <description>&lt;p&gt;"Will this model run on my Mac?" usually gets answered with the model's file size. That's only a third of the answer. While a model runs, memory goes to three things: the weights, the context (KV cache) and macOS with everything else you have open. I measured three models on my MacBook M5 with 16 GB, calculated the context cost for classic 8B–70B models, and put together what actually fits into 16 to 128 GB.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the memory goes: weights, context, system
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Weights.&lt;/strong&gt; At 4-bit (Q4, MLX 4-bit), about 0.5 GB per billion parameters. 8B is ~5 GB, 14B is 8–9 GB, 32B is 18–20 GB, 70B is ~40 GB.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Context (KV cache).&lt;/strong&gt; For every token in the context window the model keeps intermediate results on every layer. It grows linearly with length. The catch: Ollama and LM Studio reserve memory for the whole configured window up front, not for the text you actually send.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;System and apps.&lt;/strong&gt; By default macOS lets the GPU use only part of unified memory. On my 16 GB MacBook Metal's &lt;code&gt;recommendedMaxWorkingSetSize&lt;/code&gt; is 12.7 GB, about three quarters. The rest belongs to macOS, the browser and the editor.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So the working rule is: &lt;strong&gt;weights + context ≤ ¾ of your Mac's RAM.&lt;/strong&gt; You can raise the GPU limit with &lt;code&gt;sysctl iogpu.wired_limit_mb&lt;/code&gt;, but then apps get less and macOS starts swapping.&lt;/p&gt;

&lt;h2&gt;
  
  
  My measurements on a MacBook M5, 16 GB
&lt;/h2&gt;

&lt;p&gt;Setup: Apple M5, 16 GB, Ollama 0.31, MLX builds. Each model ran in three modes: a short request (a 150-word business email) with a 4K window; a 4.2K-token document (~10 pages) with an 8K window; an 18K-token document (~45 pages) with a 32K window, asking for five key takeaways. Memory is what &lt;code&gt;ollama ps&lt;/code&gt; reports. Answers were capped at 200 tokens.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model, mode&lt;/th&gt;
&lt;th&gt;Memory&lt;/th&gt;
&lt;th&gt;Prompt reading&lt;/th&gt;
&lt;th&gt;Generation&lt;/th&gt;
&lt;th&gt;Total time&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 0.8B, short&lt;/td&gt;
&lt;td&gt;1.08 GB&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;109 tok/s&lt;/td&gt;
&lt;td&gt;3 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 0.8B, 10 pages&lt;/td&gt;
&lt;td&gt;1.14 GB&lt;/td&gt;
&lt;td&gt;2257 tok/s&lt;/td&gt;
&lt;td&gt;103 tok/s&lt;/td&gt;
&lt;td&gt;4 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 0.8B, 45 pages&lt;/td&gt;
&lt;td&gt;1.73 GB&lt;/td&gt;
&lt;td&gt;1952 tok/s&lt;/td&gt;
&lt;td&gt;86 tok/s&lt;/td&gt;
&lt;td&gt;12 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 4B, short&lt;/td&gt;
&lt;td&gt;3.43 GB&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;34 tok/s&lt;/td&gt;
&lt;td&gt;8 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 4B, 10 pages&lt;/td&gt;
&lt;td&gt;3.59 GB&lt;/td&gt;
&lt;td&gt;390 tok/s&lt;/td&gt;
&lt;td&gt;32 tok/s&lt;/td&gt;
&lt;td&gt;18 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 4B, 45 pages&lt;/td&gt;
&lt;td&gt;4.81 GB&lt;/td&gt;
&lt;td&gt;312 tok/s&lt;/td&gt;
&lt;td&gt;27 tok/s&lt;/td&gt;
&lt;td&gt;67 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gemma 4 12B, short&lt;/td&gt;
&lt;td&gt;7.64 GB&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;25 tok/s&lt;/td&gt;
&lt;td&gt;14 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gemma 4 12B, 10 pages&lt;/td&gt;
&lt;td&gt;8.29 GB&lt;/td&gt;
&lt;td&gt;102 tok/s&lt;/td&gt;
&lt;td&gt;16 tok/s&lt;/td&gt;
&lt;td&gt;57 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gemma 4 12B, 45 pages&lt;/td&gt;
&lt;td&gt;9.21 GB&lt;/td&gt;
&lt;td&gt;72 tok/s&lt;/td&gt;
&lt;td&gt;9 tok/s&lt;/td&gt;
&lt;td&gt;4.8 min&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;What stands out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Context is cheap on new models.&lt;/strong&gt; A 32K window added 1.4 GB to Qwen 4B and 1.6 GB to Gemma 12B, roughly 50 KB per token. Most layers in Qwen 3.5 and Gemma 4 attend to a limited window rather than the whole text, so their cache is several times smaller than in classic models.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Long documents hurt latency more than memory.&lt;/strong&gt; Qwen 4B answers a short question in 8 seconds and a 45-page document in 67. Gemma 12B needs almost five minutes for the same document. A model three times larger reads four times slower.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;On 16 GB, an 8 GB model depends on everything else you run.&lt;/strong&gt; My first Gemma run on the 10-page document happened while I was working on the same laptop: 169 seconds and 4 tok/s. The rerun on a quiet system: 57 seconds and 16 tok/s.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Context cost for classic models
&lt;/h2&gt;

&lt;p&gt;In classic architectures (Llama 3, Qwen 3 and most 2025 models) every layer caches the whole window. The size follows from the config: 2 × layers × KV heads × head dim × 2 bytes. From the &lt;code&gt;config.json&lt;/code&gt; files on Hugging Face, at 16-bit (the default in Ollama and llama.cpp):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Q4 weights&lt;/th&gt;
&lt;th&gt;Cache per token&lt;/th&gt;
&lt;th&gt;8K&lt;/th&gt;
&lt;th&gt;32K&lt;/th&gt;
&lt;th&gt;128K&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Llama 3.1 8B (32 layers)&lt;/td&gt;
&lt;td&gt;~5 GB&lt;/td&gt;
&lt;td&gt;128 KB&lt;/td&gt;
&lt;td&gt;1 GB&lt;/td&gt;
&lt;td&gt;4 GB&lt;/td&gt;
&lt;td&gt;16 GB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen3 14B (40 layers)&lt;/td&gt;
&lt;td&gt;~9 GB&lt;/td&gt;
&lt;td&gt;160 KB&lt;/td&gt;
&lt;td&gt;1.25 GB&lt;/td&gt;
&lt;td&gt;5 GB&lt;/td&gt;
&lt;td&gt;20 GB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen3 32B (64 layers)&lt;/td&gt;
&lt;td&gt;~19 GB&lt;/td&gt;
&lt;td&gt;256 KB&lt;/td&gt;
&lt;td&gt;2 GB&lt;/td&gt;
&lt;td&gt;8 GB&lt;/td&gt;
&lt;td&gt;32 GB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Llama 3.3 70B (80 layers)&lt;/td&gt;
&lt;td&gt;~40 GB&lt;/td&gt;
&lt;td&gt;320 KB&lt;/td&gt;
&lt;td&gt;2.5 GB&lt;/td&gt;
&lt;td&gt;10 GB&lt;/td&gt;
&lt;td&gt;40 GB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 4B / Gemma 4 12B (my measurement)&lt;/td&gt;
&lt;td&gt;3.4–7.6 GB&lt;/td&gt;
&lt;td&gt;~50 KB&lt;/td&gt;
&lt;td&gt;0.4 GB&lt;/td&gt;
&lt;td&gt;1.5 GB&lt;/td&gt;
&lt;td&gt;~6 GB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;At a full 128K window, a classic model's cache weighs as much as the 4-bit model itself. A 70B model with that window needs 80 GB.&lt;/p&gt;

&lt;h2&gt;
  
  
  What fits into 16–128 GB
&lt;/h2&gt;

&lt;p&gt;Applying "weights + context ≤ ¾ RAM" with the classic-model cache numbers above (newer models with a lean cache fit with room to spare). This is a calculation, not a measurement on every machine:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Mac RAM&lt;/th&gt;
&lt;th&gt;For the model&lt;/th&gt;
&lt;th&gt;Short requests, 8K&lt;/th&gt;
&lt;th&gt;Documents, 32K&lt;/th&gt;
&lt;th&gt;Whole books, 128K&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;16 GB&lt;/td&gt;
&lt;td&gt;~12 GB&lt;/td&gt;
&lt;td&gt;up to 14B, tight&lt;/td&gt;
&lt;td&gt;8B; Gemma 4 12B (9.2 GB measured)&lt;/td&gt;
&lt;td&gt;only new-gen 4B&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;24 GB&lt;/td&gt;
&lt;td&gt;~18 GB&lt;/td&gt;
&lt;td&gt;14B comfortably&lt;/td&gt;
&lt;td&gt;14B (14 GB)&lt;/td&gt;
&lt;td&gt;only new-gen up to 12B&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;32 GB&lt;/td&gt;
&lt;td&gt;~24 GB&lt;/td&gt;
&lt;td&gt;32B, tight (21 GB)&lt;/td&gt;
&lt;td&gt;14B comfortably&lt;/td&gt;
&lt;td&gt;8B (21 GB)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;48 GB&lt;/td&gt;
&lt;td&gt;~36 GB&lt;/td&gt;
&lt;td&gt;32B comfortably&lt;/td&gt;
&lt;td&gt;32B (27 GB)&lt;/td&gt;
&lt;td&gt;14B (29 GB)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;64 GB&lt;/td&gt;
&lt;td&gt;~48 GB&lt;/td&gt;
&lt;td&gt;70B, tight (43 GB)&lt;/td&gt;
&lt;td&gt;32B comfortably&lt;/td&gt;
&lt;td&gt;32B only with a compressed cache&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;96 GB&lt;/td&gt;
&lt;td&gt;~72 GB&lt;/td&gt;
&lt;td&gt;70B comfortably&lt;/td&gt;
&lt;td&gt;70B (50 GB)&lt;/td&gt;
&lt;td&gt;32B (51 GB)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;128 GB&lt;/td&gt;
&lt;td&gt;~96 GB&lt;/td&gt;
&lt;td&gt;70B comfortably&lt;/td&gt;
&lt;td&gt;70B comfortably&lt;/td&gt;
&lt;td&gt;70B (80 GB)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How to squeeze a model into less memory
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Set the context window for the task.&lt;/strong&gt; Memory is reserved for the whole window. If you chat in short messages, a 128K window just holds gigabytes empty. In Ollama it's &lt;code&gt;num_ctx&lt;/code&gt;, in LM Studio it's Context Length.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compress the cache.&lt;/strong&gt; For GGUF models in Ollama, &lt;code&gt;OLLAMA_KV_CACHE_TYPE=q8_0&lt;/code&gt; (with &lt;code&gt;OLLAMA_FLASH_ATTENTION=1&lt;/code&gt;) stores the cache in 8 bits and halves it, with little quality impact. That lets a 32B model with a 128K window fit in 64 GB.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prefer new-generation models.&lt;/strong&gt; Qwen 3.5 and Gemma 4 spend ~50 KB per context token in my test, classic Llama 8B spends 128 KB. For long documents on a small Mac, that matters more than parameter count.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Close what you don't need.&lt;/strong&gt; On 16 GB, a browser with a dozen tabs and Xcode compete for the same memory the model needs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How much memory to buy
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;16 GB&lt;/strong&gt;: an assistant for short texts, translation and drafts on 4–12B models. Documents of dozens of pages work, but you wait minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;32 GB&lt;/strong&gt;: the sensible minimum for document work; 14B with a 32K window fits comfortably.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;48–64 GB&lt;/strong&gt;: 32B models, where local AI stops losing to the cloud on everyday tasks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;96–128 GB&lt;/strong&gt;: 70B and large MoE models, when data must never leave the machine.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;How much memory does your Mac have, and which local model do you actually run every day?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/llm-memory-mac/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>macos</category>
      <category>machinelearning</category>
    </item>
    <item>
      <title>Should your company buy an AI server? Hardware tiers, prices and payback vs the cloud</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Tue, 27 Oct 2026 14:45:53 +0000</pubDate>
      <link>https://dev.to/klukyanov/should-your-company-buy-an-ai-server-hardware-tiers-prices-and-payback-vs-the-cloud-3ohj</link>
      <guid>https://dev.to/klukyanov/should-your-company-buy-an-ai-server-hardware-tiers-prices-and-payback-vs-the-cloud-3ohj</guid>
      <description>&lt;p&gt;Companies keep asking me for an AI model on their own hardware. Usually the honest answer is "not yet": for short questions, a cloud API stays cheaper than a GPU workstation for about a year and a half. The picture changes when the model has to read a lot of internal documents on every request, or when the data simply can't leave the building. Then a single-GPU machine can pay for itself in roughly four months.&lt;/p&gt;

&lt;p&gt;Below is how I size the hardware, what it costs (I'm based in Russia, so prices are from the Russian market in October 2026), and how to do the payback math for your own workload.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a company wants its own server at all
&lt;/h2&gt;

&lt;p&gt;Three reasons come up again and again:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Data must stay inside.&lt;/strong&gt; Contracts, medical records, customer emails, source code. Even when a cloud provider promises zero retention, legal or security teams often say no. A box in the office ends the discussion.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;API bills scale with volume.&lt;/strong&gt; Short questions cost almost nothing. When every request carries ten pages of documents, the bill multiplies. Your own hardware costs the same at any load.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Predictability.&lt;/strong&gt; A hosted model can be updated, repriced or rate-limited. Your own model behaves the same until you change it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If none of these apply, start with a cloud API. It's faster and cheaper, and you can move to your own server once you know your real request volume.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much memory a model needs
&lt;/h2&gt;

&lt;p&gt;The key spec is GPU memory, not CPU power. The model has to fit entirely in VRAM, otherwise it runs many times slower or doesn't start.&lt;/p&gt;

&lt;p&gt;Local models are almost always quantized to 4 bits per parameter, with barely noticeable quality loss. That gives a simple rule of thumb: &lt;strong&gt;about 0.5 GB per billion parameters, plus headroom for context.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;7–8B: about 5 GB&lt;/li&gt;
&lt;li&gt;14B: 8–9 GB&lt;/li&gt;
&lt;li&gt;32B: 18–20 GB&lt;/li&gt;
&lt;li&gt;70B: about 40 GB&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The headroom matters. Long documents and several concurrent users add gigabytes on top of the weights.&lt;/p&gt;

&lt;h2&gt;
  
  
  My measurement: what running out of memory looks like
&lt;/h2&gt;

&lt;p&gt;I ran the same task on my own laptop, a MacBook with Apple M5 and 16 GB of memory, using Ollama: write a 150-word business email about a three-day delivery delay.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Generation&lt;/th&gt;
&lt;th&gt;Reading a 45-page document&lt;/th&gt;
&lt;th&gt;Whole email&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Qwen 3.5 4B (~4 GB)&lt;/td&gt;
&lt;td&gt;35 tokens/s&lt;/td&gt;
&lt;td&gt;312 tokens/s, 67 s&lt;/td&gt;
&lt;td&gt;9 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Gemma 4 12B (~8 GB)&lt;/td&gt;
&lt;td&gt;20 tokens/s&lt;/td&gt;
&lt;td&gt;72 tokens/s, almost 5 min&lt;/td&gt;
&lt;td&gt;23 s&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The small model writes faster than a person reads. The model three times larger generates almost half as fast, and reads a long document four times slower: on 16 GB it's competing with the OS and open apps. For a short email you barely notice. Hand it a 45-page document and an employee waits almost five minutes. (Updated Oct 28: the first version quoted prompt speed measured on a 36-token request, which isn't meaningful; the numbers above are from a real document.)&lt;/p&gt;

&lt;p&gt;The lesson for a server: buy 1.5–2x more memory than the model weighs. A 20 GB model on a 24 GB card is a squeeze; on 32 GB it's comfortable.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to buy
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Task&lt;/th&gt;
&lt;th&gt;Models&lt;/th&gt;
&lt;th&gt;Hardware&lt;/th&gt;
&lt;th&gt;Price (Russia, 2026)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Writing assistant, summaries, pilot&lt;/td&gt;
&lt;td&gt;7–14B&lt;/td&gt;
&lt;td&gt;PC with RTX 5090 (32 GB) or a Mac with 32–64 GB&lt;/td&gt;
&lt;td&gt;card 393–490k RUB, ready PC from 639k RUB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Department knowledge base, document search&lt;/td&gt;
&lt;td&gt;up to 32B&lt;/td&gt;
&lt;td&gt;Same RTX 5090 PC: 18–20 GB for the model, the rest for context&lt;/td&gt;
&lt;td&gt;from 639k RUB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;70B-class models or gpt-oss-120b&lt;/td&gt;
&lt;td&gt;70–120B&lt;/td&gt;
&lt;td&gt;Workstation with RTX PRO 6000 Blackwell (96 GB)&lt;/td&gt;
&lt;td&gt;card 1.08–1.8M RUB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The largest open models, 1–2 users&lt;/td&gt;
&lt;td&gt;hundreds of B&lt;/td&gt;
&lt;td&gt;Mac Studio M3 Ultra, 512 GB unified memory&lt;/td&gt;
&lt;td&gt;2.79–2.99M RUB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rent instead of buying&lt;/td&gt;
&lt;td&gt;any&lt;/td&gt;
&lt;td&gt;RTX 5090 / H100 80 GB by the hour&lt;/td&gt;
&lt;td&gt;66 RUB/h / 353–359 RUB/h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cloud API&lt;/td&gt;
&lt;td&gt;YandexGPT, gpt-oss, Qwen, DeepSeek&lt;/td&gt;
&lt;td&gt;no hardware, pay per token&lt;/td&gt;
&lt;td&gt;0.1–0.8 RUB per 1,000 tokens&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Sources: &lt;a href="https://digital-razor.ru/media/articles/hardware/nvidia-geforce-rtx-5090-review/" rel="noopener noreferrer"&gt;Digital Razor&lt;/a&gt; for RTX 5090 and PCs, the RTX PRO 6000 &lt;a href="https://esports.ru/news/v-dns-poyavilas-na-prodazhu-videokarta-nvidia-blackwell-s-energopotrebleniem-600-vt/" rel="noopener noreferrer"&gt;launch at DNS&lt;/a&gt; at 1,079,999 RUB in February 2026, &lt;a href="https://megabait.net/categories/mak-studio-m3-ultra" rel="noopener noreferrer"&gt;Megabait&lt;/a&gt; for Mac Studio, &lt;a href="https://zeroquant.ru/arenda" rel="noopener noreferrer"&gt;zeroquant.ru&lt;/a&gt; for GPU rental, &lt;a href="https://aistudio.yandex.ru/docs/ru/ai-studio/pricing" rel="noopener noreferrer"&gt;Yandex AI Studio pricing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Two notes. NVIDIA cards have faster memory, so they answer quicker and handle several users at once better. A Mac gives you more memory per ruble and is nearly silent, but serves fewer people concurrently. For a team of 10–30 I'd pick a GPU; for one analyst or lawyer with huge documents, a Mac. And the RTX 5090 draws up to 575 W, the RTX PRO 6000 up to 600 W: this is a hot, loud machine that belongs in a server room, not under a meeting-room desk.&lt;/p&gt;

&lt;h2&gt;
  
  
  When your own server beats the cloud
&lt;/h2&gt;

&lt;p&gt;Example: a team of 20, each making 30 requests a day, 22 working days a month.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scenario&lt;/th&gt;
&lt;th&gt;Tokens per month&lt;/th&gt;
&lt;th&gt;YandexGPT Pro 5.1&lt;/th&gt;
&lt;th&gt;Payback of a 639k RUB PC&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Short questions (~3,000 tokens per request)&lt;/td&gt;
&lt;td&gt;~40M&lt;/td&gt;
&lt;td&gt;~32k RUB/month&lt;/td&gt;
&lt;td&gt;~20 months&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Answers over a knowledge base (~15,000 tokens: question + document chunks)&lt;/td&gt;
&lt;td&gt;~198M&lt;/td&gt;
&lt;td&gt;~158k RUB/month&lt;/td&gt;
&lt;td&gt;~4 months&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;YandexGPT Pro 5.1 costs 0.8 RUB per 1,000 tokens including VAT. Open models in the same cloud are cheaper (gpt-oss-120b at 0.3 RUB, gpt-oss-20b at 0.1 RUB), which pushes payback out another 2.5–8x.&lt;/p&gt;

&lt;p&gt;Renting is the middle ground. An RTX 5090 at 66 RUB an hour, kept only during working hours (about 200 hours a month), costs around 13k RUB a month; around the clock, about 48k. An H100 around the clock is about 255k RUB a month, which only makes sense under heavy load.&lt;/p&gt;

&lt;p&gt;Not included: electricity, setup and maintenance, and model quality. A 32B model that fits on an RTX 5090 trails YandexGPT Pro on some tasks and matches it on others. Test that on your own data before buying anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I'd roll it out
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pilot in the cloud.&lt;/strong&gt; Two or three weeks of real tasks through an API, using open models of the same size you'd later host. You learn your volume and whether the model copes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do the math&lt;/strong&gt; with real numbers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Buy for the model, not the other way round.&lt;/strong&gt; Pick the model that solves the task, then hardware with 1.5–2x memory headroom.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Integrate.&lt;/strong&gt; A model without access to documents, CRM and email can't do much. Most of the work is here, not in installing the server.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My default for a company starting out: don't buy a server right away. A month on a cloud API shows the real volume. If data can't leave the office or the model works over a document base, start with one RTX 5090 machine: it handles models up to 32B for a team of a few dozen people. The RTX PRO 6000 and a 512 GB Mac Studio are for tasks where a smaller model has proven not to be enough.&lt;/p&gt;

&lt;p&gt;Is your team running models on its own hardware yet? What tipped the decision, cost or security?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/ai-server-company/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>hardware</category>
      <category>business</category>
    </item>
    <item>
      <title>Making Money on the Web with AI in 2026: What's Growing, What's Dying</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Mon, 26 Oct 2026 15:09:19 +0000</pubDate>
      <link>https://dev.to/klukyanov/making-money-on-the-web-with-ai-in-2026-whats-growing-whats-dying-49ip</link>
      <guid>https://dev.to/klukyanov/making-money-on-the-web-with-ai-in-2026-whats-growing-whats-dying-49ip</guid>
      <description>&lt;p&gt;If your page ranks first on Google and an AI answer appears above it, you get 58% fewer clicks. That's from &lt;a href="https://ahrefs.com/blog/ai-overviews-reduce-clicks-update/" rel="noopener noreferrer"&gt;Ahrefs&lt;/a&gt;. Meanwhile Cursor, a code editor, went from $2B to over $4B in annualized revenue in about four months, according to press reports. Those two numbers sum up what AI did to making money on the web: services that do the work grow, sites that sell answers shrink.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short version:&lt;/strong&gt; I wouldn't start an ad-funded content site in 2026, and I wouldn't build a Cursor competitor either. For a solo developer or a small team, the realistic options are a narrow paid tool for one profession, or doing AI implementation work for companies.&lt;/p&gt;

&lt;p&gt;This is part 2 of a short series on how people make money with AI right now. &lt;a href="https://dev.to/klukyanov/where-the-money-is-in-ai-apps-in-2026-a-niche-map-343m"&gt;Part 1&lt;/a&gt; covered mobile apps; this one covers websites and web services.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's growing: tools that do the work
&lt;/h2&gt;

&lt;p&gt;The fastest money on the web this year is in tools that write code. Press reports put &lt;strong&gt;Cursor&lt;/strong&gt; above $1B in annualized revenue by late 2025, $2B by February 2026 and over $4B by June. These are leaks, not filings, since the company is private. Even with a wide margin of error, it's one of the fastest ramps in software history.&lt;/p&gt;

&lt;p&gt;Next come the builders, where you describe an app or site in plain language. &lt;strong&gt;Lovable&lt;/strong&gt; reached $400M ARR by February 2026, per TechCrunch, and later reports put it near $600M by September. &lt;strong&gt;Replit&lt;/strong&gt;'s CEO cited $240M in 2025 revenue, with a stated goal of a $1B run rate by the end of 2026.&lt;/p&gt;

&lt;p&gt;What they have in common: you pay for a result you can use, working code or a working site, not an answer to read. It's the same pattern as photo and video apps in part 1. People pay for things they can take away and use at work.&lt;/p&gt;

&lt;p&gt;The second growing group is narrow B2B tools in the browser: decks, meeting transcription, product photos, documents. Productivity takes 15 of 50 spots in a16z's top consumer AI products by spend, and many of those live on the web rather than in the App Store. Companies pay for them, so prices are higher and churn is lower.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's shrinking: sites that answered questions
&lt;/h2&gt;

&lt;p&gt;On the other side are sites that lived on search traffic. The &lt;a href="https://reutersinstitute.politics.ox.ac.uk/journalism-media-and-technology-trends-and-predictions-2026" rel="noopener noreferrer"&gt;Reuters Institute&lt;/a&gt;, using Chartbeat data, found organic Google traffic to 2,500+ publisher sites fell 33% worldwide and 38% in the US between November 2024 and November 2025. Reference content was hit hardest: weather, horoscopes, TV listings, simple how-tos. Chartbeat data reported by &lt;a href="https://www.axios.com/2026/03/17/chartbeat-search-traffic-ai-chatbots" rel="noopener noreferrer"&gt;Axios&lt;/a&gt; shows small publishers lost 60% of search referrals over two years, versus 22% for large ones.&lt;/p&gt;

&lt;p&gt;The main driver is the AI answer above the results. Your page keeps the top spot but loses the visitors.&lt;/p&gt;

&lt;p&gt;Two examples of what this looks like in money:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Chegg&lt;/strong&gt;, a homework-help service, got most of its subscribers from Google searches for study questions. Q4 2024 revenue fell 24%, it hired Goldman Sachs to explore a sale, and in February 2025 it &lt;a href="https://searchengineland.com/google-sued-by-chegg-over-ai-overviews-hurting-traffic-and-revenue-452518" rel="noopener noreferrer"&gt;sued Google&lt;/a&gt; over AI Overviews.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stack Overflow&lt;/strong&gt;'s monthly question volume fell back to 2009 levels, when the site had just launched. The decline started before ChatGPT, but sped up sharply after it shipped in late 2022.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Business models: what grows, what shrinks
&lt;/h2&gt;

&lt;p&gt;My estimate of the entry bar is for one developer or a small team. Figures come from different sources and are measured differently, so don't compare them directly.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Examples&lt;/th&gt;
&lt;th&gt;Trend and numbers&lt;/th&gt;
&lt;th&gt;Entry bar&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Growing&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dev tools and builders&lt;/td&gt;
&lt;td&gt;Cursor, Lovable, Replit, Bolt&lt;/td&gt;
&lt;td&gt;Cursor: $4B+ annualized by June 2026 (press)&lt;/td&gt;
&lt;td&gt;Closed: needs model budgets and investors&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Narrow B2B tool in the browser&lt;/td&gt;
&lt;td&gt;Gamma, Photoroom, Otter, Fireflies&lt;/td&gt;
&lt;td&gt;Productivity: 15 of 50 in a16z top-50&lt;/td&gt;
&lt;td&gt;Medium: best shot for a solo dev&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI implementation for clients&lt;/td&gt;
&lt;td&gt;Automation, chatbots, integrations&lt;/td&gt;
&lt;td&gt;Demand growing with company interest in AI (my estimate)&lt;/td&gt;
&lt;td&gt;Low: needs experience, not capital&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Flat&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Thin wrapper over someone else's model&lt;/td&gt;
&lt;td&gt;"One prompt plus a checkout"&lt;/td&gt;
&lt;td&gt;Repeating the fate of mobile wrappers (my estimate)&lt;/td&gt;
&lt;td&gt;Low, but ChatGPT and Gemini absorb the feature&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storefront for your own product or services&lt;/td&gt;
&lt;td&gt;Landing pages, portfolios, app pages&lt;/td&gt;
&lt;td&gt;Less from search, more from social, channels, newsletters (my estimate)&lt;/td&gt;
&lt;td&gt;Low: you bring the traffic yourself&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Shrinking&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ad-funded content site&lt;/td&gt;
&lt;td&gt;Reference, how-tos, disposable news&lt;/td&gt;
&lt;td&gt;−33% Google traffic worldwide, −60% for small publishers (Reuters Institute, Chartbeat)&lt;/td&gt;
&lt;td&gt;Low, but the visitors are leaving&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Affiliate reviews&lt;/td&gt;
&lt;td&gt;"Top 10 vacuums", comparison pages&lt;/td&gt;
&lt;td&gt;−58% clicks on position one with an AI answer (Ahrefs)&lt;/td&gt;
&lt;td&gt;Low, but the AI answer takes the click&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Q&amp;amp;A sites&lt;/td&gt;
&lt;td&gt;Chegg, Stack Overflow&lt;/td&gt;
&lt;td&gt;Chegg: −24% revenue in Q4 2024, lawsuit against Google&lt;/td&gt;
&lt;td&gt;Closed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Why some grow and others shrink
&lt;/h2&gt;

&lt;p&gt;The line comes down to one question: &lt;strong&gt;can AI deliver the result right inside the search box or chat window?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If a site's product is an answer, a text or a list, AI hands it out on its own and nobody clicks through. That's what happened to horoscopes, recipes, reference pages, reviews and homework answers. The site wrote a good answer, the search engine summarized it, and the ads on the site stopped getting impressions.&lt;/p&gt;

&lt;p&gt;If the product is an action, chat AI doesn't replace it. It makes it cheaper and faster. Code has to run, a deck has to be shown to a client, a meeting has to be recorded and summarized, a business process has to be wired into a CRM. That happens in a separate service, and people pay for it.&lt;/p&gt;

&lt;p&gt;The second takeaway: a website stops being a traffic source and becomes a storefront. People arrive from a channel, a newsletter, social media or a referral, not from a random search. You have to bring them yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  What could break this
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Model costs.&lt;/strong&gt; Builders like Lovable and Bolt pay for every model call. Users complain about credits burning fast, and margins are thin. If the provider raises prices or ships the same product, a business built on someone else's model takes the hit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The platform ships it.&lt;/strong&gt; ChatGPT already makes decks, spreadsheets and simple sites. What protects a narrow tool is depth: the customer's data, integrations, a workflow tuned to one profession.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Search will keep changing.&lt;/strong&gt; The traffic numbers cover 2024–2025. AI answers keep expanding, and a model that looks "flat" today may be shrinking a year from now.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd pick
&lt;/h2&gt;

&lt;p&gt;I wouldn't start an ad-funded content site now. Even a great page at position one gets fewer and fewer clicks, and better SEO won't fix that. I wouldn't build a Cursor competitor either: that race is between companies with billions in funding.&lt;/p&gt;

&lt;p&gt;A solo developer has two realistic paths. One is a narrow paid tool for a specific profession where AI removes the routine: marketplace sellers, accountants, lawyers, real-estate agents. It's the same logic as Cal AI in part 1, just in the browser and for businesses. The other is AI implementation for companies. That's what I do myself: automation and AI-powered services for businesses. Right now there's more demand for that than for "just a website".&lt;/p&gt;

&lt;p&gt;You still need a site. Treat it as a storefront you bring people to, not as a machine that collects traffic from Google.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/ai-web-money-models/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>saas</category>
      <category>seo</category>
      <category>startup</category>
    </item>
    <item>
      <title>Where the Money Is in AI Apps in 2026: A Niche Map</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Wed, 21 Oct 2026 11:23:25 +0000</pubDate>
      <link>https://dev.to/klukyanov/where-the-money-is-in-ai-apps-in-2026-a-niche-map-343m</link>
      <guid>https://dev.to/klukyanov/where-the-money-is-in-ai-apps-in-2026-a-niche-map-343m</guid>
      <description>&lt;p&gt;In 2025, people spent more money in regular apps than in games for the first time. Generative AI is the main reason. But if you're thinking of building "an AI app", the money is not where it looks like it is. Chat assistants are taken. Photo, video, voice, and AI tucked inside a daily habit are where people still pay. I build iOS apps, so I pulled together the numbers by niche and wrote down where a small team can still get in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short version:&lt;/strong&gt; don't build another assistant. Build something that produces a file people keep, or remove the boring step from a task people already do every day. The second one is the realistic bet for a solo developer.&lt;/p&gt;

&lt;p&gt;This is part 1 of a short series on how people make money with AI right now. This one is about mobile apps; part 2 covers websites and web services.&lt;/p&gt;

&lt;h2&gt;
  
  
  The market: there is money
&lt;/h2&gt;

&lt;p&gt;According to &lt;a href="https://sensortower.com/blog/state-of-mobile-2026" rel="noopener noreferrer"&gt;Sensor Tower's State of Mobile 2026&lt;/a&gt;, consumers spent $167B in apps in 2025, up 10.6%. Non-game app spending grew 21% and passed games, which grew 1.3%. Generative AI apps were downloaded 3.8B times (double the year before), and their in-app revenue nearly tripled to over $5B.&lt;/p&gt;

&lt;p&gt;Growth hasn't stopped. &lt;a href="https://sensortower.com/press/sensor-tower-state-of-ai-2026-report-global-time-spent-on-generative-ai-apps-projected-to-more-than-double-year-over-year" rel="noopener noreferrer"&gt;Sensor Tower projects&lt;/a&gt; AI apps will pass $4B in H1 2026, 36% more than H2 2025. Time spent doubled year over year, from 17.2B to 36B hours. More than 200,000 apps now mention AI in their descriptions.&lt;/p&gt;

&lt;p&gt;That last number matters most. With 200,000 apps saying "AI", the label on its own sells nothing. What sells is the job it does.&lt;/p&gt;

&lt;h2&gt;
  
  
  Chat assistants: the field is taken
&lt;/h2&gt;

&lt;p&gt;In Q1 2026, ChatGPT, DeepSeek and Google Gemini held almost 90% of time spent in AI assistant apps (Sensor Tower). &lt;a href="https://appfigures.com/resources/insights/20251121/amp?f=3" rel="noopener noreferrer"&gt;Appfigures estimates&lt;/a&gt; ChatGPT made $187M net on mobile in October 2025, with Grok at $8.7M, Claude at $5M and Perplexity at $3.1M. Even companies with their own frontier models are 20–40x behind.&lt;/p&gt;

&lt;p&gt;It wasn't always like this. In 2023–2024, thin wrappers did well: &lt;a href="https://appfigures.com/resources/insights/20250131/3-we-ranked-every-ai-app-and-here-are-the-highest-earners" rel="noopener noreferrer"&gt;Appfigures&lt;/a&gt; puts ChatOn at $135M and Chat &amp;amp; Ask AI at $109M over two years. That was before OpenAI and Google shipped good apps of their own, when people searched the App Store for "ChatGPT" and installed whatever came up first. Today the free original beats any wrapper. That's my read, not a finding from the reports.&lt;/p&gt;

&lt;h2&gt;
  
  
  The niche map
&lt;/h2&gt;

&lt;p&gt;Figures come from different sources and aren't directly comparable: some are net of store fees, some gross, some are company claims.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Niche&lt;/th&gt;
&lt;th&gt;Who earns&lt;/th&gt;
&lt;th&gt;Numbers&lt;/th&gt;
&lt;th&gt;Barrier for a small team&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;General-purpose assistants&lt;/td&gt;
&lt;td&gt;ChatGPT, Claude, Grok, Perplexity&lt;/td&gt;
&lt;td&gt;ChatGPT: $187M net in Oct 2025 (Appfigures)&lt;/td&gt;
&lt;td&gt;Closed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Video generation &amp;amp; avatars&lt;/td&gt;
&lt;td&gt;Higgsfield, HeyGen, Runway, Kling, Synthesia&lt;/td&gt;
&lt;td&gt;Higgsfield claims $1B annualized revenue (company claim)&lt;/td&gt;
&lt;td&gt;High: generation is expensive, margins thin&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Photo: editing, retouching, product shots&lt;/td&gt;
&lt;td&gt;Photoroom, Evoto, FaceApp, Reface, Topaz&lt;/td&gt;
&lt;td&gt;About ten photo tools in a16z's top 50 by spend&lt;/td&gt;
&lt;td&gt;Medium: a narrow job works&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Audio: music, voice, read-aloud&lt;/td&gt;
&lt;td&gt;Suno, ElevenLabs, Speechify, Moises&lt;/td&gt;
&lt;td&gt;Suno is #7 in a16z's top 50&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Productivity: meetings, notes, slides&lt;/td&gt;
&lt;td&gt;Otter, Plaud, Fireflies, Gamma, Notion&lt;/td&gt;
&lt;td&gt;15 of 50 spots in a16z's top 50&lt;/td&gt;
&lt;td&gt;Medium: higher prices, companies pay&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Companions &amp;amp; roleplay&lt;/td&gt;
&lt;td&gt;Zeta, Tipsy Chat, Character.AI&lt;/td&gt;
&lt;td&gt;$165M general + $163M romance in H1 2026, gross (Appfigures via Decrypt)&lt;/td&gt;
&lt;td&gt;Low technically, high on moderation and reputation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Homework &amp;amp; study&lt;/td&gt;
&lt;td&gt;Gauth (ByteDance), Question.AI&lt;/td&gt;
&lt;td&gt;~$2.5M net combined in 2024 on 15M installs (Appfigures)&lt;/td&gt;
&lt;td&gt;High: big players plus free ChatGPT&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI inside a daily habit: food, health, fitness&lt;/td&gt;
&lt;td&gt;Cal AI and narrow trackers&lt;/td&gt;
&lt;td&gt;Cal AI: $40M+ trailing-12-month sales, acquired by MyFitnessPal in March 2026&lt;/td&gt;
&lt;td&gt;Low–medium: best shot for a solo dev&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The a16z ranking is the &lt;a href="https://officechai.com/ai/top-consumer-apps-by-revenue/" rel="noopener noreferrer"&gt;top 50 consumer AI products&lt;/a&gt; by US consumer spend (October 2026, YipitData), web and mobile combined. More than half of the list is photo, video and audio.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why people pay for photo, video and voice
&lt;/h2&gt;

&lt;p&gt;My interpretation, but it fits the numbers.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The result is a file.&lt;/strong&gt; You read a chatbot answer and close it. A video, an edited photo or a voiceover gets saved, posted, sent to a client. It's easier to pay for something you can take away.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Free ChatGPT is worse at it.&lt;/strong&gt; A general assistant can draw a picture. It won't batch-remove backgrounds from forty product shots at marketplace size.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Professionals pay.&lt;/strong&gt; Marketplace sellers, photographers, creators and marketers treat these as work tools that pay for themselves.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The flip side is cost. Every video generation costs money, and an all-you-can-eat plan will put you in the red. Credits instead of unlimited, and expensive models only on the paid tier.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a solo developer fits: AI inside a habit
&lt;/h2&gt;

&lt;p&gt;The most telling story of the year is &lt;strong&gt;Cal AI&lt;/strong&gt;. Two high schoolers built a calorie counter by photo: snap your plate, get calories and protein. In under two years it passed 15M downloads, did over $40M in sales in the trailing 12 months, and MyFitnessPal bought it in March 2026 (terms undisclosed).&lt;/p&gt;

&lt;p&gt;The model inside isn't theirs, and food recognition isn't unique. What worked: AI removed the most tedious step of a task people already wanted to do. Counting calories was always the goal; typing in every spoonful was the problem.&lt;/p&gt;

&lt;p&gt;The recipe:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Pick a task people do regularly, daily or weekly.&lt;/li&gt;
&lt;li&gt;Find the most tedious step: data entry, transcription, counting.&lt;/li&gt;
&lt;li&gt;Let AI remove that step, and keep the rest a good ordinary app.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I do this in my own fasting app: calories from a photo are part of the daily log, and recognition runs on the phone through Apple Foundation Models, offline and with no API bill. When a request costs nothing, a free tier and a long trial don't turn into losses.&lt;/p&gt;

&lt;p&gt;A habit also fights the other AI-app problem, churn. People leave AI apps faster than regular ones, and what keeps them is the recurring task, not the model. I covered that in &lt;a href="https://dev.to/klukyanov/ai-apps-earn-more-but-lose-subscribers-faster-3d6l"&gt;an earlier breakdown of RevenueCat's data&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can break it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The platform eats your feature.&lt;/strong&gt; If your product is one button, it'll show up in ChatGPT, Google Photos or iOS itself. Data, history and a good workflow are what protect you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Store rules.&lt;/strong&gt; In April 2026 Apple briefly pulled Cal AI: it took payments via Stripe outside in-app purchase and showed the weekly price more prominently than the actual charge. It came back after fixes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cost.&lt;/strong&gt; A cloud model is a variable cost per user. Do the math before launch, not after the first invoice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Companions are their own thing.&lt;/strong&gt; Hundreds of millions in revenue, but the top 10% of apps take 89% of it (Appfigures, 2025), and moderation and reputational risk are the highest anywhere.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I'd pick
&lt;/h2&gt;

&lt;p&gt;Not an assistant, and not a video generator: the first is taken, the second needs model budgets a solo developer doesn't have. I'd take a boring recurring task in a niche where people already pay for apps (food, fitness, health, bookkeeping, photos for sellers), have AI remove the most tedious step, on-device where possible, and sell an annual plan with a long trial.&lt;/p&gt;

&lt;p&gt;Less exciting than "my own ChatGPT". But it's what the one real success story of the year looks like.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/ai-apps-money-map/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mobile</category>
      <category>startup</category>
      <category>ios</category>
    </item>
    <item>
      <title>AI apps earn more but lose subscribers faster</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Mon, 19 Oct 2026 14:45:33 +0000</pubDate>
      <link>https://dev.to/klukyanov/ai-apps-earn-more-but-lose-subscribers-faster-3d6l</link>
      <guid>https://dev.to/klukyanov/ai-apps-earn-more-but-lose-subscribers-faster-3d6l</guid>
      <description>&lt;p&gt;AI features make people pay faster. They also make people leave faster. RevenueCat's latest data shows AI subscription apps earn 41% more per paying user in year one, but only about one in five annual subscribers renews. For other apps it's closer to one in three. I build iOS apps with subscriptions, so I went through the numbers and wrote down what I'd actually change.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short version:&lt;/strong&gt; subscriptions are paid for by habit, not by the model inside the app. Judge an AI app by its second year, not its first month.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the numbers come from
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.revenuecat.com/state-of-subscription-apps" rel="noopener noreferrer"&gt;State of Subscription Apps 2026&lt;/a&gt; by RevenueCat, the company whose SDK handles roughly 20% of global subscription app revenue. The data covers 2025: 115,000+ apps, $16B+ in revenue, 1B+ transactions. An "AI app" here means one where AI is part of the core experience, which is 27% of the sample.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI vs non-AI apps
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;AI apps&lt;/th&gt;
&lt;th&gt;Non-AI apps&lt;/th&gt;
&lt;th&gt;Difference&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Revenue per payer, first month&lt;/td&gt;
&lt;td&gt;$18.92&lt;/td&gt;
&lt;td&gt;$13.59&lt;/td&gt;
&lt;td&gt;+39%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Revenue per payer, first year&lt;/td&gt;
&lt;td&gt;$30.16&lt;/td&gt;
&lt;td&gt;$21.37&lt;/td&gt;
&lt;td&gt;+41%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Trial start rate (of downloads)&lt;/td&gt;
&lt;td&gt;8.5%&lt;/td&gt;
&lt;td&gt;5.6%&lt;/td&gt;
&lt;td&gt;+52%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Paid by day 35 (of downloads)&lt;/td&gt;
&lt;td&gt;2.4%&lt;/td&gt;
&lt;td&gt;2.0%&lt;/td&gt;
&lt;td&gt;+20%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Annual plan renewal&lt;/td&gt;
&lt;td&gt;21.1%&lt;/td&gt;
&lt;td&gt;30.7%&lt;/td&gt;
&lt;td&gt;−9.6 pts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Monthly plan kept for 12 months&lt;/td&gt;
&lt;td&gt;6.1%&lt;/td&gt;
&lt;td&gt;9.5%&lt;/td&gt;
&lt;td&gt;−3.4 pts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Weekly plan kept for a year&lt;/td&gt;
&lt;td&gt;1.2%&lt;/td&gt;
&lt;td&gt;1.7%&lt;/td&gt;
&lt;td&gt;−0.5 pts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Refund rate (median)&lt;/td&gt;
&lt;td&gt;4.2%&lt;/td&gt;
&lt;td&gt;3.5%&lt;/td&gt;
&lt;td&gt;+0.7 pts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Share of monthly plans&lt;/td&gt;
&lt;td&gt;59.8%&lt;/td&gt;
&lt;td&gt;26.2%&lt;/td&gt;
&lt;td&gt;×2.3&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The top half of the table is about how well AI sells. People start trials more often, convert more often and pay more. The bottom half is about how well AI retains people, and it's worse on every line. Out of 100 annual subscribers, 21 come back for year two in an AI app and 31 in a regular one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why they leave
&lt;/h2&gt;

&lt;p&gt;The report gives the numbers, not the reasons. What follows is my own reading of them.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;People buy an effect, not a habit.&lt;/strong&gt; Generating an avatar or reading calories off a food photo is impressive the first time. If the job is one-off, there's no reason to come back. Across categories, 26–40% of voluntary cancellations cite "not using it enough".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Monthly plans.&lt;/strong&gt; 60% of AI subscriptions are monthly, compared with 26% for other apps. A monthly plan asks "still worth it?" every 30 days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expectations run ahead of results.&lt;/strong&gt; Refunds are higher, and the ceiling is higher too: 16% vs 12.5%. The ad promises magic, the model sometimes gets it wrong, and the user notices while a refund is still easy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Price.&lt;/strong&gt; Model costs push AI apps to higher prices, and "too expensive" is the top cancellation reason, at 25–45% depending on category.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Five things I'd do with an AI app
&lt;/h2&gt;

&lt;p&gt;Examples from my own apps are illustrations, not measurements.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Sell annual, not monthly.&lt;/strong&gt; Annual plans renew less often than you'd like, but you collect twelve months up front. If the user cools off in month three, a monthly plan just ends. The median annual price in the report is $34.80, up from $31.60.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Use long trials instead of 3-day ones.&lt;/strong&gt; Trials of 17+ days convert at 42.5% vs 25.5% for trials of four days or less. 55% of 3-day trial cancellations happen on day zero, so a short trial tests the wow moment, not the habit. In Clay Sniper, a shooting journal, I moved the Pro trial from three days to two weeks so a shooter gets at least a couple of range sessions in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Put AI inside a recurring job.&lt;/strong&gt; AI keeps users when it removes friction from something they do every week anyway, not when it's a standalone party trick. In Lunar Fasting, calories from a photo are one line in a daily log next to water, fasting and weight, not a separate "scan your food" screen.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Push marginal cost toward zero.&lt;/strong&gt; Every cloud request costs money, which is why AI apps tighten freemium, shorten trials and add expensive AI tiers. That fights tactic 2. In Lunar Fasting, photos can be analyzed on-device with Apple Foundation Models, offline and free. The cloud is only used with the user's own API key. If a request costs nothing, a long trial doesn't lose money.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Don't give away a free tier you don't need.&lt;/strong&gt; Hard paywalls convert 10.7% of downloads by day 35, freemium converts 2.1%, and annual retention is nearly identical (27% vs 28%). The paywall model decides how many people pay, not how many stay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Modeling the economics
&lt;/h2&gt;

&lt;p&gt;An AI app takes about 63% of its first-year revenue per payer in month one, roughly the same share as a non-AI app. The difference shows up only at renewal, outside a first-year window. If your ad bidding optimizes for short-horizon value, it's easy to overpay for AI users. Plan for a lower lifetime value than market averages suggest.&lt;/p&gt;

&lt;p&gt;One more detail from the report: on Google Play, 32% of cancellations are failed payments rather than a user decision. On the App Store it's 15%. Part of your "churn" may be fixed by a card-update reminder, not by the product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bottom line
&lt;/h2&gt;

&lt;p&gt;I wouldn't build the product around the model. Models get cheaper and more alike, and in a year your competitor will have the same one. I'd build around a job people come back to every week and let AI take the tedium out of it. Sell an annual plan with a long trial, run inference on the device where possible, and look at year-two revenue.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/ai-apps-churn/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>ai</category>
      <category>mobile</category>
      <category>business</category>
    </item>
    <item>
      <title>OpenAI dots: the agent that works while you sleep</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Sat, 17 Oct 2026 10:01:26 +0000</pubDate>
      <link>https://dev.to/klukyanov/openai-dots-the-agent-that-works-while-you-sleep-6p2</link>
      <guid>https://dev.to/klukyanov/openai-dots-the-agent-that-works-while-you-sleep-6p2</guid>
      <description>&lt;p&gt;A regular ChatGPT conversation lives as long as the tab is open. Close it, and everything waits for your next message. On September 29 at DevDay, OpenAI showed the opposite: an agent that keeps doing the job after you've gone to bed. OpenAI calls it a &lt;strong&gt;dot&lt;/strong&gt;. Each dot gets its own cloud computer with a browser, access to your apps, and its own memory, and it's on around the clock.&lt;/p&gt;

&lt;p&gt;I went through what dots can do at launch, how their permissions work, what they cost and where the limits are. I haven't run a dot myself yet. OpenAI's announcement page returned 403 while I was collecting material, so the facts below come from detailed write-ups that cite OpenAI's announcement and help center. The key numbers match across three or four sources; where there's only one source, I say so.&lt;/p&gt;

&lt;p&gt;This is a snapshot as of &lt;strong&gt;October 17, 2026&lt;/strong&gt;. Dots are rolling out gradually, and details will change.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a dot is
&lt;/h2&gt;

&lt;p&gt;A dot is a persistent AI agent inside ChatGPT, running on GPT-6 Astra (released September 3). Four things set it apart from a normal chat:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Its own computer.&lt;/strong&gt; A cloud machine with a browser that keeps running when you're not chatting. You can open it and watch what the agent is doing right now.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Access to your apps.&lt;/strong&gt; Mail, calendar, Slack, spreadsheets: 4,000+ services via plugins.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Its own memory.&lt;/strong&gt; A dot keeps notes separate from ChatGPT memory and learns from your corrections.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unprompted work.&lt;/strong&gt; When you don't give it anything, it looks for ways to help. OpenAI calls this proactive research.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every dot has a name, a look and a handle like &lt;code&gt;@yourname-dot&lt;/code&gt;. You can talk to it in ChatGPT on desktop and mobile, in Slack and Microsoft Teams, or call it by voice. Context carries across channels.&lt;/p&gt;

&lt;p&gt;The example everyone repeats from the launch: an early tester's dot found an invoice he had forgotten to send, assembled it from an email thread and sent it as a PDF — after he approved it. The last part is the important one.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works: computer, plugins and Codex
&lt;/h2&gt;

&lt;p&gt;A dot is a coordinator rather than a worker. It doesn't write code itself; it hands coding to Codex and heavy office work to ChatGPT Work. Those tasks show up as their own threads you can steer directly.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cloud computer.&lt;/strong&gt; Visible under Computers. You can hit &lt;em&gt;Take over&lt;/em&gt;, drive the browser yourself and hand control back. Sign-in forms send credentials to the remote browser without the model seeing them; reusing a saved password requires your confirmation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your computer.&lt;/strong&gt; Some sites block cloud browsers, so you can let a dot use your laptop via the ChatGPT desktop app (&lt;em&gt;Allow access&lt;/em&gt; / &lt;em&gt;Revoke access&lt;/em&gt;). One personal computer at a time, and it must be online with the app open.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plugins.&lt;/strong&gt; The same as ChatGPT, Work and Codex, with permissions per action: read email yes, send email no.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limits.&lt;/strong&gt; Talking to a dot doesn't count toward ChatGPT usage limits. Codex and Work tasks it starts do.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Memory: it learns, but you can't see the notes
&lt;/h2&gt;

&lt;p&gt;A dot draws on the conversation, relevant ChatGPT memory and its own notes. The notes are the most controversial part of the system: you &lt;strong&gt;can't view, correct or delete individual entries&lt;/strong&gt;. The only full reset is deleting the dot. Disconnecting a plugin stops new access but keeps what was already learned; turning off ChatGPT memory stops sharing but doesn't delete what the dot already received. Credentials, images and screenshots don't go into dot context.&lt;/p&gt;

&lt;p&gt;For an agent that reads your mail for months, the lack of a "forget this" button is a real gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four rules, and what a dot will never do on its own
&lt;/h2&gt;

&lt;p&gt;The core of dots isn't the model, it's the permission system. Under Custom rules, every action gets one of four modes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Take action without asking&lt;/strong&gt; — routine where mistakes cost nothing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Take action when you say so&lt;/strong&gt; — pre-approved, executed on your command.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask before taking action&lt;/strong&gt; — the dot prepares a draft and waits for your yes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hand off to you&lt;/strong&gt; — the dot gets the task to the point where a human is needed.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;On top of your rules sit limits you can't remove:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Password changes and money transfers&lt;/strong&gt; always go back to you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Purchases&lt;/strong&gt; need approval, and advance approval only works for a specific purchase.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Permanent deletion and software installs&lt;/strong&gt; may need approval every time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Auto-review&lt;/strong&gt; checks actions that touch accounts or share information, such as sending email, and can block, ask or stop. The dot can't turn it off.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Proactive research is read-only&lt;/strong&gt;: it can't send messages, change app content or control a browser.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Pause stops the main task but not necessarily delegated or scheduled work, and nothing is rolled back: a sent email stays sent.&lt;/p&gt;

&lt;h2&gt;
  
  
  The safety numbers
&lt;/h2&gt;

&lt;p&gt;From the GPT-6 Astra system card appendix, as reported in Flavio Copes's deep dive (the only source with the full set):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Prompt injection:&lt;/strong&gt; 100 runs of 500 simulated emails, 16,600 attacks — none succeeded.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Adaptive attacker:&lt;/strong&gt; 2,638 attempts, no success.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scope violations in chained tasks:&lt;/strong&gt; 8.6% with five tasks in between, 19.7% with ten. No severe breaches.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Permission changes mid-task:&lt;/strong&gt; adapted in all 17 explicit cases; passed 45 of 49 episodes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data exfiltration&lt;/strong&gt; by human red-teamers: all attempts failed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The third line is the one I care about. In a chain of ten tasks, almost one time in five the agent steps outside its brief. That's not a hack, it's an agent forgetting what it was asked — and long chains of tasks over weeks are exactly how a dot is meant to work. OpenAI says it plainly: "Dots can still make mistakes, so always review consequential work."&lt;/p&gt;

&lt;h2&gt;
  
  
  Who gets it and what it costs
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;Dots&lt;/th&gt;
&lt;th&gt;Price&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Free, Go, Plus&lt;/td&gt;
&lt;td&gt;No, no date&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pro&lt;/td&gt;
&lt;td&gt;One dot; not in the EEA, UK or Switzerland&lt;/td&gt;
&lt;td&gt;from $100/month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Business Premium&lt;/td&gt;
&lt;td&gt;One dot, all supported regions&lt;/td&gt;
&lt;td&gt;$100/user/month annually, $125 monthly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Enterprise, Edu, Healthcare&lt;/td&gt;
&lt;td&gt;Beta, off until an admin enables it&lt;/td&gt;
&lt;td&gt;via sales&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The first dot is included, with extended limits for the first month after launch. Post-launch limits, extra dots and extra capacity have no published prices yet. Setup is desktop-only, and users under 18 can't use dots.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dots vs. the competition
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Product&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Difference from dots&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;OpenAI dots&lt;/td&gt;
&lt;td&gt;One always-on coordinator with its own cloud computer, 4,000+ apps&lt;/td&gt;
&lt;td&gt;Delegates to Codex and Work, strict rules, no API&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Grok Bot&lt;/td&gt;
&lt;td&gt;Closest match: persistent cloud computer, scheduled work, asks before sensitive actions&lt;/td&gt;
&lt;td&gt;Several named Bots instead of one agent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cursor Projects&lt;/td&gt;
&lt;td&gt;Coordinator for long-running coding work&lt;/td&gt;
&lt;td&gt;Coding only, returns pull requests&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Meta Muse&lt;/td&gt;
&lt;td&gt;Consumer assistant for errands, travel and forms via the Muse app and WhatsApp&lt;/td&gt;
&lt;td&gt;Free for most uses; a small-business version launched on DevDay&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This comparison is based on product descriptions, not measurements.&lt;/p&gt;

&lt;h2&gt;
  
  
  What dots can't do yet
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No email address of their own.&lt;/li&gt;
&lt;li&gt;Can't call you; texting is a narrow beta for some US Pro users.&lt;/li&gt;
&lt;li&gt;One primary dot per person; teams of dots are planned.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No API.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;No way to inspect or clean memory entry by entry.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A developer's view: no API is a signal
&lt;/h2&gt;

&lt;p&gt;I build apps and agents, so the first thing I looked for was a way to talk to a dot from code. There isn't one: OpenAI hasn't announced an API for dots. It's a ChatGPT product, not a developer platform.&lt;/p&gt;

&lt;p&gt;The Codex link is telling, though. A dot can start a task in a Codex cloud environment while your computer is off, send work to your connected machine, or continue an existing Codex thread. OpenAI is building a hierarchy: on top, an agent that knows you and your work; below, specialized executors. If you build agents yourself, selling "an assistant that does everything" just got harder, while a niche executor with a clear interface is still in demand.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd hand to a dot
&lt;/h2&gt;

&lt;p&gt;A good dot task is recurring, spans several apps and ends in a draft:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every Friday at 4 pm, match delivered projects to invoices, draft missing invoices, send nothing, message me a list.&lt;/li&gt;
&lt;li&gt;Watch the Leads label, draft replies, ask before sending, flag anyone silent for 48 hours in Slack.&lt;/li&gt;
&lt;li&gt;Weekly, compare stock with reorder levels and draft purchase orders for approval. Never place orders.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A bad task is one where mistakes can't be undone: money, passwords, unchecked emails to important people. Not because the dot is dumb, but because 19.7% out-of-scope on long chains is a lot for irreversible actions. Treat it like a new assistant: drafts first, then widen permissions one at a time.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/openai-dots/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>openai</category>
      <category>agents</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Swift on Android, part 1: what the official SDK does and how it differs from KMP</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Tue, 13 Oct 2026 13:13:12 +0000</pubDate>
      <link>https://dev.to/klukyanov/swift-on-android-part-1-what-the-official-sdk-does-and-how-it-differs-from-kmp-574b</link>
      <guid>https://dev.to/klukyanov/swift-on-android-part-1-what-the-official-sdk-does-and-how-it-differs-from-kmp-574b</guid>
      <description>&lt;p&gt;I ship an app on Kotlin Multiplatform, and when I counted the lines, the shared Kotlin code turned out to be just 14% of the codebase. So here's the question I keep asking myself as an iOS developer: what if the shared code had been Swift running on Android, instead of Kotlin running on iPhone? Since Swift 6.3 that's an officially supported option.&lt;/p&gt;

&lt;p&gt;This is part 1 of a three-part series. Here I cover what actually shipped, how it works, what's in the Swift SDK for Android and what isn't, and how it compares to KMP feature by feature. Part 2 is hands-on, and part 3 is an honest side-by-side on a real app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I care
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://klukyanov.ru/projects/carcode/?theme=dark" rel="noopener noreferrer"&gt;MyCarCode&lt;/a&gt;, my car maintenance log, is built with Kotlin Multiplatform: shared logic in Kotlin, native UI on both sides (SwiftUI and Jetpack Compose, each with its own Flux stores). At build 8 I counted:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;shared Kotlin code (&lt;code&gt;commonMain&lt;/code&gt;): &lt;strong&gt;1,574 lines&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;iOS UI and stores: &lt;strong&gt;~9.8k lines of Swift&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Android UI and stores: &lt;strong&gt;~9.6k lines of Kotlin&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's roughly 14% shared code. For that 14% I paid with a second language on the iOS side, Gradle running inside the Xcode build, and a long fight with Firebase linking. If I mentally write the logic in Swift anyway, maybe Swift should be the one traveling.&lt;/p&gt;

&lt;h2&gt;
  
  
  What shipped and when
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;June 2025.&lt;/strong&gt; The Swift project announced the Android Workgroup.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;October 24, 2025.&lt;/strong&gt; First nightly previews of the Swift SDK for Android on swift.org.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;March 24, 2026.&lt;/strong&gt; Swift 6.3: the "first official release of the Swift SDK for Android."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;September 15, 2026.&lt;/strong&gt; Swift 6.4, a day after Xcode 27. The getting-started guide currently targets SDK 6.4.1.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Important: this isn't Apple shipping Swift for Android. It's the open-source Swift project and its workgroup. SwiftUI, UIKit and Apple frameworks don't come along.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;The SDK is a cross-compilation kit. You write a regular Swift package on macOS or Linux, and &lt;code&gt;swift build&lt;/code&gt; targets Android instead of macOS. It relies on the Android NDK (the guide asks for LTS r30). The examples use &lt;code&gt;aarch64&lt;/code&gt; (devices) and &lt;code&gt;x86_64&lt;/code&gt; (emulator) with API level 23.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# 1. Swift toolchain matching the SDK version&lt;/span&gt;
swiftly &lt;span class="nb"&gt;install &lt;/span&gt;latest

&lt;span class="c"&gt;# 2. The Android SDK itself&lt;/span&gt;
swift sdk &lt;span class="nb"&gt;install&lt;/span&gt; &amp;lt;archive-url&amp;gt; &lt;span class="nt"&gt;--checksum&lt;/span&gt; &amp;lt;sha256&amp;gt;
swift sdk list   &lt;span class="c"&gt;# swift-6.4.1-RELEASE_android&lt;/span&gt;

&lt;span class="c"&gt;# 3. Android NDK r30&lt;/span&gt;
&lt;span class="nb"&gt;export &lt;/span&gt;&lt;span class="nv"&gt;ANDROID_NDK_HOME&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$PWD&lt;/span&gt;/android-ndk-r30
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The output is a native &lt;code&gt;.so&lt;/code&gt; per architecture. It isn't an app on its own: the app stays a regular Kotlin/Java Android project, the library ships inside the APK, and Kotlin calls into Swift through &lt;strong&gt;swift-java&lt;/strong&gt;, the official bridge and code generator that produces Java wrappers over JNI.&lt;/p&gt;

&lt;p&gt;It's a mirror image of KMP. In KMP, Android is home and Kotlin travels to iPhone as a native framework talking to Swift through Objective-C headers. With the Swift SDK, iOS is home and Swift travels to Android, talking to Kotlin through JNI.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in the box
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The whole language.&lt;/strong&gt; Same Swift 6.4 compiler, strict concurrency, &lt;code&gt;async/await&lt;/code&gt;, actors, macros. No "lite dialect."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Standard library and Foundation.&lt;/strong&gt; Dates, strings, &lt;code&gt;Codable&lt;/code&gt;, JSON. Networking (&lt;code&gt;URLSession&lt;/code&gt;) lives in &lt;code&gt;FoundationNetworking&lt;/code&gt; off Apple platforms and is imported explicitly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Swift packages.&lt;/strong&gt; Anything that already builds on Linux and doesn't pull in Apple frameworks has a good chance of building for Android.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A two-way bridge.&lt;/strong&gt; swift-java can call Swift from Kotlin and Java classes from Swift. Async Swift functions surface in Java as &lt;code&gt;CompletableFuture&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real-world proof.&lt;/strong&gt; Skip Fuse builds whole SwiftUI apps for Android on top of this same official SDK.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's missing
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;UI.&lt;/strong&gt; No SwiftUI or UIKit on Android. Screens are Jetpack Compose; Swift stays under the hood (unless you adopt Skip and its rules).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apple frameworks.&lt;/strong&gt; SwiftData, Core Data, StoreKit, HealthKit, Combine stay on iPhone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Service SDKs in Swift.&lt;/strong&gt; Firebase, Google Sign-In, payments have Kotlin libraries for Android and Swift libraries for iOS, but no Swift build for Android. From shared Swift code you reach them through the Java bridge or Skip's wrappers. For MyCarCode, whose whole data layer sits on Firestore, this is the big one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Comfortable debugging.&lt;/strong&gt; It's a stated workgroup goal, but "set a breakpoint in Android Studio and step into Swift" isn't there yet. From the Android side the debugger sees generated Java wrappers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A mature bridge.&lt;/strong&gt; Early adopters report that every Swift error reaches Kotlin as a plain &lt;code&gt;java.lang.Exception&lt;/code&gt;, and swift-java has open issues around async functions with generic results.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Swift SDK vs. KMP, feature by feature
&lt;/h2&gt;

&lt;p&gt;This is based on documentation and other people's experience, not my measurements. My numbers come in part 3.&lt;/p&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;Swift SDK for Android&lt;/th&gt;
&lt;th&gt;Kotlin Multiplatform&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Shared language&lt;/td&gt;
&lt;td&gt;Swift&lt;/td&gt;
&lt;td&gt;Kotlin&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Status&lt;/td&gt;
&lt;td&gt;Official since Swift 6.3 (March 2026)&lt;/td&gt;
&lt;td&gt;Stable since November 2023&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Home platform&lt;/td&gt;
&lt;td&gt;iOS (Android is the guest)&lt;/td&gt;
&lt;td&gt;Android (iOS is the guest)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Guest artifact&lt;/td&gt;
&lt;td&gt;Native &lt;code&gt;.so&lt;/code&gt; per ABI inside the APK&lt;/td&gt;
&lt;td&gt;Native &lt;code&gt;.framework&lt;/code&gt; via Kotlin/Native&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Language bridge&lt;/td&gt;
&lt;td&gt;swift-java over JNI, generated Java wrappers&lt;/td&gt;
&lt;td&gt;Objective-C headers, SKIE, experimental Swift export&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Async&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;async&lt;/code&gt; → &lt;code&gt;CompletableFuture&lt;/code&gt; in Java&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;suspend&lt;/code&gt; → &lt;code&gt;async/await&lt;/code&gt; in Swift (via SKIE)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Errors&lt;/td&gt;
&lt;td&gt;Arrive in Kotlin as &lt;code&gt;java.lang.Exception&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Without &lt;code&gt;@Throws&lt;/code&gt;, an exception crashes the iOS app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shared UI&lt;/td&gt;
&lt;td&gt;None (only via third-party Skip)&lt;/td&gt;
&lt;td&gt;Compose Multiplatform, stable on iOS since 2025&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Libraries&lt;/td&gt;
&lt;td&gt;Swift packages that build off Apple platforms&lt;/td&gt;
&lt;td&gt;Own ecosystem: Ktor, kotlinx, Koin, SQLDelight&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Firebase in shared code&lt;/td&gt;
&lt;td&gt;No native build; bridge or Skip&lt;/td&gt;
&lt;td&gt;Yes: GitLive Firebase SDK (unofficial)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Debugging shared code&lt;/td&gt;
&lt;td&gt;Good from iOS, weak from Android&lt;/td&gt;
&lt;td&gt;Good from Android, weaker from iOS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fits best&lt;/td&gt;
&lt;td&gt;iOS-first teams&lt;/td&gt;
&lt;td&gt;Android-first teams&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In one sentence: both solve the same problem from opposite shores. Both share logic, not screens (Compose Multiplatform and Skip aside). Both make one platform live with a foreign language and a bridge. The difference is which team feels the bridge, and that KMP has two and a half more years of scars and libraries.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who should try it now
&lt;/h2&gt;

&lt;p&gt;My preliminary take, before installing anything myself:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Yes&lt;/strong&gt;, if you have an iOS app with heavy logic that doesn't depend on services: calculations, parsers, validation, file formats, an offline engine. That code can go to Android nearly as is.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Yes&lt;/strong&gt;, if your team is all-Swift and the Android version just needs to exist. Skip on top of the official SDK is the shortest path.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not yet&lt;/strong&gt;, if your shared layer is built on Firebase and other service SDKs. You'll be bridging to their Android versions, and the savings end there. KMP with ready-made wrappers is ahead.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not yet&lt;/strong&gt;, if your team is mostly Android developers who'd have to debug Swift through generated Java wrappers. KMP will feel like home to them.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's next in the series
&lt;/h2&gt;

&lt;p&gt;Docs tell half the story. They won't tell you how much a Swift library actually weighs inside an APK, how long the first setup takes, or where the bridge breaks on real code rather than "Hello, Android."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;In part 2&lt;/strong&gt; I install the SDK on my Mac and try to build real logic from one of my apps for Android: actual models and calculations that live on iPhone today. What compiles on the first try, what needs rewriting, how big the result is, and whether I can call it from Compose at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;In part 3&lt;/strong&gt;: an honest comparison with KMP on MyCarCode. I kept a full log of what broke when Kotlin moved to iPhone: hand-unpacking Firebase into frameworks, duplicate symbols at link time, a crash caused by one forgotten annotation, and a bug where a screen wouldn't close itself after saving because the Kotlin code resumed on the wrong thread. I'll go through which of those the Swift SDK removes and which it just moves to the other shore.&lt;/p&gt;

&lt;p&gt;A spoiler I'm not sure about yet: some of those rakes will turn out to be mirror images. We'll see.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/swift-android-sdk/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>swift</category>
      <category>android</category>
      <category>kotlin</category>
      <category>ios</category>
    </item>
    <item>
      <title>ASO on my own apps: what actually moved App Store impressions in a month</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Mon, 12 Oct 2026 12:46:34 +0000</pubDate>
      <link>https://dev.to/klukyanov/aso-on-my-own-apps-what-actually-moved-app-store-impressions-in-a-month-4jpi</link>
      <guid>https://dev.to/klukyanov/aso-on-my-own-apps-what-actually-moved-app-store-impressions-in-a-month-4jpi</guid>
      <description>&lt;p&gt;A month ago, almost nobody in the US or Europe could see my clay shooting app on the App Store: 97% of its impressions came from Russia, Kazakhstan and random countries. Today two thirds of impressions come from the US and Europe, and daily impressions are up 5×. And my Mac app went from #130 to #9 for "eye strain" in the UK store.&lt;/p&gt;

&lt;p&gt;Here is how I approach ASO as a solo developer, what I actually changed, what moved, what didn't, and what's next. Two live examples: &lt;strong&gt;Clay Sniper&lt;/strong&gt; (iPhone + Apple Watch, a log for trap, skeet and sporting clays) and &lt;strong&gt;SafeYourEye&lt;/strong&gt; (Mac, eye breaks and self-check vision tests).&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;About the numbers.&lt;/strong&gt; All volume metrics below (impressions, page views, installs, ratings) are multiplied by the same constant. I don't publish real values, but proportions and dynamics are exact. Search rankings are real: a position says nothing about money. Revenue, subscriptions and ad budget are not shown at all.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What ASO is made of
&lt;/h2&gt;

&lt;p&gt;ASO has two halves, and the order matters:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Being found&lt;/strong&gt; — search ranking.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Being chosen&lt;/strong&gt; — conversion from impression to page view to install.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Improving conversion is pointless while nobody sees the product page.&lt;/p&gt;

&lt;p&gt;Search on the App Store is driven by a few fields:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Name&lt;/strong&gt; — 30 characters, the heaviest weight.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subtitle&lt;/strong&gt; — 30 characters, second by weight.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keywords&lt;/strong&gt; — 100 characters, comma-separated, invisible to users.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Localizations&lt;/strong&gt; — each language has its own set of these three fields. And each storefront also indexes several &lt;em&gt;other&lt;/em&gt; locales: the US store reads es-MX, ru, zh-Hans, fr-FR and more on top of en-US. That's cross-localization: free extra keyword space.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Conversion is driven by screenshots, the App Preview video, ratings and &lt;strong&gt;Custom Product Pages&lt;/strong&gt; (alternative versions of your page for different queries and ad groups). &lt;strong&gt;Promotional text&lt;/strong&gt; (170 characters above the description) can be changed without review — leaving it empty means wasting a free lever.&lt;/p&gt;

&lt;h2&gt;
  
  
  The process: seven steps
&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;Step&lt;/th&gt;
&lt;th&gt;What I do&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Baseline&lt;/td&gt;
&lt;td&gt;Impressions, page views, installs by source and country (&lt;code&gt;asc analytics&lt;/code&gt;); rankings for 20–40 queries per target country&lt;/td&gt;
&lt;td&gt;Without a "before", there's no proof. Apple keeps daily analytics for ~9 days, so I collect it weekly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Pick markets&lt;/td&gt;
&lt;td&gt;Decide where the app should grow and where to leave it as is&lt;/td&gt;
&lt;td&gt;Keywords, locales and screenshots target specific storefronts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Build the semantic core&lt;/td&gt;
&lt;td&gt;App Store search suggestions, iTunes Search API results, competitor metadata, terms from the app's own code&lt;/td&gt;
&lt;td&gt;Without paid tools you can't measure query volume, so I look at competition: how many apps rank and how relevant they are&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Duplicate audit&lt;/td&gt;
&lt;td&gt;Overlap between name, subtitle and keywords&lt;/td&gt;
&lt;td&gt;A word repeated in keywords is wasted characters. In SafeYourEye, duplicates ate a third of the field&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Spread across locales&lt;/td&gt;
&lt;td&gt;Own name, subtitle, keywords per storefront language, plus a second keyword pool via cross-localization&lt;/td&gt;
&lt;td&gt;Without its own locale, a storefront shows the default language — sometimes Russian&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Ship and amplify&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;asc metadata push&lt;/code&gt; with the release, promotional text right away, Custom Product Pages for key queries&lt;/td&gt;
&lt;td&gt;Metadata lives in the repo, so every change is a diff&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Measure in 1–2 weeks&lt;/td&gt;
&lt;td&gt;Repeat step 1, compare per country and per query&lt;/td&gt;
&lt;td&gt;Indexing takes days; looking earlier means reading noise&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All of this is wrapped into a Claude Code skill and a dashboard: one weekly command pulls App Store analytics for all my apps, rankings across target storefronts and a metadata snapshot with change history, through the official App Store Connect API.&lt;/p&gt;

&lt;h2&gt;
  
  
  Starting point: nobody saw the page
&lt;/h2&gt;

&lt;p&gt;Clay sports live mostly in the US and Europe. In mid-September Clay Sniper looked like this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;72% of impressions from Russia and Kazakhstan&lt;/strong&gt;, a quarter from random countries, 3% from the US and Europe.&lt;/li&gt;
&lt;li&gt;Three locales: ru, en-US, de-DE. The primary language was Russian, so &lt;strong&gt;France and Italy saw the Russian page&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Not in the US top 100 for "trap shooting", "sporting clays", "skeet".&lt;/li&gt;
&lt;li&gt;Zero Custom Product Pages, empty promotional text, no review prompt in the code.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The diagnosis in one line: &lt;strong&gt;no sales not because the page fails to convince, but because almost nobody sees it.&lt;/strong&gt; The funnel wasn't leaking — it was tiny at the top. So: reach first, conversion second, paid traffic third.&lt;/p&gt;

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

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Date&lt;/th&gt;
&lt;th&gt;Version&lt;/th&gt;
&lt;th&gt;Change&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Aug 23&lt;/td&gt;
&lt;td&gt;1.1.0&lt;/td&gt;
&lt;td&gt;Keywords rewritten around disciplines: "double, compact, fitasc, 5stand, scorecard" instead of generic "shooting, range, gun, hunting". First promotional text&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sep 21&lt;/td&gt;
&lt;td&gt;1.2.0&lt;/td&gt;
&lt;td&gt;German locale&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sep 26&lt;/td&gt;
&lt;td&gt;1.3.0&lt;/td&gt;
&lt;td&gt;French locale: "ball-trap", "carnet de tir", "compak"&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 1&lt;/td&gt;
&lt;td&gt;1.4.1&lt;/td&gt;
&lt;td&gt;en-GB with British terms ("DTL", "clay pigeon", "cartridges"), Italian. en-US keywords cleaned of words already in the subtitle&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 6&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;Apple Ads pilot in the US: competitor and niche queries, exact match&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 7&lt;/td&gt;
&lt;td&gt;1.4.2&lt;/td&gt;
&lt;td&gt;es-ES and es-MX (a second keyword pool for the US). 8 locales total&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 8&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;Apple approved 12 Custom Product Pages (trap, skeet, sporting, Apple Watch, stats…) in under a day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 11&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;All 12 Custom Product Pages got versions in six more storefront languages, with their own keywords and screenshots&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Both apps also got a system review prompt after a good moment (in Clay Sniper — a finished session). Ratings doubled over the period, average 5.0.&lt;/p&gt;

&lt;p&gt;For SafeYourEye the audit found two problems: a third of the keyword field duplicated the name, and the app's real differentiator — vision self-checks on a Mac (acuity, contrast, astigmatism, Amsler grid) — wasn't searchable at all. For queries like "visual acuity" and "amsler grid", there are only 12–24 apps in results, almost none about Mac vision checks; for "Sehtest" in Germany we're the only one. New name: &lt;strong&gt;"SafeYourEye: Eye Strain Timer"&lt;/strong&gt;, subtitle &lt;strong&gt;"20-20-20 Break &amp;amp; Vision Test"&lt;/strong&gt;, plus en-GB, fr-FR and it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dynamics
&lt;/h2&gt;

&lt;p&gt;Clay Sniper, daily averages by week (volumes scaled):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Week&lt;/th&gt;
&lt;th&gt;Impressions/day&lt;/th&gt;
&lt;th&gt;Page views/day&lt;/th&gt;
&lt;th&gt;Impression → page&lt;/th&gt;
&lt;th&gt;New installs/day&lt;/th&gt;
&lt;th&gt;US + Europe share&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Sep 16–20&lt;/td&gt;
&lt;td&gt;1,020&lt;/td&gt;
&lt;td&gt;80&lt;/td&gt;
&lt;td&gt;7.8%&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;3%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sep 21–27&lt;/td&gt;
&lt;td&gt;1,193&lt;/td&gt;
&lt;td&gt;71&lt;/td&gt;
&lt;td&gt;6.0%&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;25%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sep 28 – Oct 4&lt;/td&gt;
&lt;td&gt;1,246&lt;/td&gt;
&lt;td&gt;286&lt;/td&gt;
&lt;td&gt;22.9%&lt;/td&gt;
&lt;td&gt;21&lt;/td&gt;
&lt;td&gt;30%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 5–7&lt;/td&gt;
&lt;td&gt;992&lt;/td&gt;
&lt;td&gt;83&lt;/td&gt;
&lt;td&gt;8.4%&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;36%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Oct 8–10&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;4,867&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;192&lt;/td&gt;
&lt;td&gt;3.9%&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;68%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Geography flipped.&lt;/strong&gt; The main result: target markets went from 3% to 68% of impressions. Locales started working.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Installs appeared.&lt;/strong&gt; Zero new installs in the week of Sep 16–20, every week since Sep 21.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The late-September spike was a one-off.&lt;/strong&gt; It matched the 1.4.0/1.4.1 releases, but conversion returned to 8% a week later. At these volumes I can't separate the metadata effect from noise, so I don't try.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A jump from October 8.&lt;/strong&gt; Daily impressions grew 5×, almost all of it from the US and the UK. That same day Apple approved the 12 Custom Product Pages and my Apple Ads groups were switched to them. How much is ads vs. organic, the Apple Ads report will tell — next time. Page-view conversion dropped to 3.9%: the new audience sees the app but doesn't open it yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apple backfills data.&lt;/strong&gt; The first pull showed October 8 as almost empty; the next one showed it as the peak of the week. Don't draw conclusions from the last 2–3 days.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;SafeYourEye gets fewer impressions (Mac App Store search is smaller): 105–185 a day, and &lt;strong&gt;zero new installs in a month&lt;/strong&gt;. People find the page and don't open it. That's a conversion problem now, not a search one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rankings, before and after
&lt;/h2&gt;

&lt;p&gt;Positions via iTunes Search API (close to the real App Store, not identical). "—" means not in the top 200. Before: Sep 23–27; after: Oct 9 for SafeYourEye, Oct 12 for Clay Sniper.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;App&lt;/th&gt;
&lt;th&gt;Country&lt;/th&gt;
&lt;th&gt;Query&lt;/th&gt;
&lt;th&gt;Before&lt;/th&gt;
&lt;th&gt;After&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;UK&lt;/td&gt;
&lt;td&gt;eye strain&lt;/td&gt;
&lt;td&gt;130&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;9&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;Germany&lt;/td&gt;
&lt;td&gt;eye strain&lt;/td&gt;
&lt;td&gt;83&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;13&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;US&lt;/td&gt;
&lt;td&gt;eye strain&lt;/td&gt;
&lt;td&gt;170&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;39&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;Germany&lt;/td&gt;
&lt;td&gt;eye health&lt;/td&gt;
&lt;td&gt;126&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;France / Italy&lt;/td&gt;
&lt;td&gt;pause yeux / pausa occhi&lt;/td&gt;
&lt;td&gt;no locale&lt;/td&gt;
&lt;td&gt;7 / 5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;US&lt;/td&gt;
&lt;td&gt;20-20-20 rule&lt;/td&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SafeYourEye&lt;/td&gt;
&lt;td&gt;US&lt;/td&gt;
&lt;td&gt;eye care timer&lt;/td&gt;
&lt;td&gt;39&lt;/td&gt;
&lt;td&gt;100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;td&gt;US&lt;/td&gt;
&lt;td&gt;clay shooting&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;29&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;td&gt;Germany&lt;/td&gt;
&lt;td&gt;Tontaubenschießen&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;8&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;td&gt;France&lt;/td&gt;
&lt;td&gt;ball trap&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;106&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;td&gt;UK&lt;/td&gt;
&lt;td&gt;clay pigeon&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;45&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;td&gt;Germany&lt;/td&gt;
&lt;td&gt;Wurfscheiben&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clay Sniper&lt;/td&gt;
&lt;td&gt;US&lt;/td&gt;
&lt;td&gt;trap shooting / sporting clays&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;125 / 108&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;There are wins and losses here, and that's the honest price of a decision. Swapping "Eye Care Timer" for "Eye Strain Timer" in the name lifted the broad query in three countries and dropped the narrow ones. The broad query brings more impressions, so it's a good trade — but if you only look at winners, ASO looks like pure growth.&lt;/p&gt;

&lt;p&gt;Clay Sniper's head terms in the US, "trap shooting" and "sporting clays", have only just entered the top 200: niche leaders like HotClays sit there, and those words are only in my subtitle. "Clay shooting" holds in the 20s, but it jumps day to day (35th, 18th, 29th within four days), so I trust weekly trends, not single measurements. In the new locales "shooting log" (UK), "Wurftaube" (Germany) and "strozzatore" (Italy) landed in the top 5 right away.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Locales beat keyword polishing.&lt;/strong&gt; The biggest shift came not from tuning 100 characters but from the page speaking the storefront's language.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Custom Product Pages only accept words from the keywords field.&lt;/strong&gt; Words from the name and subtitle can't be assigned. My two main pages, trap and skeet, ended up with zero US keywords. Plan your field split with future pages in mind.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Impressions and installs are different problems.&lt;/strong&gt; SafeYourEye climbed in search and got zero installs. Search brings people to the page; the page has to do the convincing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Finish metadata before submitting for review.&lt;/strong&gt; While a version is waiting for review, you can't add a new locale. I once had to withdraw a submission to add languages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No baseline, no proof.&lt;/strong&gt; Apple keeps daily analytics for about nine days. If you don't collect regularly, a month later there's nothing to compare against.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Clay Sniper has a 90-day plan until December 22. The locale goal (7) is already exceeded with 8. The rest:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Keywords for Custom Product Pages&lt;/strong&gt; — reshuffle words between fields so trap and skeet pages get their own queries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A storefront for Western markets&lt;/strong&gt; — demo data in US/UK screenshots still shows Russian clubs and ammo; reshoot it and add an App Preview to the main page with the next version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Community&lt;/strong&gt; — emails to federations and clubs in the US, UK, France and Italy with free access via offer codes, each link with its own campaign token.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apple Ads&lt;/strong&gt; — US pilot first, then the UK; money decisions only on numbers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SafeYourEye&lt;/strong&gt; — fix conversion: first two screenshots, promotional text, video.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The rest of my apps&lt;/strong&gt; — two of them still rank nowhere, even for their own name. They're next.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal by year-end: 3× daily impressions vs. the start and 5× more ratings than today. I'll report back in a month.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/aso-app-store/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>appstore</category>
      <category>marketing</category>
      <category>indiedev</category>
    </item>
    <item>
      <title>An AI film crew made our app ad: who did what</title>
      <dc:creator>Kirill Lukyanov</dc:creator>
      <pubDate>Fri, 09 Oct 2026 11:13:17 +0000</pubDate>
      <link>https://dev.to/klukyanov/an-ai-film-crew-made-our-app-ad-who-did-what-1f6e</link>
      <guid>https://dev.to/klukyanov/an-ai-film-crew-made-our-app-ad-who-did-what-1f6e</guid>
      <description>&lt;p&gt;Seventeen seconds: a red-haired champion, a jittery rookie, tea from a tartan thermos and a shot at sunrise. There isn't a single real frame in this ad. AI agents wrote it, cast it, shot it and cut it, each in its own role. My job was to approve things and reject things.&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%2F3wqf2pg7e6smaoq7j7di.jpg" 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%2F3wqf2pg7e6smaoq7j7di.jpg" alt="Four frames from the generated ad: the Legend and the Rookie in armchairs on a trap range, the Legend saying " width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch the ad (9:16, 1080×1920, 20.6 s, sound on):&lt;/strong&gt; &lt;a href="https://storage.yandexcloud.net/klukyanov-ru-media/video/clay-sniper-ai-ad.mp4" rel="noopener noreferrer"&gt;clay-sniper-ai-ad.mp4&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The ad is for &lt;a href="https://apps.apple.com/app/clay-sniper/id6774298651" rel="noopener noreferrer"&gt;Clay Sniper&lt;/a&gt;, my iPhone and Apple Watch logbook for clay shooters. It took three days, October 7–9, from the approved plan to the final file: two for the shoot and the first cut, and one more for polishing. Here's who did what, which ideas went into it, and where it nearly fell apart.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why generate an ad at all
&lt;/h2&gt;

&lt;p&gt;Clay Sniper already has an App Preview on the App Store, and it's honest: a screen recording of the real app, the watch, a real gunshot sound. Apple doesn't accept anything else there. But that video only works for people who've already opened the product page. To get them there, you need something for the feed: Reels, Shorts, TikTok. Fifteen seconds, a story, faces, a joke. A solo developer can't shoot that with actors on a real range, so I had it generated.&lt;/p&gt;

&lt;p&gt;This was the second attempt. The first ad, "Hands full", ran on a local video model on my second Mac: no voices, almost no faces. It taught me the main lesson about hooks (more on that below). For "The Legend" I switched to a cloud model that can hold characters, dialogue and sound.&lt;/p&gt;

&lt;h2&gt;
  
  
  The idea: even legends miss
&lt;/h2&gt;

&lt;p&gt;An ad needs one promise, not a feature list. For a shooter's logbook, Claude put it like this: &lt;strong&gt;"Even legends miss. The difference is they know exactly where."&lt;/strong&gt; The end card squeezes it into three words: &lt;strong&gt;KNOW YOUR MISS&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The camera style was mine: someone else's ad I liked. A field at golden hour, two armchairs and a side table in the grass, Wes Anderson symmetry, warm film grain, a cut every 2–3 seconds, snap zooms, whip pans, macro inserts. We cut three short silent clips from it and used them as camera-motion references only. The model was told not to copy the people, the props or the story, just the way the camera moves.&lt;/p&gt;

&lt;p&gt;Two characters carry the story:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The Legend&lt;/strong&gt;: a fictional champion with fiery red hair, amber shooting glasses pushed up on her head, an olive vest, a dry half-smile and slow, precise movements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Rookie&lt;/strong&gt;: a jittery newcomer in a brand-new orange vest with the price tag still on the sleeve. He asks the question the viewer would ask.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;He asks "How do you never miss?" She says "I do. I log them." and slides her phone with the stats toward him. Then she solemnly sips tea from a tartan thermos, walks to the station and smokes the clay. The tweed crowd erupts. The myth of the flawless shooter breaks, and the product shows up as evidence in her hand, not as a slide.&lt;/p&gt;

&lt;h2&gt;
  
  
  The crew: who did what
&lt;/h2&gt;

&lt;p&gt;The most interesting part of the project is how the roles split. Two agents and one video model did the work, and each had its own job, just like on a real set.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Role on set&lt;/th&gt;
&lt;th&gt;Who&lt;/th&gt;
&lt;th&gt;What they did&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Showrunner&lt;/td&gt;
&lt;td&gt;Me&lt;/td&gt;
&lt;td&gt;Brought the style reference, approved the plan and the heroine, accepted the draft, lifted the "no gun on screen" rule, picked a silhouette over a face for the shot, decided to upscale to 1080p in the edit, made the calls at every fork&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Screenwriter&lt;/td&gt;
&lt;td&gt;Claude&lt;/td&gt;
&lt;td&gt;The promise, a four-part beat sheet, a six-shot storyboard, dialogue timing at 2.5 English words per second, a retention pass&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fact-checker&lt;/td&gt;
&lt;td&gt;Claude&lt;/td&gt;
&lt;td&gt;Checked every line and every screen against the app's code and real screenshots. Cut a feature that didn't exist&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Character artist&lt;/td&gt;
&lt;td&gt;Codex&lt;/td&gt;
&lt;td&gt;Character sheets: the heroine full-length, from behind and as a portrait (two versions), the rookie. The model uses them to keep faces consistent shot to shot&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Production designer&lt;/td&gt;
&lt;td&gt;Codex&lt;/td&gt;
&lt;td&gt;The location start frame: armchairs, table, thermos, crowd behind a rope, a phone with a bright green screen to replace later&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Director&lt;/td&gt;
&lt;td&gt;Claude&lt;/td&gt;
&lt;td&gt;A brief for six cuts pinned to timecodes, the 180-degree rule, camera-motion references, a list of restrictions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Camera, cast, sound&lt;/td&gt;
&lt;td&gt;Seedance 2.5&lt;/td&gt;
&lt;td&gt;Shot every cut in one pass, played both leads and the crowd, voiced the lines, the range noise and the shots&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Production coordinator&lt;/td&gt;
&lt;td&gt;Claude&lt;/td&gt;
&lt;td&gt;Launched the generation, watched the queue, saved the IDs of every piece so we could come back to them&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Editor and sound&lt;/td&gt;
&lt;td&gt;Claude&lt;/td&gt;
&lt;td&gt;Edit decision list, cuts, subtitles, the KNOW YOUR MISS card, an App Store end card, the 1080×1920 upscale, frame-by-frame screen fixes, a real gunshot layered over the generated one&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Censor&lt;/td&gt;
&lt;td&gt;Claude&lt;/td&gt;
&lt;td&gt;Caught what ad platforms reject: barrels pointing at the camera, revealing angles&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Notice that Claude has the most roles but none of them involve drawing. It writes, counts, checks, briefs and edits. Codex and Seedance make the pictures; Claude writes their briefs and signs off on the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fact-checking: a line that couldn't exist
&lt;/h2&gt;

&lt;p&gt;In the first draft, the Legend answered dryly: "I do. Station four." Nice line. But Claude checked it against the app's code first and found per-station stats only in the competition schedule. You can't show a screen that doesn't exist in an ad, so the line became "I do. I log them.", and the phone got a real screen with a best series of 22/25.&lt;/p&gt;

&lt;p&gt;The next day it turned out per-station stats do exist: a By station screen shipped in a newer version that lives in a different repository. Station 7 is red on it, 50%, which is KNOW YOUR MISS in a single picture. The second version of the ad shows exactly that screen.&lt;/p&gt;

&lt;p&gt;The lesson goes back to the first ad. Its hook was that a gloved finger can't tap a phone screen, while the watch crown still works. I rejected the shots: on the range people wear thin shooting gloves, and those work with touchscreens just fine. The hook was false for the very audience it targeted. The rule since then: &lt;strong&gt;check everyday details against real life and features against the code&lt;/strong&gt;, both before generating, not after.&lt;/p&gt;

&lt;h2&gt;
  
  
  Casting: character sheets
&lt;/h2&gt;

&lt;p&gt;A video model doesn't remember what a character looked like in the previous shot. To make the red-haired Legend in cut one the same person as in cut six, you feed it a character sheet: full-length, from behind, and a portrait. Codex drew those.&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%2Fsfvxfryd8ad94l9tf628.jpg" 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%2Fsfvxfryd8ad94l9tf628.jpg" alt="Character sheet of the Legend: full-length front view, back view and portrait" width="560" height="996"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I approved the heroine on the second try, and the rule was strict: &lt;strong&gt;the look gets approved before any video runs&lt;/strong&gt;. Redrawing a picture takes a minute; reshooting an ad because the face is wrong takes hours.&lt;/p&gt;

&lt;p&gt;Claude also set boundaries for the character: striking, but not sexualized. No body-focused angles, no cleavage, no bare skin. The charisma comes from light, gaze and that half-smile. The reason is practical: ad platforms reject such creatives, and the video model simply refuses those prompts. Other restrictions: no real people or athlete lookalikes, no logos. Even the thermos is unbranded, just tartan.&lt;/p&gt;

&lt;h2&gt;
  
  
  Storyboard: six shots in fifteen seconds
&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;Time&lt;/th&gt;
&lt;th&gt;On screen&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;0–2.5 s&lt;/td&gt;
&lt;td&gt;An orange clay bursts in slow motion. The crowd turns heads in unison. Caption: "She hasn't missed all day."&lt;/td&gt;
&lt;td&gt;Hook: everyone is looking the wrong way&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;2.5–5 s&lt;/td&gt;
&lt;td&gt;Whip pan to the armchairs, over the rookie's shoulder: "How do you never miss?" Snap zoom on her: "I do."&lt;/td&gt;
&lt;td&gt;Character clash and the viewer's question&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;5–7 s&lt;/td&gt;
&lt;td&gt;Macro: her hand slides the phone, per-station stats on screen. Voice-over: "I log them."&lt;/td&gt;
&lt;td&gt;The product as evidence, not a slide&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;7–10 s&lt;/td&gt;
&lt;td&gt;She pours tea from the thermos and takes a solemn sip. The rookie, out of focus: "...tea?"&lt;/td&gt;
&lt;td&gt;The most shareable beat, a pause before the shot&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;10–12.5 s&lt;/td&gt;
&lt;td&gt;Silence, a silhouette at the station against the sunrise, "Pull!", the shot, the clay turns to dust&lt;/td&gt;
&lt;td&gt;The hook's promise is paid off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;12.5–15 s&lt;/td&gt;
&lt;td&gt;Perfect symmetry: she raises the thermos cap like a toast, the rookie copies her with an empty hand. KNOW YOUR MISS&lt;/td&gt;
&lt;td&gt;Finale and one line of promise&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A few professional rules Claude followed without being asked:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The 180-degree rule.&lt;/strong&gt; In the dialogue the rookie is always on the left and she's on the right. The camera never crosses the line between them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Varied shot sizes.&lt;/strong&gt; Extreme wide, medium, macro, close-up, wide, wide. Never three of the same in a row.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dialogue windows.&lt;/strong&gt; Every line is timed at 2.5 words per second. "I log them." didn't fit the macro shot, so it became a voice-over on top of the phone.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Works with the sound off.&lt;/strong&gt; Subtitles duplicate every line and sit between 15% and 75% of the frame height, clear of the Reels and TikTok buttons.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The shoot: the whole ad in one pass
&lt;/h2&gt;

&lt;p&gt;Seedance 2.5 shot the first draft in a single pass: all six cuts from one generation. It got six references: three images (both character sheets and the start frame) and three video clips with the camera style. Every camera move in the prompt pointed to its reference: "over the shoulder like Video 1", "whip pan like Video 3".&lt;/p&gt;

&lt;p&gt;The job sat in the queue for almost two hours. The draft came out at 480p, 14 seconds. A pleasant surprise: the model produced voices, intonation, the gurgle of tea and the crowd noise itself. No separate voice-over needed.&lt;/p&gt;

&lt;p&gt;I accepted the draft with two notes. First, the gun wasn't visible in the shooting scene. That came straight from the prompt: Claude, being cautious, had banned close-ups of the gun, and the model removed it altogether. Second, Claude had composited a real stats screenshot onto the green phone screen, but at 480p the "Best series 22/25" line was unreadable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fixes: reshoot pieces, not the whole ad
&lt;/h2&gt;

&lt;p&gt;Regenerating the whole ad for two notes means gambling everything that already works. The model shoots differently every time, and the heroine in the tea shot could come back as someone else. So Claude reshot only the weak pieces as separate generations. The first round, the phone and the shot, took about twenty minutes. The shot was later reshot once more, more on that below.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Piece&lt;/th&gt;
&lt;th&gt;Draft v1&lt;/th&gt;
&lt;th&gt;Final&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Phone, 4 s&lt;/td&gt;
&lt;td&gt;Green screen with a perspective-warped screenshot. Numbers blur at 480p&lt;/td&gt;
&lt;td&gt;The model got our own clip as a "repeat this frame by frame" reference plus the By station screenshot. Motion repeated, screen drawn by the model, large station badges readable. Later the Russian demo clubs were swapped for US ones&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shot, 5 s&lt;/td&gt;
&lt;td&gt;Silhouette from behind, no gun visible, a "pistol" pose&lt;/td&gt;
&lt;td&gt;Third take: one shot from behind and slightly to the side, a silhouette at sunrise, the whole gun visible, no face. The prompt describes a long double-barrel shotgun and a proper trap stance; a pistol grip is banned&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Phone in wide shots&lt;/td&gt;
&lt;td&gt;A 26×12 px green rectangle on the table&lt;/td&gt;
&lt;td&gt;We tried the splash screen and the icon; both dissolve into a blob at that size. The screen is now off: nearly black with a reflection&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Length&lt;/td&gt;
&lt;td&gt;15 s&lt;/td&gt;
&lt;td&gt;20.6 s: 18 s of story from three generations with freeze frames at the joins, plus a 2.5 s end card&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The biggest surprise was the phone screen. The assumption had been that you can't trust a model with small UI, so Claude always composited the real screenshot on top. It turns out that if you give the model its own clip as a motion reference plus the screen image, it repeats the shot and draws the UI itself. Large elements, numbers and badges, come out readable. Small text still drifts, so this only works for large on-screen elements.&lt;/p&gt;

&lt;h2&gt;
  
  
  The edit: an EDL and a censor
&lt;/h2&gt;

&lt;p&gt;The final ad is assembled from pieces of three generations. Claude described it as an edit decision list: for every piece, the source, in and out points, which audio to use and whether to hold a freeze frame at the end. A build script assembles the video from that list and lays on the subtitles, the end card and the sound. The gunshot is a real one, taken from the App Preview recording, layered over the generated one.&lt;/p&gt;

&lt;p&gt;The cuts inside the generated draft had to be found by hand: standard scene-change detectors found nothing in this video. Claude compared neighbouring frames pixel by pixel and located cuts by spikes in the difference, then timed the subtitles by the loudness of the audio track.&lt;/p&gt;

&lt;p&gt;Censorship landed in the edit too. In the second take of the shooting scene the model swung the barrels straight at the camera for just over a second. That's a no-go for an ad, so Claude cut the piece entirely. What was left of the three-quarter view lasted about half a second and looked like a fragment. So I asked for the scene to be reshot differently: one shot from behind and slightly to the side, a silhouette against the sunrise. The whole gun is visible, and the barrels physically can't point at the camera. That third take made the final cut.&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%2Fmarydhp9hv5otzwn90ud.jpg" 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%2Fmarydhp9hv5otzwn90ud.jpg" alt="The final shooting scene: the Legend in silhouette from behind, a double-barrel shotgun at her shoulder, sunrise behind her" width="560" height="996"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Polishing: one more day
&lt;/h2&gt;

&lt;p&gt;The ad that looked done on the evening of October 8 wasn't ready to run: no app name, no App Store link, and the picture was still 480p. Polishing took another day, and the model didn't shoot a single new frame for it. It's all editing.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;1080×1920 on our own.&lt;/strong&gt; Regenerating in 1080p would have meant reshooting every piece and gambling the good takes again. So Claude upscaled the 480p sources during assembly with careful scaling and light sharpening. Subtitles and cards are drawn natively at 1080, so text stays sharp even where the picture is softer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A 2.5-second end card.&lt;/strong&gt; The last frame blurred, the icon, the name Clay Sniper, the subtitle from the App Store listing and the official Download on the App Store badge, taken from Apple's site rather than redrawn.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;US clubs on screen.&lt;/strong&gt; The phone close-up showed clubs from Moscow and Krasnodar at the bottom, the app's demo data. For a US campaign Claude captured a fresh screenshot with US demo data, clubs in Texas and Pennsylvania. Instead of regenerating the piece, the new card was pasted in frame by frame: on the close-up it's anchored to the old screen by keypoints; on the table, where the screen is tiny and in steep perspective, the screen corners are tracked frame to frame and motion blur is added to match.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The pump click.&lt;/strong&gt; In the shooting scene the model generated the sound of a pump-action being racked. A double-barrel has no pump, and any shooter would hear it. Claude muted that third of a second.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One thing stayed as it was. In the phone piece the model zooms in until the screen fills the frame and the phone body disappears. I wanted the whole phone in her hand, but there's no such frame in the footage. We discussed three options: redraw the frame with a local model and paste in the screenshot, crop the zoom out, or reshoot the piece. We decided it doesn't hurt the ad.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The wink.&lt;/strong&gt; I asked for a glance over the shoulder with a wink before the shot. The model never did it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Resolution.&lt;/strong&gt; The sources are 480p and the final is upscaled to 1080×1920. Fine for a phone feed, but softer than true 1080p.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The whole phone.&lt;/strong&gt; The model zooms in so far that the phone body disappears. There's no frame with the whole phone in her hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subtitles by ear.&lt;/strong&gt; Timing was matched to the track's loudness; no human ear has checked it yet.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I took away
&lt;/h2&gt;

&lt;p&gt;It felt less like using a tool and more like working with a small film crew. I didn't write prompts or scrub a timeline. I looked at frames and said "yes", "no", "actually, let's show the gun". Claude kept the whole project in its head, from the promise to the last cut, and talked to each crew member in their own language: character sheets for Codex, a second-by-second brief for Seedance.&lt;/p&gt;

&lt;p&gt;Second: fixes. Generate the whole ad once, then reshoot only the weak pieces. What works stays put, and a fix takes minutes instead of hours.&lt;/p&gt;

&lt;p&gt;Third: fact-checking beats beauty. The most dangerous mistakes in this project weren't in the picture but in the meaning: a line about a feature the agent didn't find at first, and a glove hook that turned out to be false. A model will draw anything, so whether it's true has to be checked before you generate.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://klukyanov.ru/notes/clay-sniper-ai-ad/" rel="noopener noreferrer"&gt;klukyanov.ru&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Shorter weekly write-ups (in Russian) — on &lt;a href="https://t.me/+KSAy8mfFOsgwYWMy" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>video</category>
      <category>marketing</category>
      <category>ios</category>
    </item>
  </channel>
</rss>
