Menu

Porting Swift near zero-UI hotkey productivity app to Windows: native C# for snappy feel from shell layer. Will the Mac seamless feel survive?

#windows#swift#shell#file#hotkey
Reading 0:00
15s threshold

Long-time lurker, first post!

Been building a macOS menu bar app in Swift 6 (SwiftUI and AppKit). Hotkey, select a capture, click to drop numbered dots to annotate, and type/dictate a note for each dot. Repeat across multiple captures creates a "round". Zero-UI app (aside from menu bar icon) writes a folder (annotated PNG, Markdown, JSON) and aggregate copies a single text prompt with local file links to paste into any AI coding agent. Users have asked for a Windows version. Here's what I'm thinking. Please let me know if I'm missing anything.

**What ports and what doesn't**

Code for writing directory and files is ~2,000 lines of mostly Foundation Swift. Should port to C# fairly simply.

All user touchpoints Apple-only: ScreenCaptureKit, Vision OCR, a non-activating NSPanel for the notes, NSStatusItem, and global hotkeys. Every route needs a new Windows layer for those.

**Routes I considered versus C3 snappy shell layer**

**Swift everywhere** on the official Windows toolchain.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.