Sharing CloudKit Data with Other iCloud Users

At a glance

Project structure

Source bundle/
└── CloudKitShare/
    ├── AppDelegate.swift
    ├── Caches/
    │   ├── BaseLocalCache.swift
    │   ├── TopicLocalCache+ViewController.swift
    │   ├── TopicLocalCache.swift
    │   └── ZoneLocalCache+ViewController.swift
    ├── ViewControllers/
    │   ├── SpinnerViewController.swift
    │   ├── TopicSectionTitleView.swift
    │   ├── MainViewController.swift
    │   ├── NoteViewController.swift
    │   ├── ZoneViewController.swift
    │   └── MainViewController+SharingController.swift
    └── SceneDelegate.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 27 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["MainViewController"]
    N3["CloudKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

CloudKitShare/AppDelegate.swift:12 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {
    private var currentUserRecordID: CKRecord.ID?
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into CloudKit.

Ownership and state

classDiagram
    AppDelegate o-- ID : currentUserRecordID
    AppDelegate o-- ZoneLocalCache : zoneCacheOrNil
    AppDelegate o-- TopicLocalCache : topicCacheOrNil
    AppDelegate o-- CKContainer : container

Ownership evidence

CloudKitShare/AppDelegate.swift:14 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {
    private var currentUserRecordID: CKRecord.ID?
    // ...
}

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

CloudKitShare/Caches/BaseLocalCache.swift:83 — representative execution boundary

class BaseLocalCache {
    // ...
        return DispatchQueue(label: "LocalCache", attributes: .concurrent)
    // ...
}

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

CloudKitShare/AppDelegate.swift:13 — representative type boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {
    private var currentUserRecordID: CKRecord.ID?
    // ...
}

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

Access control

Reference code

CloudKitShare/AppDelegate.swift:14 — representative boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {
    private var currentUserRecordID: CKRecord.ID?
    // ...
}

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: Controller: MainViewController, NoteViewController, SpinnerViewController, ZoneViewController; Delegate: AppDelegate, SceneDelegate; View: TopicSectionTitleView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, updateWithNotificationUserInfo, userNotificationCenter, topicCacheForFirstZone, invalidateCurrentUser, buildZoneCacheIfNeed, zoneCacheDidChange, zoneDidSwitch.
• Files: CloudKitShare/AppDelegate.swift, CloudKitShare/Caches/BaseLocalCache.swift, CloudKitShare/ViewControllers/SpinnerViewController.swift, CloudKitShare/ViewControllers/TopicSectionTitleView.swift, CloudKitShare/SceneDelegate.swift, CloudKitShare/ViewControllers/MainViewController.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches CloudKit, UIKit, UserNotifications 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