Building a document-based app using SwiftData

At a glance

Project structure

Source bundle/
├── End/
│   └── FlashCard/
│       ├── SwiftDataFlashCardSample.swift
│       └── Views/
│           ├── CardEditorView.swift
│           ├── CardContainerView.swift
│           ├── CardReaderView.swift
│           ├── ContentView.swift
│           └── FlashCardView.swift
└── Start/
    └── FlashCard/
        ├── SwiftDataFlashCardSample.swift
        └── Views/
            ├── CardEditorView.swift
            ├── CardContainerView.swift
            ├── CardReaderView.swift
            ├── ContentView.swift
            └── FlashCardView.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 10 project/configuration file(s) and 34 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["End"]
    V2["Start"]
    Boundary["SwiftUI APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

End/FlashCard/SwiftDataFlashCardSample.swift:11 — architecture anchor

@main
struct SwiftDataFlashCardSample: App {
    // ...
}

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
    CardEditorView o-- Card : card
    CardEditorView o-- FocusedField : focusedField
    CardContainerView o-- Content : content
    CardReaderView o-- Color : color

Ownership evidence

End/FlashCard/Views/CardEditorView.swift:11 — stored dependency or nearest verified ownership anchor

struct CardEditorView: View {
    @Bindable var card: Card
    // ...
}

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

End/FlashCard/Views/CardEditorView.swift:10 — representative type boundary

struct CardEditorView: View {
    // ...
}

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

Access control

Reference code

End/FlashCard/Views/CardCarousel.swift:13 — representative boundary

    @State private var selectedCardID: PersistentIdentifier?
    @FocusState private var focusCardID: PersistentIdentifier?
    private let initialCardID: PersistentIdentifier

    let editing: Bool
    var cards: [Card]

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: View: CardContainerView, CardEditorView, CardReaderView, ContentView, FlashCardView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: makeBody.
• Files: End/FlashCard/SwiftDataFlashCardSample.swift, Start/FlashCard/SwiftDataFlashCardSample.swift, End/FlashCard/Views/CardEditorView.swift, Start/FlashCard/Views/CardEditorView.swift, End/FlashCard/Views/CardContainerView.swift, End/FlashCard/Views/CardReaderView.swift.

Architecture takeaways

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