Adopting drag and drop using SwiftUI

At a glance

Project structure

Source bundle/
└── AdoptingDragAndDropInASwiftUIApp/
    ├── AdoptingDragAndDropInASwiftUIAppApp.swift
    ├── Models/
    │   ├── DataModel.swift
    │   ├── Constants.swift
    │   └── Contact.swift
    └── Views/
        ├── ContactDetailView.swift
        ├── ContactInfoView.swift
        ├── HeaderView.swift
        ├── ContentView.swift
        ├── ThumbnailView.swift
        ├── ContactsTable.swift
        ├── ContactList.swift
        └── DisplayModePicker.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 5 project/configuration file(s) and 18 source declaration(s).

Overall architecture

flowchart LR
    N1["AdoptingDragAndDropInASwiftUIAppApp"]
    N2["ContentView"]
    N3["DataModel"]
    N4["SwiftUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

AdoptingDragAndDropInASwiftUIApp/AdoptingDragAndDropInASwiftUIAppApp.swift:10 — architecture anchor

@main
struct AdoptingDragAndDropInASwiftUIApp: App {
    @State private var dataModel = DataModel()

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environment(dataModel)
            // Set minimum window size.
            #if os(macOS) || os(visionOS)
                .frame(minWidth: Constants.contentWindowWidth, maxWidth: .infinity, minHeight: Constants.contentWindowHeight, maxHeight: .infinity)
            #endif
        }
        .windowResizability(.contentSize)
    }
}

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

Ownership and state

classDiagram
    AdoptingDragAndDropInASwiftUIApp *-- DataModel : dataModel
    DataModel *-- Array : contacts
    DataModel o-- DisplayMode : displayMode
    Video *-- URL : url

Ownership evidence

AdoptingDragAndDropInASwiftUIApp/AdoptingDragAndDropInASwiftUIAppApp.swift:12 — stored dependency or nearest verified ownership anchor

@main
struct AdoptingDragAndDropInASwiftUIApp: App {
    @State private var dataModel = DataModel()
    // ...
}

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

AdoptingDragAndDropInASwiftUIApp/Models/Contact.swift:44 — representative execution boundary

    static var transferRepresentation: some TransferRepresentation {
        // ...
            try await parseVCardData(data)
        // ...
    }

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

AdoptingDragAndDropInASwiftUIApp/AdoptingDragAndDropInASwiftUIAppApp.swift:11 — representative type boundary

@main
struct AdoptingDragAndDropInASwiftUIApp: App {
    @State private var dataModel = DataModel()
    // ...
}

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

Access control

Reference code

AdoptingDragAndDropInASwiftUIApp/AdoptingDragAndDropInASwiftUIAppApp.swift:12 — representative boundary

@main
struct AdoptingDragAndDropInASwiftUIApp: App {
    @State private var dataModel = DataModel()
    // ...
}

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: AdoptingDragAndDropInASwiftUIApp; Model: DataModel; View: CompactContactView, ContactDetailView, ContactInfoView, ContentView, HeaderView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: handleDroppedContacts, loadImage, loadItem, copyLibraryFile, makeBody.
• Files: AdoptingDragAndDropInASwiftUIApp/Models/DataModel.swift, AdoptingDragAndDropInASwiftUIApp/Views/ContactDetailView.swift, AdoptingDragAndDropInASwiftUIApp/Views/ContactInfoView.swift, AdoptingDragAndDropInASwiftUIApp/Views/HeaderView.swift, AdoptingDragAndDropInASwiftUIApp/Views/ContentView.swift, AdoptingDragAndDropInASwiftUIApp/Views/ThumbnailView.swift.

Architecture takeaways

• AdoptingDragAndDropInASwiftUIAppApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, Contacts, PhotosUI, UniformTypeIdentifiers 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