Optimizing home electricity usage

At a glance

Project structure

Source bundle/
└── EnergyKitSampleApp/
    └── EnergyKitSampleApp/
        ├── EnergyKitSampleApp.swift
        ├── Models/
        │   ├── ElectricVehicle/
        │   │   ├── ElectricVehicleController.swift
        │   │   └── ElectricVehicle.swift
        │   └── EnergyVenueManager.swift
        ├── Views/
        │   ├── EV/
        │   │   ├── EVDetailsView.swift
        │   │   ├── EVView.swift
        │   │   └── Load Event/
        │   │       ├── LoadEventDetailView.swift
        │   │       └── LoadEventsView.swift
        │   ├── ChargingLocation/
        │   │   └── ChargingLocationView.swift
        │   └── Common/
        │       ├── AttributeValueTextView.swift
        │       └── UUIDTextView.swift
        └── ContentView.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 28 source declaration(s).

Overall architecture

flowchart LR
    N1["EnergyKitSampleApp"]
    N2["ContentView"]
    N3["EnergyVenueManager"]
    N4["EnergyKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

EnergyKitSampleApp/EnergyKitSampleApp/EnergyKitSampleApp.swift:11 — architecture anchor

@main
struct EnergyKitSampleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
        .modelContainer(for: ChargingLocation.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 EnergyKit.

Ownership and state

classDiagram
    ElectricVehicleController *-- DateInterval : chargingWindow
    ElectricVehicleController o-- TimeInterval : timestep
    ElectricVehicleController o-- ElectricVehicle : configuration
    ElectricVehicleController *-- Array : snapshots

Ownership evidence

EnergyKitSampleApp/EnergyKitSampleApp/Models/ElectricVehicle/ElectricVehicleController.swift:15 — stored dependency or nearest verified ownership anchor

    var chargingWindow: DateInterval = .init(start: Date(), end: Date().addingTimeInterval(60 * 60 * 10))
    /// An incremental portion of the simulation, in seconds.
    var timestep: TimeInterval = 60

    // MARK: Electric Vehicle (EV)
    /// The configuration of the EV.
    var configuration: ElectricVehicle
    /// The EV snapshots for UI purposes.
    var snapshots: [ElectricVehicle] = []

    // MARK: EnergyKit
    /// The EV load event session.
    var session: ElectricVehicleLoadEvent.Session?

    // Electricity Guidance
    /// The guidance stored at the EV.
    var currentGuidance: ElectricityGuidance {
        // ...
    }

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

EnergyKitSampleApp/EnergyKitSampleApp/Models/ElectricVehicle/ElectricVehicleController.swift:318 — representative execution boundary

    func submitEvents() async throws {
        try await currentVenue.submitEvents(events)
    }

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

EnergyKitSampleApp/EnergyKitSampleApp/EnergyKitSampleApp.swift:12 — representative type boundary

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

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

Access control

Reference code

EnergyKitSampleApp/EnergyKitSampleApp/Models/ElectricVehicle/ElectricVehicleController.swift:91 — representative boundary

    fileprivate func energyRequiredToFullCharge() -> Double {
        if configuration.properties.desiredStateOfCharge <= configuration.state.stateOfCharge {
            return 0
        }
        return configuration.properties.batteryCapacity * (configuration.properties.desiredStateOfCharge - configuration.state.stateOfCharge) / 100
    }

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: EnergyKitSampleApp; Controller: ElectricVehicleController; Manager: EnergyVenueManager; View: AttributeValueTextView, ChargingLocationView, ContentView, EVDetailsView, EVView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: setElectricityGuidance, setEnergyVenue, energyRequiredToFullCharge, calculateEVChargingSchedule, selectingChargingIntervals, selectCleanestChargingIntervals, guidanceIntervalIsInChargingWindow, simulateCharging.
• Files: EnergyKitSampleApp/EnergyKitSampleApp/EnergyKitSampleApp.swift, EnergyKitSampleApp/EnergyKitSampleApp/Models/ElectricVehicle/ElectricVehicleController.swift, EnergyKitSampleApp/EnergyKitSampleApp/Models/EnergyVenueManager.swift, EnergyKitSampleApp/EnergyKitSampleApp/Views/EV/EVDetailsView.swift, EnergyKitSampleApp/EnergyKitSampleApp/Models/ElectricVehicle/ElectricVehicle.swift, EnergyKitSampleApp/EnergyKitSampleApp/ContentView.swift.

Architecture takeaways

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