有人直接跑去問 Claude：「你在對話中的 Generative UI 到底怎麼生出來的？結果 Claude 就老老實實的權招了 👀」 答案說穿不值錢，不是什麼神奇渲染引擎 是一個叫 show_widget 的 tool call，把 HTML 當參數丟出來，直接注入父頁面的 DOM（不是 iframe），邊 streaming 邊 incremental parse，所以才會看到畫面一塊一塊長出來。 真正的功夫全在那份「設計準則」：streaming-first 的結構、禁漸層／陰影（DOM diff 時會閃）、兩種字重、強制 dark mode……作者甚至從 devtools 把 Anthropic 餵給模型的 verbatim guidelines 整份撈了出來。 最漂亮的是 read_me 這個 pattern：模型動手前要先 lazy-load 對應模組的設計文件進 context，而不是把整套 system prompt 一次塞爆。等於把 progressive disclosure 用在模型自己的指令上。 最後他把這整套搬進終端機的 coding agent pi，用 Glimpse（原生 macOS WKWebView）＋ morphdom 解掉 streaming 閃爍。

Built CefSwift. Embed real Chromium (CEF) in SwiftUI apps on macOS with a single package. No WKWebView hacks. No manual CEF setup. Just Swift Package Manager. 🧵Here are some powerful examples 👇👇👇

然后又众所周知，目前绝大部分桌面版app都是网页 chromium套壳（Electron），也就是如果你的自制前端有网页版的话，套个壳就能变成桌面app，并且兼容macOS和Windows，只需下载安装包即可 同时，如果做内置浏览器，那么chromium框架会比手机上的WKWebView自由度高很多 也就是说，只需一个安装包，你就可以在各种电脑用上自己的app和私人浏览器☝️

按cc的话来说，“WKWebView就是一个完整的浏览器塞进一个UIView里 你只是在外面包了一层地址栏”

赞美WKWebView ！

Ruby でブラウザーが作れるようになりました。 不可視の WKWebView をテクスチャに取り込んで OpenGL で描画してます。

自作 GUI ライブラリーで YouTube 再生 #gui #toolkit #opengl #wkwebview #ruby

これ、YouTube の動画だけ描画されない問題があって諦めかけてたけど、不可視の WKWebView ウィンドウを1ピクセルでもスクリーン内に入れれば動画が描画されることが分かり、それで妥協しよう（1px 見えちゃう）と思ったけど、ミラクルなアイデアを思いつき 1px の問題解決した。 そのアイデアとは、

SwiftUI 写的原生 macOS Markdown 阅读器，三栏布局：目录树、渲染视图、大纲导航。基于 cmark-gfm 和 WKWebView 渲染，支持 Mermaid、KaTeX、PlantUML、Prism.js 代码高亮、33 套主题、Quick Look 预览、PDF 导出和多语言。 github.com/davidhoo/Markdown…

You can build iOS apps from your iPhone now. No Mac required. Rilable is an open-source iOS app that turns prompts into real apps — web or native. Type what you want, an AI agent writes the code, spins up a Daytona sandbox, compiles via cloud Xcode (Chorus), and drops an OTA install link in the chat. The stack is honest: SwiftUI Convex Claude. Your own API keys, your own deployment. No auth gate, no waitlist, no monthly subscription. What makes this technically interesting: — Web apps compile in Daytona sandboxes and render in a WKWebView — iOS apps compile via Chorus cloud Xcode, streamed from a cloud iPhone simulator — Compile errors auto-repair via agent follow-ups — Voice input via Whisper, keys stay server-side — Every app the agent builds gets AI features through Vercel AI Gateway (keyless proxy — no leaked keys in client code) Built by @rileybrown in 10 prompts for ~$210 in API credits. Fable 5 (secretly Opus 4.8) under the hood. This is what "app development for everyone" actually looks like. No Mac, no Xcode install, no provisioning profile hell. github.com/rbrown101010/rila…

how is the extension getting the content of the X posts? I used to be able to load the x links in a WKWebView but today X just returns the first paragraph of posts/articles (everything is behind a paywall now). Are you receiving the content of the X webview?

うおー、iOS Safariからも動く（iOS 26.5.1） なんならXアプリのWKWebViewでも動く。

If you've run into an issue or are looking for pointers on Web Views on Apple platforms including (e.g. WebView for SwiftUI, or WKWebView) drop by our WWDC26 Q&A. We have engineers standing by, ready to answer your questions over the next couple of hours. developer.apple.com/forums/a…

turns out the 4gb spike i saw from profiling my book reading app is a security feature from WebKit's JS VM Gigacage, not a leak. 4GB of virtual memory but zero physical RAM. and the actual real extra problem was apple webkit's back-forward cache holding onto the old caches from previous chapters so i re implemented the reader and started a fresh WkWebView per chapter. that kills the process between chapters, releasing the cache, no accumulation. this spends about 200ms per chapter load but using a single WkWebView comes with a lot of cache management that i'm not ready for atm, maybe later. now i got worried about that too because that'd mean moving back and forth between the end of chapter A and the start of chapter B would kill and open processes repeatedly and that doesn't sit well too. i ever faced something similar when i was learning jdbc in java, the problem was to either use one connection during the server runtime or open and close a connection to the db everytime. that ended with me using a connection pool similar here i'm thinking of using a pool of WkWebView, about 3 of them, one for the current chapter and the next for the next 2 adjacent chapters. with this the user won't feel the process spawn per chapter and with 3 WKWebViews in a ring buffer, the adjacent navigation becomes instant. far jumps still spawns, but that happens once a while while reading a book may learn newer stuff though