<?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: Veysel Okatan</title>
    <description>The latest articles on DEV Community by Veysel Okatan (@veysel_okatan_1996cb38de2).</description>
    <link>https://dev.to/veysel_okatan_1996cb38de2</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%2F3326819%2Fc0f66677-c174-47d8-9bf4-3a516f20acc0.jpg</url>
      <title>DEV Community: Veysel Okatan</title>
      <link>https://dev.to/veysel_okatan_1996cb38de2</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/veysel_okatan_1996cb38de2"/>
    <language>en</language>
    <item>
      <title>Why I Built a Native macOS Window Manager from Scratch with SwiftUI</title>
      <dc:creator>Veysel Okatan</dc:creator>
      <pubDate>Tue, 08 Sep 2026 15:23:48 +0000</pubDate>
      <link>https://dev.to/veysel_okatan_1996cb38de2/why-i-built-a-native-macos-window-manager-from-scratch-with-swiftui-339n</link>
      <guid>https://dev.to/veysel_okatan_1996cb38de2/why-i-built-a-native-macos-window-manager-from-scratch-with-swiftui-339n</guid>
      <description>&lt;p&gt;Managing multiple windows on macOS has always felt slightly incomplete out of the box. While native split view helps, power users often find themselves missing flexible snap areas, multi-display workflow optimizations, and gesture-driven control without heavy background resource usage.&lt;/p&gt;

&lt;p&gt;As an independent software developer, I decided to tackle this problem natively. Instead of relying on bloated web wrappers or heavy background processes, I built &lt;strong&gt;&lt;a href="https://getneotiler.com" rel="noopener noreferrer"&gt;NeoTiler&lt;/a&gt;&lt;/strong&gt; from the ground up using Swift and SwiftUI.&lt;/p&gt;

&lt;h3&gt;
  
  
  Core Architectural Goals
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lightweight &amp;amp; Efficient:&lt;/strong&gt; Keeping memory footprint under 25 MB and CPU usage minimal while idling in the menu bar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Granular Snapping:&lt;/strong&gt; Moving beyond simple halves and quarters by adding thirds, sixths, custom snap grids, and multi-monitor cursor synchronization.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Privacy by Design:&lt;/strong&gt; Zero tracking, zero telemetry, and 100% offline local processing using macOS Accessibility APIs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Building native tools for the macOS ecosystem requires careful attention to OS lifecycle changes and native keyboard event handling. &lt;/p&gt;

&lt;p&gt;You can check out the full feature set and project details at &lt;strong&gt;&lt;a href="https://getneotiler.com" rel="noopener noreferrer"&gt;getneotiler.com&lt;/a&gt;&lt;/strong&gt;. I would love to hear feedback from fellow Swift and macOS developers on window tiling ergonomics and native UI patterns!&lt;/p&gt;

</description>
      <category>macos</category>
      <category>swift</category>
      <category>swiftui</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
