Adding Shortcuts for Wind Down

At a glance

Project structure

Source bundle/
├── Bedtime/
│   ├── AppDelegate.swift
│   ├── LibraryTableViewController.swift
│   └── TrackTableViewController.swift
├── BedtimeIntents/
│   ├── PlayMediaIntentHandler.swift
│   └── IntentHandler.swift
└── BedtimeKit/
    ├── AudioPlaybackManager.swift
    ├── SoundLibraryDataManager.swift
    ├── LibraryItem.swift
    ├── DataTypes+Intents.swift
    ├── PlayRequest.swift
    ├── Segment.swift
    └── SoundLibrary.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 10 project/configuration file(s) and 16 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["LibraryTableViewController"]
    N3["AudioPlaybackManager"]
    N4["IntentHandler"]
    N5["Intents APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

Bedtime/AppDelegate.swift:12 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder {

    var window: UIWindow?
    var audioManager: AudioPlaybackManager?
}

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 Intents.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    AppDelegate o-- AudioPlaybackManager : audioManager
    SoundLibraryTableViewCell o-- UIImageView : libraryItemImageView
    SoundLibraryTableViewCell o-- UILabel : libraryItemTitleLabel

Ownership evidence

Bedtime/AppDelegate.swift:15 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder {

    var window: UIWindow?
    var audioManager: AudioPlaybackManager?
}

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.

Class and protocol design

BedtimeKit/LibraryItem.swift:11 — representative type boundary

public protocol LibraryItem {
    var itemID: LibraryItemID { get }
    var title: String { get }
}

The source explicitly defines local protocol relationships: Soundscape → LibraryItem, Track → LibraryItem, Track → LibraryItem, Soundscape → MediaItemConvertible, Track → MediaItemConvertible.

Access control

Reference code

Bedtime/LibraryTableViewController.swift:34 — representative boundary

    private lazy var libraryManager: SoundLibraryDataManager = {
        let libraryManager = SoundLibraryDataManager.shared
        
        return libraryManager
    }()

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: Controller: LibraryTableViewController, TrackTableViewController; Delegate: AppDelegate; Handler: IntentHandler, PlayMediaIntentHandler; Manager: AudioPlaybackManager, SoundLibraryDataManager.
• Protocols: LibraryItem, MediaItemConvertible.
• Methods: application, confirm, handle, awakeFromNib, stopPlayback, prepare, restoreUserActivityState, viewDidLoad.
• Files: Bedtime/AppDelegate.swift, BedtimeIntents/PlayMediaIntentHandler.swift, Bedtime/LibraryTableViewController.swift, Bedtime/TrackTableViewController.swift, BedtimeIntents/IntentHandler.swift, BedtimeKit/AudioPlaybackManager.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches Intents, BedtimeKit, UIKit, AVFoundation 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.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation