just make sure to call startForeground() from the service within 5 seconds of launch

this is needed for Android Oreo's background service limitation

but yeah if the app is in background without any foreground service and waiting for the state to change (from a thread), it is more likely to be killed

Rational behind is, I have a very stateful api, that is guared by statemachine. However if this api sits inside the service, and somebody misuses it, i.e calls wrong method at wrong time, that means the intent is routed through service, and albeit state machine refuses the input, it already started the service, since any intent will (and I cant just stopSelf if statemachine rules invalid, as the state could be ongoing, which would cancel it) and there fore it is sitting in memory for no reason

So statemachine needs to sit before service, but I dont feel comfortable having no machine behind it as well, and all in all that domain > android > domain sandwich feels bad

But if I were just to not deal with the service, code would call my foomanager directly, where the inputs would be guarded by statemachine, but inside foomanager so its transparent

and service would be only be mirrored, i.e. only started when call is ongoing, stopped when call hanguped, and only setting startForeground stopForeground, and nothing else

do you know what I mean? usually service has your object reference, and you send intents to service, and service routes those intents to your object's methods

problem is not in the service, its about the design, wether do you put your callManager inside it, or next to it horizontally so to speak

so then the different is just the importance of your app for Android (foreground service would give more lifetime than a bound service using application context)

anyways, that is out of the way

And for your design, yes an empty foreground service is just fine

but would help out my code greatly, since i would have 1. have parcelable objects in order to be sent through intent, 2. dont have to have stupid logic like "if statemachine refused input and call state is disconnected then stopself)

tldr; service instance as a sideeffect vs. service instance as a facade infront