Sharing Core Data objects between iCloud users

At a glance

Project structure

Source bundle/
├── CoreDataCloudKitShare/
│   ├── CoreDataCloudKitShareApp.swift
│   └── SceneDelegate.swift
├── CoreDataCloudKitShareOnWatch/
│   ├── CoreDataCloudKitShareApp.swift
│   └── AppDelegate.swift
├── Persistence/
│   └── PersistenceController.swift
└── SwiftUI/
    ├── ParticipantView.swift
    ├── SwiftUIHelper.swift
    ├── TaggingView.swift
    ├── PhotoGridView.swift
    ├── RatingView.swift
    ├── AddToExistingShareView.swift
    └── FullImageView.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 8 project/configuration file(s) and 35 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["CoreDataCloudKitShare"]
    V2["CoreDataCloudKitShareOnWatch"]
    Boundary["CoreData APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

CoreDataCloudKitShare/CoreDataCloudKitShareApp.swift:11 — architecture anchor

@main
struct CoreDataCloudKitShareApp: App {
    @ApplicationDelegateAdaptor var appDelegate: AppDelegate

    private let persistentContainer = PersistenceController.shared.persistentContainer

    var body: some Scene {
        #if InitializeCloudKitSchema
        WindowGroup {
            Text("Initializing CloudKit Schema...").font(.title)
            Text("Stop after Xcode says 'no more requests to execute', " +
                 "then check with CloudKit Console if the schema is created correctly.").padding()
        }
        #else
        WindowGroup {
            PhotoGridView()
                .environment(\.managedObjectContext, persistentContainer.viewContext)
        }
        #endif
    }
}

Interpretation

The branches represent separate entry-bearing project variants in the downloaded bundle, not runtime calls between those variants. Each branch is intentionally collapsed at the documented framework boundary; the detailed target-local flow remains in the cited files. Ownership is claimed only where the next section cites a stored property or assignment.

Ownership and state

classDiagram
    CoreDataCloudKitShareApp o-- AppDelegate : appDelegate
    PersistenceController o-- Notification : cdcksStoreDidChange
    PersistenceController *-- PersistenceController : shared
    PersistenceController o-- NSPersistentCloudKitContainer : persistentContainer

Ownership evidence

CoreDataCloudKitShare/CoreDataCloudKitShareApp.swift:13 — stored dependency or nearest verified ownership anchor

@main
struct CoreDataCloudKitShareApp: App {
    @ApplicationDelegateAdaptor var appDelegate: AppDelegate
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

Persistence/PersistenceController+Photo.swift:138 — representative execution boundary

#if os(iOS) || os(macOS)
                let photo = await persistentContainer.viewContext.perform {
                    let coordinator = persistentContainer.viewContext.persistentStoreCoordinator
                    // ...
                }
#endif

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

CoreDataCloudKitShare/CoreDataCloudKitShareApp.swift:12 — representative type boundary

@main
struct CoreDataCloudKitShareApp: App {
    @ApplicationDelegateAdaptor var appDelegate: AppDelegate
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

CoreDataCloudKitShare/CoreDataCloudKitShareApp.swift:15 — representative boundary

@main
struct CoreDataCloudKitShareApp: App {
    // ...
    private let persistentContainer = PersistenceController.shared.persistentContainer
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: CoreDataCloudKitShareApp; Controller: PersistenceController; Delegate: AppDelegate, SceneDelegate; View: AddToExistingShareView, FullImageView, ManagingSharesView, ParticipantView, PhotoGridItemView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: participantListView, sectionHeader, sectionContent, toolbarItems, purgeShare, deleteParticipant, processStoreChangeNotification, addParticipant.
• Files: CoreDataCloudKitShare/CoreDataCloudKitShareApp.swift, CoreDataCloudKitShareOnWatch/CoreDataCloudKitShareApp.swift, Persistence/PersistenceController.swift, SwiftUI/ParticipantView.swift, SwiftUI/TaggingView.swift, SwiftUI/PhotoGridView.swift.

Architecture takeaways

• CoreDataCloudKitShareApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches CoreData, CloudKit, SwiftUI, UIKit through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation