Creating an App for Face-Painting in AR

At a glance

Project structure

Source bundle/
└── FacePainting/
    ├── ContentView.swift  # ContentView, ARViewContainer, DrawingViewContainer
    └── AppDelegate.swift  # FacePainting

Structure observations

• The runtime boundary is WindowGroup + SwiftUI/UIKit host; the tree is pruned to lifecycle, state, framework, rendering, and ECS files.
• The source is Swift; role-named types and feature folders separate the major responsibilities.

Overall architecture

flowchart LR
    FacePainting_1["FacePainting"]
    WindowGroup___SwiftUI_UIKit_host_2["WindowGroup + SwiftUI/UIKit host"]
    FacePaintingView_3["FacePaintingView"]
    RealityKit_entity_graph_4["RealityKit entity graph"]
    AR_face_tracking___PencilKit_material_5["AR face tracking + PencilKit material"]
    FacePainting_1 --> WindowGroup___SwiftUI_UIKit_host_2
    WindowGroup___SwiftUI_UIKit_host_2 --> FacePaintingView_3
    FacePaintingView_3 --> RealityKit_entity_graph_4
    RealityKit_entity_graph_4 --> AR_face_tracking___PencilKit_material_5

Reference code

FacePainting/AppDelegate.swift:12 — executable or app-lifecycle anchor.

struct FacePainting: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

The diagram is a responsibility flow, not a claim that every adjacent node directly calls the next. It separates lifecycle, presentation, stable state, framework/session work, and the RealityKit entity graph.

Ownership and state

classDiagram
    FacePaintingView --> HasModel : faceEntity
    FacePaintingView *-- EntityQuery : sceneUnderstandingQuery
    FacePaintingView --> UITouch : lastTouchPoint
    FacePaintingView --> Cancellable : subscription

Ownership evidence

FacePainting/ContentView.swift:156 — representative stored state or nearest verified lifecycle anchor.

class FacePaintingView: ARView {
    // ...
    var faceEntity: HasModel? = nil
    // ...
}

Ownership is intentionally narrow: environment, bindings, observed objects, weak links, and delegate callbacks do not prove lifetime ownership. Initialized stored services and wrapper-managed state do; entities added inside a RealityKit content closure belong to that entity graph.

Class and protocol design

The reviewed source defines no local substitution protocol. Its App, View, delegate, renderer, ARKit, and RealityKit conformances are framework-facing contracts, so this document does not label the whole app protocol-oriented.

Access control

No reviewed Swift access example uses fileprivate, private(set), open; declarations without a modifier are internal.

Reference code

FacePainting/ContentView.swift:16 — representative visibility boundary.

struct ContentView: View {
    @State private var showPicker = true
    // ...
}

Logic ownership and placement

Design patterns

Naming conventions

• Role suffixes are evidence, not decoration: View: ContentView, FacePaintingView.
• Protocols: no app-defined protocol in the reviewed source.
• Commands use verb-led methods: makeUIView, updateUIView, transform, setup, updateFaceTextureWithLatestDrawing, updateFaceEntityTextureUsing, setDrawingUndoable, findFaceEntity.
• Files and folders use primary-type or responsibility names such as Views, Models, Rendering, Components, Systems, Packages, or feature names where those boundaries exist.

Architecture takeaways

• Treat FacePainting as the owner of executable or scene lifecycle, not automatically as the owner of every entity created later.
• Keep view/controller input near presentation, but move sessions, reconstruction, capture, rendering, shared game state, or documents into stable owners when their lifetime exceeds one callback or render pass.

Source map

• Official Apple documentation