SwiftUI lifecycle about cookbook

[aure]

You should be able to do this on your main ContentView() onAppear block.

[genedelisa]

import SwiftUI
import AVFoundation

@main
struct AVApp: App {
    
    #if os(macOS)
    @NSApplicationDelegateAdaptor(macOSNSAppDelegate.self) var appDelegate: NSAppDelegate
    #endif
    
    #if os(iOS)
    @UIApplicationDelegateAdaptor(iOSAppDelegate.self) var appDelegate
    #endif
    
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
    
}

#if os(iOS)
class iOSAppDelegate: UIResponder, UIApplicationDelegate {
    
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {
        
        do {
            try AVAudioSession.sharedInstance().setPreferredIOBufferDuration(1) // whatever
            try AVAudioSession.sharedInstance().setCategory(.playAndRecord,
                                                            options: [.defaultToSpeaker, .mixWithOthers])
            try AVAudioSession.sharedInstance().setActive(true)
        } catch let err {
            print(err)
        }
        return true
    }
}
#endif

#if os(macOS)
class macOSNSAppDelegate: NSObject, NSApplicationDelegate {
}
#endif

[aure]

Really depends on your application. It used to be that we wholeheartedly recommended one Conductor app for technical reasons, but now I just think it keeps things simpler.

[aure]

Thanks for the pointers @genedelisa

[transat]

Another quick question: in general is it preferable to initialise a Conductor class here and share it everywhere in the app or to have individual Conductors for each view, as per the Cookbook examples?