Effect.Service Pattern for Multiple "Live" Implementations

in our system we provide multiple "live" implementations of some layers, notably when we're running the effect in the browser vs on the server. Does the newer Effect.Service pattern work in that situation or it's more just a convenience for Live + Test implementations ?