Tyler Stromberg

I think it'd be _easier_ if we tied this to `Worker`, but we could build it more generally: ```swift public struct LifecycleWorker { let key: AnyHashable let onStarted: () ->...

Why would we _not_ want to store state in `State`? I get that it's more boilerplate, but having these side channels feels antithetical to a lot of the consolidation work...

IIRC, they're in `Samples` currently because we explicitly _don't_ want them to be added as dependencies elsewhere — they're just guideposts to help others build their own containers. Outside of...

One of the suggestions @bencochran brought up internally was the option of us publishing the structs for these `Screen`s (instead of both the struct and the UIViewController) and allowing folks...