Building rich SwiftUI text experiences

At a glance

Project structure

Source bundle/
└── SampleRecipeEditor/
    └── SampleRecipeEditor/
        ├── SampleRecipeEditorApp.swift
        ├── AttributeScopes.swift
        ├── AttributedStringModel.swift
        ├── BackgroundView.swift
        ├── InspectorView.swift
        ├── NavigationView.swift
        ├── RecipeFormattingDefinition.swift
        ├── RecipeView.swift
        ├── IngredientList.swift
        ├── RecipeList.swift
        ├── DispatchingChanges.swift
        └── EditableRecipeText.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 4 project/configuration file(s) and 32 source declaration(s).

Overall architecture

flowchart LR
    N1["SampleRecipeEditorApp"]
    N2["RootView"]
    N3["AttributedStringModel"]
    N4["SwiftUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

SampleRecipeEditor/SampleRecipeEditor/SampleRecipeEditorApp.swift:12 — architecture anchor

@main
struct SampleRecipeEditorApp: App {
    var body: some Scene {
        WindowGroup {
            RootView()
        }
        .modelContainer(for: Recipe.self)
    }
}

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
    IngredientNameAttributes o-- AdaptiveImageGlyphAttribute : adaptiveImageGlyph
    RecipeModelAttributes o-- CustomAttributes : custom
    RecipeModelAttributes o-- FontAttribute : font
    RecipeModelAttributes o-- IngredientNameAttributes : ingredientName

Ownership evidence

SampleRecipeEditor/SampleRecipeEditor/AttributeScopes.swift:17 — stored dependency or nearest verified ownership anchor

    struct IngredientNameAttributes: AttributeScope {
        let adaptiveImageGlyph: AttributeScopes.SwiftUIAttributes.AdaptiveImageGlyphAttribute
    }

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

SampleRecipeEditor/SampleRecipeEditor/BackgroundView.swift:67 — representative execution boundary

struct ImageWithPlaceholder<Placeholder: View>: View {
    // ...
            self.loadedImage = try? await Image(importing: imageData, contentType: .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

SampleRecipeEditor/SampleRecipeEditor/SampleRecipeEditorApp.swift:13 — representative type boundary

@main
struct SampleRecipeEditorApp: App {
    // ...
            RootView()
    // ...
}

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

Access control

Reference code

SampleRecipeEditor/SampleRecipeEditor/AttributedStringModel.swift:24 — representative boundary

@Model
final class AttributedStringModel: Identifiable {
    // ...
    private var valueChanged: Bool = false
    // ...
}

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: SampleRecipeEditorApp; Model: AttributedStringModel; View: BackgroundView, InspectorView, RecipeView, RootView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: initializeValue, willSave, hash, addIngredient, constrain.
• Files: SampleRecipeEditor/SampleRecipeEditor/SampleRecipeEditorApp.swift, SampleRecipeEditor/SampleRecipeEditor/AttributedStringModel.swift, SampleRecipeEditor/SampleRecipeEditor/BackgroundView.swift, SampleRecipeEditor/SampleRecipeEditor/InspectorView.swift, SampleRecipeEditor/SampleRecipeEditor/RecipeFormattingDefinition.swift, SampleRecipeEditor/SampleRecipeEditor/RecipeView.swift.

Architecture takeaways

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