
Apps uploaded to App Store Connect must be built with Xcode 16 or later using an SDK for iOS 18, iPadOS 18, tvOS 18, visionOS 2, or watchOS 11.Learn about submitting apps

A community to discuss iOS, macOS, watchOS, tvOS, and visionOS development. Ask questions. Share articles. Share links to open source projects. Links to commercial projects are acceptable if it is not self-promotional in nature.
For now, it is okay to ask for feedback on an app. Please be considerate and do not spam the community.
Let's ship some .NET iOS & Android apps! CI/CD Deep Dive | Merge Conflict ep. 454
Click to view this content.
Apple to require Xcode 16 and Sonoma 14.5 to submit to the App Store starting on April 24, 2025
Apps uploaded to App Store Connect must be built with Xcode 16 or later using an SDK for iOS 18, iPadOS 18, tvOS 18, visionOS 2, or watchOS 11.Learn about submitting apps
Apps uploaded to App Store Connect must be built with Xcode 16 or later.
Swift Polyglot, an open source tool to check localizable strings
Contribute to appdecostudio/SwiftPolyglot development by creating an account on GitHub.
SwiftUI's scrollTargetBehavior provides precise scrolling control, but default paging misaligns in landscape mode. This article explores its limitations and implements a custom ScrollTargetBehavior for perfect paging alignment.
SwiftUI's scrollTargetBehavior provides precise scrolling control, but default paging misaligns in landscape mode. This article explores its limitations and implements a custom ScrollTargetBehavior for perfect paging alignment
Splito - Divide, Conquer & Enjoy Together! 💰
Simplify group expense management with Splito, the ultimate open-source solution to track, split, and settle shared costs seamlessly.
Why Choose Splito?
Splito makes managing group expenses with friends, family, or colleagues effortless:
Features You'll Love:
Download Now & Start Splitting Fairly! https://apps.apple.com/in/app/splito-split-enjoy-together/id6477442217
Exciting Upcoming Features �*
We’d love to hear your thoughts to help us make it even better!
Explore the Project! 👇
GitHub Copilot for Xcode in public preview
We are excited to announce that GitHub Copilot for Xcode is now available in public preview. This is a major milestone in our ongoing mission to make Copilot an essential…
Flutter has been forked to Flock
The Flutter team has a labor shortage. We're forking Flutter so that the community can accelerate Flutter's development.
Fatbobman's Swift Weekly #051 | Xcode Is Not Alone
Explore NSManagedObjectID and PersistentIdentifier in Core Data and SwiftData. Learn their features, usage, and how to manage data object identity efficiently.
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?
Explore how to use Swift Charts’ advanced APIs for precise data binning. Learn about NumberBins and DateBins for efficient data processing and visualization. Discover how to improve app performance.
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
Apple Watch, The Sturdy Linchpin of the Apple Ecosystem
Fatbobman's Swift Weekly #048 | Apple Watch, The Sturdy Linchpin of the Apple Ecosystem
Societal Progress Through the Lens of Driver's License Medical Examinations
Fatbobman's Swift Weekly #047 | Societal Progress Through the Lens of Driver's License Medical Examinations
Warning-Free Compilation is Not the Ultimate Goal of Swift 6
Fatbobman's Swift Weekly #046 | Warning-Free Compilation is Not the Ultimate Goal of Swift 6
Fatbobman's Swift Weekly #045 | We Need More "Wukong"
Accessible HVStack in SwiftUI
publication croisée depuis : https://programming.dev/post/18354166
A small publication with a Swift gist about a SwiftUI custom View which will swing to HStack or VStack dependent to the dynamic type size.
Accessibility settings nuggets from iOS 18
publication croisée depuis : https://programming.dev/post/18354171
Some details about improvements in accessibility features embedded within iOS 18
Explore key considerations for using Codable and enums in SwiftData models. Learn how SwiftData handles Codable, query predicates, and potential pitfalls to avoid.
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