Origami: Crafting a dynamic tutorial for Apple Intelligence

At a glance

Project structure

Source bundle/
└── Origami/
    ├── OrigamiApp.swift
    ├── Brainstorm/
    │   ├── BrainstormView.swift
    │   └── BrainstormModel.swift
    ├── Terms/
    │   ├── TermView.swift
    │   └── TermModel.swift
    ├── Tutorial/
    │   ├── Views/
    │   │   └── TutorialStepTextView.swift
    │   ├── Models/
    │   │   └── TutorialGenerationModel.swift
    │   └── Intelligence/
    │       └── CraftTools.swift
    ├── Projects/
    │   └── LibraryView.swift
    ├── UI/
    │   └── Photos/
    │       └── PhotoView.swift
    └── Coach/
        ├── CoachModel.swift
        └── CoachView.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 134 source declaration(s).

Overall architecture

flowchart LR
    N1["OrigamiApp"]
    N2["ContentView"]
    N3["TutorialTemplateStore"]
    N4["GlyphRevealTextRenderer"]
    N5["FoundationModels APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

Origami/OrigamiApp.swift:12 — architecture anchor

@main
struct OrigamiApp: App {

    // Store the data model in app state so SwiftUI creates and owns a single
    // instance for the lifetime of the app.
    @State private var dataModel = DataModel()

    var body: some Scene {
        WindowGroup {
            ContentView()
                .task {
                    do {
                        try dataModel.prepareData()
                    } catch {
                        logger.error("Failed to prepare the app's data: \(error)")
                    }
                }
        }
        // Add the model container to the environment so views can query and update SwiftData.
        .modelContainer(dataModel.modelContainer)
    }
}

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 Foundation Models.

Ownership and state

classDiagram
    BrainstormOptionRow *-- Int : index
    BrainstormOptionRow o-- BrainstormIdea : idea
    BrainstormModel o-- Project : project
    BrainstormModel o-- ModelContext : modelContext

Ownership evidence

Origami/Brainstorm/BrainstormView.swift:106 — stored dependency or nearest verified ownership anchor

struct BrainstormOptionRow: View {
    let index: Int
    // ...
}

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

Origami/Brainstorm/BrainstormIdea.swift:12 — representative execution boundary

@Generable(description: "A single brainstorm idea")
struct BrainstormIdea: Identifiable, Sendable {
    let id = UUID()
    var title: String
    var description: String
}

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

Origami/OrigamiApp.swift:13 — representative type boundary

@main
struct OrigamiApp: 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

Origami/Brainstorm/BrainstormModel.swift:47 — representative boundary

    private static func decodeIdeas(from data: Data?) -> [BrainstormIdea] {
        guard let data,
            let snapshots = try? JSONDecoder().decode([IdeaSnapshot].self, from: data)
        // ...
    }

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: OrigamiApp; Model: BrainstormModel, CoachModel, DataModel, ProjectModel, SettingsModel; Recorder: TranscriptRecorder; Renderer: GlyphRevealTextRenderer; Store: TutorialTemplateStore; View: BrainstormView, ButtonBackgroundView, CheckMarkView, CoachView, ContentView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: reduce, playReveal, draw, applyReorder, instantImage, photoImage, instantCaption, setCraftDomain.
• Files: Origami/OrigamiApp.swift, Origami/Brainstorm/BrainstormView.swift, Origami/Terms/TermView.swift, Origami/Tutorial/Views/TutorialStepTextView.swift, Origami/Projects/LibraryView.swift, Origami/UI/Photos/PhotoView.swift.

Architecture takeaways

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