Synchronizing a local store to the cloud

At a glance

Project structure

Source bundle/
├── CoreDataCloudKitDemo/
│   ├── AppDelegate.swift
│   ├── Detail/
│   │   ├── DetailViewController+Sharing.swift
│   │   ├── DetailViewController.swift
│   │   └── AttachmentInteractionDelegate.swift
│   ├── Tag/
│   │   └── TagsCollectionView.swift
│   ├── Attachment/
│   │   └── FullImageViewController.swift
│   └── DataProvider/
│       ├── AttachmentProvider.swift
│       ├── Data Generators/
│       │   └── LargeDataGenerator.swift
│       ├── PostProvider.swift
│       └── TagProvider.swift
└── CoreDataCloudKitDemoUnitTests/
    ├── Shared/
    │   └── CloudKitTestingSupport.swift
    └── Test Cases/
        └── TestMainViewController.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 7 project/configuration file(s) and 49 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["DetailViewController"]
    N3["InjectableCLLocationManager"]
    N4["AttachmentProvider"]
    N5["CoreData / CoreDataCloudKitDemo APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

CoreDataCloudKitDemo/AppDelegate.swift:13 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UISplitViewControllerDelegate {
    // ...
}

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 Core Data.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    AppDelegate *-- CLLocationManager : locationManager
    AppDelegate o-- CoreDataStack : coreDataStack
    AppDelegate o-- AppDelegate : sharedAppDelegate

Ownership evidence

CoreDataCloudKitDemo/AppDelegate.swift:16 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UISplitViewControllerDelegate {
    // ...
    var window: UIWindow?
    // ...
}

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.

Class and protocol design

CoreDataCloudKitDemo/Detail/DetailViewController+Sharing.swift:43 — representative type boundary

protocol SharingProvider {
    // ...
}

The source explicitly defines local protocol relationships: InjectableUserIdentity → RenderableUserIdentity, InjectableShareParticipant → RenderableShareParticipant, InjectableShare → RenderableShare, BlockBasedShareProvider → SharingProvider, CoreDataStack → SharingProvider, CKUserIdentity → RenderableUserIdentity.

Access control

Reference code

CoreDataCloudKitDemo/DataProvider/Attachment+Image.swift:27 — representative boundary

    private func thumbnailURL() -> URL {
        let fileName = uuid!.uuidString + ".thumbnail"
        return CoreDataStack.attachmentFolder.appendingPathComponent(fileName)
    }

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: DetailViewController, FullImageViewController, MainViewController, SpinnerViewController, TagPickerViewController; Delegate: AppDelegate, AttachmentInteractionDelegate, BlockFetchedResultsControllerDelegate, CLLocationManagerBlockDelegate, PostInteractionDelegate; Generator: LargeDataGenerator, TestLargeDataGenerator; Manager: InjectableCLLocationManager; Provider: AttachmentProvider, BlockBasedShareProvider, PostProvider, SharingProvider, TagProvider; Transformer: ColorTransformer, SecureCLLocationTransformer; View: TagsCollectionView.
• Protocols: SharingProvider, AttachmentInteractionDelegate, PostInteractionDelegate, RenderableUserIdentity, RenderableShareParticipant, RenderableShare.
• Methods: application, splitViewController, isShared, participants, shares, canEdit, canDelete, shareNoteAction.
• Files: CoreDataCloudKitDemo/AppDelegate.swift, CoreDataCloudKitDemo/Detail/DetailViewController.swift, CoreDataCloudKitDemo/Tag/TagsCollectionView.swift, CoreDataCloudKitDemoUnitTests/Test Cases/TestMainViewController.swift, CoreDataCloudKitDemo/Attachment/FullImageViewController.swift, CoreDataCloudKitDemo/DataProvider/AttachmentProvider.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches CoreData, UIKit, CoreDataCloudKitDemo, CloudKit 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.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation