Swift

Have You Registered for WWDC 2025 Group Labs Yet?

• ✨ Experience the Charm of Swift
• 🌌 Apple Developer Relations
• 🤚 Creating Xcode Source Editor Extensions
• 📊 Mesh Gradients in SwiftUI
• and more...

Use Swift’s generics, KeyPath, protocol extensions, and ResultBuilder to build a type-safe DataFrame export tool with TabularData. Dive into column mapping, conditional logic, and clean DSL syntax for maximum flexibility

Fatbobman’s Swift Weekly #084 is out!

Awaiting WWDC 2025 with Serenity

• ✨ SwiftUI’s .ignoredByLayout()
• 🌌 Picker With Optional Selection
• 🤚 Don't Save SQLite in App Group Container
• 📊 Default isolation with Swift 6.2

and more...

Publication croisée depuis https://programming.dev/post/30462189

Among SwiftUI’s many APIs, .ignoredByLayout() is something of an “understated member.” Information is scarce, usage scenarios are uncommon, and its very name tends to raise questions. It seems to suggest some kind of “ignoring” of the layout—but how does that differ from modifiers like offset or scaleEffect, which by default don’t affect their parent’s layout? When does ignoredByLayout actually come into play, and what exactly does it “ignore” or “hide”? In this article, we’ll lift the veil on this subtle API in SwiftUI’s layout mechanism.

Don't Let Vibe Coding Hinder Your Technical Growth

Fatbobman’s Swift Weekly #083 is out!

• 📏 A Complete Guide to Swift Measurement
• 🔒 SwiftUI View Model Ownership
• 🍫 Cocoa Basics
• 🖥️ xtool - Cross-platform alternative to Xcode

and more...

In everyday life we constantly convert values between different units of measurement. For developers this seems easy—write a few formulas, sprinkle in a couple of switch statements and you’re done. But the moment you try to support dozens of units, seamless internationalisation, formatting, precision and rounding, the workload sky-rockets and the drudgery can make you question your life choices. The good news: starting with iOS 10 Apple added a comprehensive Measurement API to Foundation, taking all that “donkey work” off our hands. This article walks you through its usage and best practices.

Apple Pays the Price for Its Arrogance

Fatbobman’s Swift Weekly #082 is out!

• 🍏 Using equatable() in SwiftUI
• 🆕 What's New in Swift 6.1
• 🔒 Mutex in Swift
• 🎨 Convert VS Code Themes to Xcode

…and more

NavigationLink is a component SwiftUI developers love. By ingeniously combining the behavior of Button with navigation logic, it dramatically simplifies code. Unfortunately, in certain scenarios, using it the wrong way can create serious performance issues and make your app sluggish. This article analyzes the cause of the problem and offers a practical—albeit slightly mysterious—solution: adding the equatable() modifier to optimize performance.

The Chrome Paradox: Could DOJ’s Antitrust Remedy Create OpenAI’s Next Monopoly?

Fatbobman’s Swift Weekly #081 is out!

🔧 make NSImage sendable 🖼️ custom about window for a Mac 🌀 fully native cross-platform Swift apps …and more

Swift’s powerful type system empowers us to create semantically explicit and safe data models. Yet when we move to SwiftData or Core Data, the constraints of their underlying storage mechanisms often force us to compromise on type expressiveness. Those concessions blur our domain models’ intent and plant hidden seeds of instability.

This article explores how, within the restrictions of persistence layers, we can leverage ingenious type wrappers and conversions to build data models that are simultaneously Type-safe, semantically clear, and highly efficient.

Shorter Validity, Longer Shelf Life | Fatbobman's Swift Weekly #80

• My Hopes for Xcode
• SwiftUI Colors
• Zooming Slider
• Thinking of WWDC
• Alerts in iOS
• Swift Reduce
• XcodeBuild MCP
• Swift Regex

Can Xcode still capture developers’ enthusiasm? What changes does it need to stay competitive and relevant? In this article, I will outline several key improvements I hope to see in Xcode.

🚨 Microsoft tightens plugin rules ☁️ Google goes all-in on cloud-native AI 🤔 What’s next for Xcode?

Fatbobman’s Swift Weekly #079 is out!

🧱 Build WASM apps in Swift 🔀 Structured Concurrency (EGG rule) 🎯 WWDC25 wishes …and more

Swift 6.1 unleashes official WebAssembly builds through SwiftWasm—no patches required. Dive into this article to discover how to craft WebAssembly apps with Swift and unlock the boundless potential of cross-platform development.

Do Not Market Driver-Assistance as Autonomous Driving | Fatbobman's Swift Weekly #078

• Environment dismiss
• Swift 6.1
• Cross Compiling Swift
• Modern URL Construction
• Inspector
• MKMapView to Image
• MCP-Supported AI Frameworks
• State Management

In SwiftUI, dismiss is popular for its flexibility, but overusing it can introduce hidden risks, testing challenges, and stability issues. Opt for state-driven methods like Binding or custom environments for safer, more maintainable UI logic.

The Rise of MCP and Apple's AI Framework Vision | Fatbobman's Swift Weekly #077

• SwiftUI Environment
• TCA
• CustomTestStringConvertible
• Flexible, Styled Component
• TabView
• ModelActor
• Avoid Xcode Projects Merge Conflicts
• Swiftly 1.0

SwiftUI’s Environment is a powerful and elegant mechanism for dependency injection, and almost every SwiftUI developer encounters and uses it in daily development. Not only does it simplify data transfer between views, it also opens up greater possibilities for application architecture design. In this article, we will set aside specific implementation details and instead focus on the role and boundaries of Environment within an architecture, exploring some often-overlooked yet crucial design ideas and practical experiences.

Photographing My Fur Babies ｜ Fatbobman's Swift Weekly #076

• Intercept iPhone Network Requests
• Why I Avoid Group
• Sign in with Apple in the watchOS Simulator
• Color Space
• MCP server in Swift
• Macro Issues in Xcode Cloud
• Git Hooks in Swift

OpenAI Appeals to the US Government: Competitive Concerns Over DeepSeek | Fatbobman's Swift Weekly #075

• Key Considerations Before Using SwiftData
• Async/Await & SwiftUI
• Swift Compiler Issue
• Swift Testing Tip
• Interactive Charts
• Browse No More

This article aims to serve as a guide for developers interested in SwiftData, helping you understand its strengths and limitations so you can make informed decisions based on your project needs. Whether you’re considering adopting SwiftData in a new project or planning a migration from another persistence solution, the following content will provide valuable insights to support your decision-making process.