Emoji Rangers: Supporting Live Activities, interactivity, and animations

At a glance

Project structure

Source bundle/
├── Emoji Rangers/
│   ├── EmojiRangersApp.swift
│   ├── Shared/
│   │   └── Views/
│   │       ├── AdventureLiveActivityView.swift
│   │       └── AvatarView.swift
│   ├── Game Status/
│   │   ├── AdventureView.swift
│   │   └── AdventureViewModel.swift
│   └── ContentView.swift
├── EmojiRangersWatchApp/
│   ├── EmojiRangersWatchApp.swift
│   └── ContentView.swift
├── EmojiRangerWidgetExtension/
│   ├── EmojiRangersWidgetBundle.swift
│   ├── EmojiRangersWidget.swift
│   └── LeaderboardWidget.swift
└── App Intent/
    └── EmojiRangerSelection.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: C/Objective-C header, Swift.
• The verified tree contains 11 project/configuration file(s) and 44 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["Emoji Rangers"]
    V2["EmojiRangerWidgetExtension"]
    V3["EmojiRangersWatchApp"]
    Boundary["WidgetKit APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary
    Bundle --> V3
    V3 --> Boundary

Reference code

Emoji Rangers/EmojiRangersApp.swift:10 — architecture anchor

@main
struct EmojiRangersApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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
    AdventureLiveActivityContent o-- EmojiRanger : hero
    AdventureLiveActivityContent *-- Bool : isStale
    AdventureLiveActivityContent o-- ContentState : contentState
    AdventureLiveActivityView o-- EmojiRanger : hero

Ownership evidence

Emoji Rangers/Shared/Views/AdventureLiveActivityView.swift:14 — stored dependency or nearest verified ownership anchor

#if canImport(ActivityKit)
struct AdventureLiveActivityContent: View {
    let hero: EmojiRanger
    // ...
}
#endif

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

App Intent/EmojiRangerSelection.swift:23 — representative execution boundary

        func results() async throws -> [EmojiRanger] {
            EmojiRanger.allHeros
        }

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

Emoji Rangers/EmojiRangersApp.swift:11 — representative type boundary

@main
struct EmojiRangersApp: App {
    // ...
            ContentView()
    // ...
}

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

Access control

Reference code

Emoji Rangers/ContentView.swift:12 — representative boundary

struct ContentView: View {
    // ...
    @State private var selection: EmojiRanger?
    // ...
}

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: EmojiRangersApp, EmojiRangersWatchAppApp; Provider: AppIntentProvider, EmojiRangerOptionsProvider, LeaderboardProvider; View: AdventureLiveActivityView, AdventureView, AllCharactersView, AvatarView, ContentView; ViewModel: AdventureViewModel.
• Protocols: no local protocol declaration in the scanned source.
• Methods: loadAdventure, startAdventureButtonTapped, updateAdventureButtonTapped, endAdventureButtonTapped, endActivity, setup, observeActivity, updateAdventure.
• Files: Emoji Rangers/EmojiRangersApp.swift, Emoji Rangers/Shared/Views/AdventureLiveActivityView.swift, EmojiRangerWidgetExtension/EmojiRangersWidgetBundle.swift, Emoji Rangers/Game Status/AdventureView.swift, App Intent/EmojiRangerSelection.swift, Emoji Rangers/ContentView.swift.

Architecture takeaways

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