Building Shopie for Mac with SwiftUI
The article discusses challenges and criticisms of SwiftUI, particularly regarding its cross-platform approach and adaptability across different Apple devices. The author argues that SwiftUI's design prioritizes code reuse over optimal user experience, especially when scaling interfaces from watchOS to Mac. Interface Builder and Auto Layout are presented as more reliable alternatives for creating adaptive UIs on macOS.
- ▪SwiftUI is criticized for prioritizing cross-platform code reuse over tailored user experiences.
- ▪Interface Builder and Auto Layout are described as effective tools that still work well for macOS development.
- ▪The author believes SwiftUI can break layouts during OS updates, unlike more predictable systems like CSS.
- ▪Size classes in Apple's frameworks are seen as limiting and not always practical for determining device orientation.
- ▪Building a WYSIWYG editor is challenging when UIs must adapt to varying screen sizes, resolutions, and input methods.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Mjtsai |
| Canonical URL | https://mjtsai.com/blog/2026/05/08/building-shopie-for-mac-with-swiftui/ |
| Publication time | Sun, 17 May 2026 10:39:37 +0000 |
| Retrieval time | 2026-05-17T10:52:13.099Z |
| Last seen | 2026-05-17T10:52:13.099Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ZwvYuHF81TbK |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
> I’m not entirely sure, but I think this is different for SwiftUI (and many other Apple frameworks). Maybe it was the original intention for watchOS, but certainly not for UIKit+. It doesn’t seem it was “app first”. (even just for something seemingly simple/baseline, like building TextEdit or Finder) It was built for "Apple cross platform" first. Just try to reuse as much as possible. > Sorry, the point I was trying to make is that it is extremely difficult, if at all possible, to make a WYSIWYG editor for a UI that can look vastly different depending on screen size, resolution, DPI, input device, and so on, and whose visual expression is dependent on rulesets rather than something that can be directly manipulated in a GUI.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Mjtsai.
Discussion
0 commentsMore from Mjtsai
