Closed Nek-12 closed 4 months ago
Thanks for the idea. Similarly to #158 this would require creating a separate module just for this API. For now I would like to avoid one-API modules, considering the simplicity of the API. I will keep this in mind as well.
For desktop apps that don't need to use Decompose, but want to use Essenty for lifecycle handling, having LifecycleController in the Decompose introduces unnecessary overhead of depending on the whole library just for the lifecycle functionality. Consider moving functionality that allows to provide Essenty lifecycle for desktop, compose and other platforms to a separate module in Essenty instead of Decompose.