Inyecte dependencias en ViewModels y repositorios

You registered dependencies and started Koin. Now comes the payoff: injecting those objects into your repositories and view models without building them by hand.

The cleanest style is constructor injection: list what a class needs as parameters, and Koin fills them via get() in the module.

Your repository simply declares its needs in the constructor. It never touches Koin, which keeps it easy to test in isolation.

A shared ViewModel takes the repository through its constructor too, so all of its data comes from one injected source.

Add the view model to your module. A factory fits well, giving each screen its own fresh instance.

On Android the koinViewModel() helper hands a Compose screen the wired-up view model in a single call.

From Swift you ask Koin for the same view model through a small bridge function, so SwiftUI gets an identically wired object. 🍏

Prefer constructor injection over calling get() deep inside classes. Hidden lookups make code harder to read, reuse, and test.

Depend on an interface and let Koin supply the implementation. Swapping in a fake for tests then becomes a one-line module change.

Notice the chain Koin assembles for you: client builds repo, repo builds use case, use case builds view model, all from constructors.

Because everything arrives through constructors, your tests just pass fakes directly, no Koin required, keeping unit tests fast and predictable.

Choose the cleanest injection style.

You injected dependencies through constructors into repos and view models, resolved them per platform, and saw why interfaces plus constructor injection make testing a breeze. 🎯