بدء Koin في Android وiOS

Declaring modules is only half the job. Each platform must start Koin at launch so the container is ready before anything asks for a dependency.

Put the common startup in shared code with a small initKoin function. Both platforms call it, so the wiring never drifts apart.

Give initKoin a parameter so each platform can append its own setup, like Android needing the application context.

On Android, call initKoin from your Application class so the graph exists for the whole process lifetime.

Android modules often need a Context. Pass it through the extra block using androidContext so definitions can resolve it.

Remember to point your manifest at the custom Application class, or onCreate never runs and Koin never starts.

On iOS you call the same initKoin through the generated framework, typically from your SwiftUI App init or AppDelegate.

Koin exposes a tiny helper so Swift can launch the graph in one clean line at app startup. 🍎

Call startKoin a single time per app launch. Starting it twice throws an error, so keep init in one obvious entry point.

Turn on printLogger during development so Koin prints what it builds, making missing-definition mistakes easy to spot.

The key idea: the same modules load from two platform entry points. Android uses its Application, iOS uses its App init, both share the wiring.

You exposed a shared initKoin, called it from Android's Application and iOS's App init, and learned to start it once with optional logging. The graph is live on both. ✅