Fatbobman's Swift Weekly #082
Apple Pays the Price for Its ArroganceA few days ago, the Epic Games v. Apple case reached a critical milestone. The court ruled that Apple had willfully violated the permanent antitrust injunction issued in 2021. While Apple superficially allowed developers to use third-party payment channels, in practice it maintained its original monopoly position through high commissions, deliberate user-experience friction, and intimidating warning screens. The court not only approved Epic's motion to enforce the injunction but also took the rare step of referring Apple's behavior to the U.S. Attorney's Office for the Northern District of California, to investigate potential criminal contempt of court charges. Through the iPhone and App Store, Apple has built formidable commercial barriers, transforming from a once unique and proudly innovative company into the type of tech giant it once sought to avoid becoming. As Apple's market size and influence expanded, its focus naturally shifted from innovation toward protection and defense of its established market position. This is hardly surprising—once an enterprise reaches sufficient scale, the stable returns from preserving market dominance often outweigh the uncertain gains from continuous innovation. Whether the App Store's commission rates are reasonable ultimately hinges on the actual value and services it provides to developers. For smaller, particularly independent developers, despite the relatively high commission rate, the App Store offers a stable global payment infrastructure, a trustworthy distribution platform, and convenient promotional tools, making steady revenues achievable. However, large technology firms with their own extensive promotional channels and user bases understandably find it difficult to accept such substantial revenue cuts merely for App Store distribution. This has been at the heart of Apple's conflicts with developers and regulatory authorities in recent years. It is foreseeable that this court decision will accelerate global regulatory and legislative scrutiny, potentially marking the end of Apple's era of easily extracting hefty "toll fees." Apple has consistently struggled to escape its hardware-centric development path, lacking sufficiently compelling internet and cloud services to offer truly convincing added value to its ecosystem developers. Many developers deeply invested in the Apple ecosystem naturally gravitate towards Apple's first-party APIs and services. Furthermore, Apple is entirely capable of enhancing its ecosystem attractiveness by providing more efficient and stable cloud services, richer and more accessible large-scale AI model APIs, or even highly competitive AI cloud computing services. Such improvements would enable Apple to gain developers' acceptance and generate revenue in ways developers genuinely appreciate. Unfortunately, Apple has yet to do so. This judgment serves not only as a wake-up call regarding Apple's arrogance toward court rulings but also highlights the inevitable repercussions stemming from its long-term lack of empathy and its condescending attitude towards its developer ecosystem. Hopefully, this lesson will prompt Apple to genuinely reassess its ecosystem strategies, abandon its defensive mindset, and adopt a more proactive, open, and inclusive approach toward the developer community. By fully leveraging its technological and service advantages, Apple can rebuild developers' trust and enthusiasm for collaboration. Only then can the App Store return to the right track, establishing a prosperous, sustainable ecosystem that genuinely benefits developers, users, and platform owners alike. Previous Issue｜Newsletter Archive If you appreciate my work and want to promote your product to the Swift and iOS developer community, sponsoring my blog & newsletter could be an excellent opportunity for you. OriginalUsing equatable() to Avoid the NavigationLink Pre-Build Pitfall
Recent RecommendationsWhat's New in Swift 6.1?I’ve previously recommended several excellent articles covering new features in Swift 6.1. However, Paul Hudson’s overview still surfaced a few details I had overlooked. One such feature is Metatype Keypaths, which is exactly what I needed for my current project—it allows accessing static properties via key paths, overcoming the limitation of instance-only access. Another example is Protecting Mutable State with Mutex in SwiftWhile
Keep Downloading with a Background SessionSince iOS 7, developers have been able to use Dependency Container on Top of Task Local Values in SwiftSwift’s
Deep or Not Too DeepDeep Linking is essential for creating seamless user experiences, enabling attribution tracking and context restoration. As mobile systems evolved, so too has the implementation of deep linking. In this in-depth article, Kyryl Horbushko thoroughly reviews the evolution and native solutions for deep linking across iOS and Android, and offers a detailed walkthrough of implementing deferred deep links and attribution using AppsFlyer. A great reference worth bookmarking. Oscillating Glowing Strings with Metal and SwiftUIAs always, Uladzislau Volchyk returns with another eye-catching SwiftUI + Metal experiment. This time, he builds a glowing, oscillating button using ToolsChord ProviderChordPro is a text-based markup format for aligning chords with lyrics. Nick Berendsen’s Chord Provider is a native, open-source ChordPro file editor and viewer built specifically for macOS. Written entirely in Swift 6 and SwiftUI without third-party dependencies, it's a great reference project for macOS developers—it demonstrates best practices in managing NSAlchemy - Useful macOS Controls for SwiftUIDespite SwiftUI’s increasing macOS support, many essential controls are still missing. To bridge this gap, Joshua J. Root created NSAlchemy, a library that wraps various AppKit components for SwiftUI use. The current version includes components like VS2X - Convert VS Code Themes to XcodeCompared to Xcode, VSCode boasts a more vibrant theme ecosystem and a highly active customization community. To help Xcode users tap into this variety, Wei Wang (onevcat) created an online tool that converts your favorite VSCode themes into Xcode-compatible formats. The project was fully generated by AI, and its source code is open-sourced. For clear-cut, purpose-driven tools like this, AI is already showing impressive practical potential. 苹果为傲慢付出了代价几天前，Epic Games 与 Apple 案迎来了一项重要裁决。法官认定 Apple 故意违反了法院于 2021 年发布的反垄断永久禁令，表面上虽允许开发者使用第三方支付渠道，但却通过高额佣金、用户体验障碍以及警告页面等方式，实质上继续维护着原有的市场垄断地位。法院不仅批准了 Epic 提交的执行禁令动议，还罕见地将 Apple 的行为移交给美国司法部加州北区检察官，以调查其是否构成刑事藐视法庭。 苹果凭借 iPhone 和 App Store 建立起牢固的商业壁垒，曾经那家特立独行、以创新为骄傲的企业，如今却逐步转变成它自己也曾试图避免的科技巨头。随着公司体量与市场影响力的增加，苹果逐渐从追求创新转向对市场地位的保护和防御，这本身并不奇怪——当企业规模足够大时，保护自身市场优势的收益，往往比不断投入不确定的创新更具吸引力。 App Store 的分成比例合适与否，完全取决于其给软件开发者带来的实际价值和服务。对于小型尤其是独立开发者来说，尽管佣金比例不低，但 App Store 提供的全球支付渠道、可信任的分发平台，以及便捷的推广手段，使它们能够相对容易地实现稳定的收入。但对于那些具备自主宣传渠道和广泛用户基础的大型科技公司而言，仅因通过 App Store 分发就被抽取高昂比例的收入无疑难以接受，这也是近年来苹果不断遭遇开发者和监管机构挑战的核心问题。 可以预见，本次裁决无疑会进一步加快全球各地监管、立法机构的跟进步伐，苹果“轻松收取过路费”的时代或将一去不复返。 苹果一直未能彻底摆脱以硬件为主导的发展路径，缺乏足够强大的网络服务吸引力，难以为生态内的开发者提供令人信服的增值服务。对于大量专注于苹果生态的开发者来说，他们天然倾向于使用苹果第一方的 API 和服务。苹果完全有能力通过提供更高效稳定的云端服务、更丰富且易用的大模型 API，甚至竞争力更强的 AI 云计算服务，来进一步增强自身生态的吸引力，并以更加令开发者认可的方式获得收益。然而，苹果迄今尚未迈出这关键一步。 本次裁决对苹果而言，不仅仅是对其傲慢姿态的警醒，更深刻揭示了其长期以来在生态建设中缺乏同理心、居高临下的态度所带来的必然反噬。希望这一教训能真正促使苹果重新审视自身生态战略，摒弃防御心态，以更加主动、开放、包容的姿态面对开发者社区，充分发挥自身技术与服务优势，重塑开发者的信任与合作热情。唯有如此，App Store 才能重回正轨，成为一个开发者、用户与平台方均能实现长期共赢的繁荣生态。 如果您发现这份周报或我的博客对您有所帮助，可以考虑通过 爱发电，Buy Me a Coffee 支持我的创作。 原创使用 equatable() 避免 NavigationLink 预构建陷阱
近期推荐Swift 6.1 新特性速览 (What's New in Swift 6.1?)在之前的周报中，我已经推荐过多篇介绍 Swift 6.1 新特性的优秀文章。但当我读到 Paul Hudson 的这篇总结时，仍然发现了一些此前没有注意到的细节。其中，Metatype Keypaths 就是我当前项目中急需的能力，它使得我们可以使用 key path 访问类型的静态属性，不再受限于实例成员。此外，我最近在测试中使用的 用 Mutex 保护可变状态 (Protecting Mutable State with Mutex in Swift)
实现后台下载 (Keep Downloading with a Background Session)从 iOS 7 开始，开发者便可以通过 基于 Task Local 构建依赖容器 (Dependency Container on Top of Task Local Values in Swift)Swift 的
深度链接实践全解 (Deep or Not Too Deep)深度链接（Deep Linking）是提升用户体验、实现跳转归因与上下文还原的关键机制。随着移动系统的发展，Deep Linking 的实现方式也在不断演进。kyryl horbushko 在这篇内容详实的长文中，系统回顾了 iOS 与 Android 平台上深度链接的演进历史与原生实现方式，并深入讲解了如何借助 AppsFlyer 实现 deferred deep link 与归因跟踪。这是一篇值得收藏的参考资料。 🪜 用 Metal + SwiftUI 构建波动发光按钮 (Oscillating Glowing Strings with Metal and SwiftUI)一如既往，Uladzislau Volchyk 再次带来一篇精彩的 SwiftUI + Metal 视觉实验。本文通过 工具Chord ProviderChordPro 是一种用于编排歌词与和弦的文本标记格式，而 Nick Berendsen 开发的 Chord Provider，则是一个专为 macOS 打造的原生开源 ChordPro 文件编辑与阅读器。项目完全采用 Swift 6 与 SwiftUI 编写，无任何第三方依赖。对 macOS 程序员而言，Chord Provider 涵盖了 NSAlchemy：扩展 SwiftUI 的 macOS 控件库尽管 SwiftUI 近年来在 macOS 平台上不断扩展，但依旧缺少不少关键控件。为此，Joshua J. Root 开发了 NSAlchemy —— 一个将常用 AppKit 控件封装为 SwiftUI 组件的库。当前版本中已包含 VS2X: VSCode 主题转换器相较于 Xcode，VSCode 拥有更丰富的主题生态，用户社区也更热衷于分享与自定义。为此，Wei Wang (onevcat) 推出了一款在线工具，可将喜爱的 VSCode 主题一键转换为 Xcode 可用的格式。项目完全由 AI 驱动生成，作者也 开源了全部代码。对于这种目标明确、功能聚焦的应用场景，大模型的确已经具备了令人惊喜的实用性。 Welcome to my blog Fatbobman's Swift Blog( 肘子的Swift记事本 )
|
