Synchronizing documents in the iCloud environment

At a glance

Project structure

Source bundle/
└── SimpleiCloudDocument/
    ├── AppDelegate.swift
    ├── Detail/
    │   ├── Document.swift
    │   ├── DetailViewController.swift
    │   ├── ImageViewController.swift
    │   ├── DetailViewController+CollectionView.swift
    │   └── ImageCVCell.swift
    ├── Main/
    │   ├── MainViewController.swift
    │   ├── MetadataProvider.swift
    │   ├── MainViewController+Document.swift
    │   ├── MainViewController+TableView.swift
    │   └── DiffableMetadataSource.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 7 project/configuration file(s) and 17 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["DetailViewController"]
    N3["Document"]
    N4["MetadataProvider"]
    N5["UIKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

SimpleiCloudDocument/AppDelegate.swift:10 — architecture anchor

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
    func application(_ application: UIApplication,
                     didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        return true
    }
    // ...
}

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 UIKit.

Ownership and state

classDiagram
    Changes o-- DispatchQueue : accessQueue
    Changes *-- Dictionary : _fileWrappersUnderRoot
    Changes *-- Changes : _unsavedUserChanges
    Changes *-- Changes : unpresentedPeerChanges

Ownership evidence

SimpleiCloudDocument/Detail/Document.swift:36 — stored dependency or nearest verified ownership anchor

    private lazy var accessQueue: DispatchQueue = {
        return DispatchQueue(label: "Document", attributes: .concurrent)
    }()

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

SimpleiCloudDocument/Detail/DetailViewController+CollectionView.swift:28 — representative execution boundary

            DispatchQueue.main.async {
                // ...
                    self.presentImageViewController(image: image)
                // ...
            }

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

SimpleiCloudDocument/Detail/ImageCVCell.swift:10 — representative type boundary

protocol ImagCVCellDelegate: AnyObject {
    func deleteCell(_ cell: UICollectionViewCell)
}

The source explicitly defines local protocol relationships: DetailViewController → ImagCVCellDelegate.

Access control

Reference code

SimpleiCloudDocument/Detail/DetailViewController+CollectionView.swift:26 — representative boundary

    private func retrieveAndPresentImage(with imageName: String) {
        // ...
                    self.presentImageViewController(image: image)
        // ...
    }

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, ImageViewController, MainViewController; Delegate: AppDelegate, ImagCVCellDelegate, SceneDelegate; Document: Document; Provider: MetadataProvider.
• Protocols: ImagCVCellDelegate.
• Methods: application, clear, load, contents, save, revert, accommodatePresentedItemDeletion, handleError.
• Files: SimpleiCloudDocument/AppDelegate.swift, SimpleiCloudDocument/Detail/Document.swift, SimpleiCloudDocument/Main/MainViewController.swift, SimpleiCloudDocument/Main/MetadataProvider.swift, SimpleiCloudDocument/Detail/DetailViewController.swift, SimpleiCloudDocument/Detail/ImageViewController.swift.

Architecture takeaways

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

Source map

• Official Apple documentation