fatbobman

Fatbobman's Swift Weekly #052 | Reflecting on the Original Aspiration: On the First Anniversary of the Weekly's Inception

• Dev Conversations
• VoiceOver and Voice Control
• Shared With You
• UIKit or SwiftUI
• SwiftUI Environment

Fatbobman's Swift Weekly #051 | Xcode Is Not Alone

• NSManagedObjectID and PersistentIdentifier
• Container in SwiftUI
• Reduce Local AI Model Size
• Blend modes
• Tips of NSFetchedResultsController
• Communication Patterns in SwiftUI
• Mesh Gradients

Core Data and SwiftData are powerful data management frameworks designed by Apple for developers, capable of efficiently handling complex object relationships, hence known as object graph management frameworks. In these two frameworks, NSManagedObjectID and PersistentIdentifier serve similar functions and are both extremely important. This article will delve into their features, usage methods, and important considerations.

Fatbobman's Swift Weekly #050 | Has Your App Been Defeated by the New System?

• Data Binning
• Style Text in Terminal
• Pass Binding in NavigationDestination
• SPM Snippets
• Realm Deprecation
• ContentMargins in SwiftUI
• NSAttributedString Changes

Data binning is a commonly used data processing technique that typically divides continuous numerical or temporal data into multiple intervals (which are mostly adjacent and non-overlapping). This method not only covers the entire data range but also provides clear demarcation for data points within each interval. By performing data binning, we can analyze, visualize, and statistically process complex datasets more effectively. This article will explore how to use the advanced APIs provided by Swift Charts to achieve precise and efficient data binning.

Fatbobman's Swift Weekly #049 | Innovation Comes in Many Forms

• Core Data Issue
• Observable vs ObservableObject
• SwiftData Expressions
• Obj-c to SwiftUI
• Swift Testing
• Memory Leak
• visionOS 2 PortalComponent

Fatbobman's Swift Weekly #048 | Apple Watch, The Sturdy Linchpin of the Apple Ecosystem

• Hover Effects
• AirDrop Conundrum
• LockedCameraCapture Framework
• iOS Performance
• visionOS in Medical
• Github Contribution Graph with Swift Charts

Fatbobman's Swift Weekly #047 | Societal Progress Through the Lens of Driver's License Medical Examinations

• TipKit
• Gucci App on VisionPro
• App Size
• Darwin Notifications
• Custom Symbols in Control Center Widgets
• init of View
• UDP in SwiftNIO

Fatbobman's Swift Weekly #046 | Warning-Free Compilation is Not the Ultimate Goal of Swift 6

• EditorConfig in Xcode
• SwiftUI for Mac 2024
• Guide to Xcode Cloud
• Swift and WebAssembly
• From Highlighting to AI
• _ConditionalContent in List SubView

Fatbobman's Swift Weekly #045 | We Need More "Wukong"

• Codable and Enums in SwiftData Models
• Global Sheets Pattern in SwiftUI
• SwiftUI: Perception and Reality
• Emoji in 2024
• Disabling Xcode Asset Symbol Generation
• Insights on App Review

Compared to Core Data, SwiftData has fundamentally revolutionized the way data models are constructed. It not only supports a purely code-based declaration method but also allows the direct use of types conforming to the Codable protocol and enum types within models, which are its significant new features. Many developers are inclined to leverage these new capabilities because they seem to fit very well with the Swift language’s declaration style. However, a lack of understanding of the implementation details and potential limitations of these new features may lead to various issues in the future. This article aims to discuss several key points to consider when using Codable and enums in SwiftData models, helping developers avoid common pitfalls.

Fatbobman's Swift Weekly #044 | It's Time for a Summer Break

• Analyzing Grid Layout Issues
• Exploring Task Isolation Inheritance
• Interesting Swift Websites
• Customizing windows in SwiftUI
• Swift Concurrency
• Releasing Swift Binaries with Actions