Synchronizing App Preferences with iCloud

At a glance

Project structure

Source bundle/
├── PrefsInCloud_iOS/
│   ├── AppDelegate.swift
│   ├── ColorsTableViewController.swift
│   ├── ViewController.swift
│   └── Base.lproj/
│       ├── LaunchScreen.storyboard
│       └── Main.storyboard
├── PrefsInCloud_macOS/
│   ├── AppDelegate.swift
│   └── ViewController.swift
├── Shared/
│   ├── Colors.swift
│   └── ViewController+KVS.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── PrefsInCloud.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

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 10 project/configuration file(s) and 6 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["PrefsInCloud_iOS"]
    V2["PrefsInCloud_macOS"]
    Boundary["UIKit / Cocoa APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

PrefsInCloud_iOS/AppDelegate.swift:10 — architecture anchor

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

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
    AppDelegate o-- UIWindow : window
    ColorsTableViewController o-- IndexPath : selectedIndexPath
    ViewController o-- NSPopUpButton : popupButton

Ownership evidence

PrefsInCloud_iOS/AppDelegate.swift:12 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    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.

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.

No source-visible execution, scheduling, or synchronization boundary was found in the indexed source.

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

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

PrefsInCloud_iOS/AppDelegate.swift:11 — representative type boundary

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

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

Access control

Reference code

PrefsInCloud_macOS/ViewController.swift:12 — representative boundary

class ViewController: NSViewController {
    // ...
    @IBOutlet private weak var popupButton: NSPopUpButton!
    // ...
}

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: ColorsTableViewController, ViewController; Delegate: AppDelegate.
• Protocols: no local protocol declaration in the scanned source.
• Methods: viewWillAppear, tableView, viewDidLoad, updateUserInterface, unwindToMenu, prepare, popupColorAction, prepareKeyValueStoreForUse.
• Files: PrefsInCloud_iOS/AppDelegate.swift, PrefsInCloud_macOS/AppDelegate.swift, PrefsInCloud_iOS/ColorsTableViewController.swift, PrefsInCloud_iOS/ViewController.swift, PrefsInCloud_macOS/ViewController.swift.

Architecture takeaways

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