Full Guide to Dependency Injection With Koin for Compose Multiplatform - KMP for Beginners

preview_player
Показать описание
In this video you'll find a full guide to Dependency Injection With Koin for Compose Multiplatform!

💻 Let me be your mentor and become an industry-ready Android developer in 10 weeks:

⭐ Courses with real-life practices
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:

Get my FREE PDF about 20 things you should never do in Jetpack Compose:

Get the source code on GitHub:

Join my Discord server:
Рекомендации по теме
Комментарии
Автор

Jetbrain KMP should contract with you to produce their videos because you are the best at it ❤😍

zakariabouchantouf
Автор

Hi Philipp, can you make a video on how to use swift UI components with compose multiplatform. Like implementing AdMob on iOS and android.

tzstudios
Автор

Great video. Super useful! Thanks for the this series.

DaleHawkins
Автор

very simple example and koin is a service locator pattern😊 Good work!

yaroslavglonin
Автор

Great videos, you've been doing lately regarding KMP lets go :D

osmanmusse
Автор

Plz include desktop for compose multi platform in your videos. Thanks for great stuff !!!

mikelantzelo
Автор

Plz continue and tell us how to select files or images and open the camera and read or write qrcode and more


Thank you for your support

meshoraouf
Автор

Great video. Thoughts on Koin Annotations? Would be great to see a part 2 using it 😀

aiders
Автор

@PhilippLackner

Can i leverage koin and viewModel in a case where I am sharing logic but not UI (maybe am just looking to share a little UI across all platforms, e.g a button)

Also can I share just viewModels only across all platforms.

Thanks

olalekanraheem
Автор

Hello Philip really helpful your videos. Kotlin multiplatform could also work with interfaces too. I'd prefer this approach because it's more "object oriented" way than expect/actual mechanism. What do you think about this are there any drawbacks on using interfaces instead of expect/actual?

andreaslinis
Автор

@PhilippLackner Please arrange the playlist, because it is not in order. ▶

YaMehdi
Автор

Can you make video about di scopes please? What if I don‘t want to create everything as ‘single‘ or in which scenario should we use singleton? I couldn’t find any helpful guide on it

wkhklnb
Автор

Android team made ViewModel multiplatform too, I guess that's why you were able to put that definition to the common module. Would be nice to see some usage examples. For instance, since navigation and view model are both multiplatform, I expect the navigation to work just fine in compose multiplatform, including injecting navigation arguments to view models. But those injected arguments are read from SavedStateHandle, which feels pretty Android-specific. I wonder if that's also multiplatform, will you be able to add that dependency to your ViewModel class constructor and read out flows of arguments (just like we do on Android)?

_runtime
Автор

Hello, I am exactly using the same version of libraries u using but I get errors in this line
singleOf(:DbClient:)
I imported the same package but it still showing error:
"None of the following functions can be called with the arguments supplied"

lmzzxje
Автор

When i using network call using coroutines incetance create issue with ios app.. desktop and Android apps works fine

sureshseeni
Автор

In my case androidContext in android init crashes with exception. I don't understand

origin-pehy
Автор

Can you just use KoinApplication composable in commonCompose instead of initKoin() in separate platforms?

DanniiTran
Автор

Hey i have the total instructions but not able to execute could you instruct me how to follow the steps in a basic manner

danial
Автор

please record video about splash screen in kmp

abobus_f
Автор

I think that the Kotlin language should solve this problem soon, For example with context receivers. When using a DI library, if it does not use a Clean Architecture design pattern, it will be difficult to trace in the code where a particular dependency is injected. The very thing IDE powerless at times. I don't like all these classes that are built with DI. This should be done stably by Kotlin 2.0 in memory without a DI library in my opinion.I may not be right, but only time will tell.

skarloti