Which module should be responsible for configuring the WorkManager instance? If such a module exists, wouldn’t it need to depend on all modules that need workers? Wouldn’t that break the “ low cohesion” principle when modularizing apps? It would, so instead, we lean on another software engineering principle: delegation. Things get more nuanced in a multi-module app.
You can also implement a WorkerFactory to aid in dependency injection when using WorkManager with Hilt.
To provide custom configuration for this instance in a single module app, you can implement a Configuration.Provider that provides parameters for the Executor used to perform work. WorkManager exists as a singleton instance. This blog post details how we set up WorkManager for use in the multi module Now in Android app. This is often convenient, but in a modularized app where different modules often have different dependencies, WorkManager’s default configuration may not be enough. WorkManager provides a default configuration that is applied on app start up. Modularization is a great tool for building an app at scale, however care must be taken to ensure that resources shared between modules are properly instantiated.
0 kommentar(er)
