Native macOS developers have long favored Swift and SwiftUI for smooth interfaces, but a recent experiment shows limits when handling rich Markdown chats. The author, a veteran iOS engineer, built a SwiftUI prototype, then shifted to NSTextView with TextKit 2, AppKit, and finally WebKit. Each step exposed performance spikes, lag, or missing selection features for users who value seamless typing.

Despite mastering native APIs, the author hit an impasse: SwiftUI struggles with scrolling, AppKit cells blink, and pure TextKit 2 delivers poor streaming. Even after manual tweaks and accessibility fixes, basic features like context menus and dictionary lookups lagged. Switching to WebKit resolved rendering, but the ultimate shortcut came from a lightweight Electron shell, delivering instant, accurate markdown display for developers.

These trials illustrate why many chat‑centric apps pivot to web‑based stacks: native toolkits can’t match the combined typography, selection, and streaming performance of Electron or React Native. For developers prioritizing rich text, the decision boils down to trade‑offs; native may win on integration, but the web route offers faster, more reliable rendering without reinventing the wheel for developers in production.