forkDaemon to start some long running work associated with the service but this results in a self-referential layer. For example:doBackgroundStuffWithTestService which obviously won't work. One solution could be to pass anything I need as function arguments to doBackgroundStuffWithTestService but that doesn't seem as clean as just consuming the service as things grow in complexity. DeviceStateService needs to forkDaemon a fiber to keep a subscription ref in sync with react-native's AppState.addEventListener.