Add rich graphics to your SwiftUI app

At a glance

Project structure

Source bundle/
└── Shared/
    ├── GradientBuilderApp.swift
    ├── Model/
    │   ├── GradientModel.swift
    │   └── GradientModelStore.swift
    └── Views/
        ├── ContentView.swift
        ├── GradientDetailView.swift
        ├── SystemColorPicker.swift
        ├── Visualizers/
        │   ├── Particles/
        │   │   ├── ParticleModel.swift
        │   │   └── Particle.swift
        │   ├── ShapeVisualizer.swift
        │   └── ParticleVisualizer.swift
        ├── GradientControl.swift
        └── Visualizer.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 6 project/configuration file(s) and 21 source declaration(s).

Overall architecture

flowchart LR
    N1["GradientBuilderApp"]
    N2["ContentView"]
    N3["GradientModelStore"]
    N4["SwiftUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Shared/GradientBuilderApp.swift:10 — architecture anchor

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

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
    Stop o-- Color : color
    Stop *-- Double : location
    Stop *-- Int : id
    Stop *-- Array : stops

Ownership evidence

Shared/Model/GradientModel.swift:14 — stored dependency or nearest verified ownership anchor

    struct Stop: Equatable, Identifiable {
        // ...
        var color: Color
        // ...
    }

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

Shared/GradientBuilderApp.swift:11 — representative type boundary

struct GradientBuilderApp: App {
    // ...
}

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

Access control

Reference code

Shared/GradientBuilderApp.swift:12 — representative boundary

@main
struct GradientBuilderApp: App {
    @State private var store = GradientModelStore.defaultStore
    // ...
}

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: GradientBuilderApp; Model: GradientModel, ParticleModel; Store: GradientModelStore; View: ContentView, GradientDetailView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: append, remove, update, add, make, forEachParticle, path.
• Files: Shared/GradientBuilderApp.swift, Shared/Model/GradientModel.swift, Shared/Views/ContentView.swift, Shared/Views/GradientDetailView.swift, Shared/Model/GradientModelStore.swift, Shared/Views/SystemColorPicker.swift.

Architecture takeaways

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