Playing with Hilt DI

Hilt is one of the latest update from Jetpack. It brings a new way to implement the dependency injection over top of Dagger. It simplifies the process and the Dagger ritual to do the dependency injection with ease. It is still alpha version and worth to try!

Transcript

1. GDG Jakarta Playing with Hilt DI Sidiq Permana sidiq@nusantarabetastudio.com
2. Dependency Injection is one of inversion control (others : service locator, strategy pattern, factory pattern) technique whereby one object (or static method) supplies the dependencies of another object. A dependency is an object that can be used (a service).
4. Advantages Decoupling Dependency : Avoid hard dependency. Reusability : Reduce boilerplate and reinvent the wheel. Ease to Test : Replace the dependency with mock. Ease to Refactor : Improve code? No worry.
5. Dependency Injection in Nutshell DI Library Component Module Push to inject Scope
6. Manual Dependency Injection
7. Impl Manual Dependency Injection
8. Automated Dependency Injection Using DI Library
9. GDG Jakarta Introducing Hilt
10. Hilt is a dependency injection library for Android that reduces the boilerplate of doing manual dependency injection in your project. Build on top of Dagger library and simplified the ‘Dagger Ritual’ and implement DI with ease!
11. Why Hilt? Build on Top Of Dagger. They can coexist. Simplify the Dagger Process. Set a standard of components and scopes to ease setup, readability, and code sharing between apps. Provide an easy way to provision different bindings to various build types, such as testing, debug, or release.
12. GDG Jakarta Jump to the code
13. Setup : Add Classpath in gradle file Project Level
14. Setup 2 : Add the dependency and apply the plugin
15. Setup 3 : Hilt uses Java8
16. 4. Define Module
17. Generated Components for Android Classes
18. Component Hierarchy
19. 5. Define The Bindings
20. Bindings It is a way to provide instances of the necessary dependencies from the corresponding component to perform the Field Injection. A binding contains the information necessary to provide instances of a type as a dependency. One way to provide binding information to Hilt is constructor injection with @Inject annotation.
21. Inject Interface with @Binds
22. 6. Wiring up the bindings into the module
23. Component Scope
24. Component Default Bindings
25. 7. Add @AndroidEntryPoint to Activity
26. @AndroidEntryPoint Hilt can provide dependencies to other Android classes that have the @AndroidEntryPoint annotation. Current Android Classes supported : • Application (by using @HiltAndroidApp) • Activity (Only derivation of ComponentActivity such as AppCompatActivity) • Fragment (Not working in Retained Fragment and only androidx.Fragment) • View • Service • BroadcastReceiver
27. Obtain dependency with @Inject Fields injected by Hilt cannot be private. Attempting to inject a private field with Hilt results in a compilation error.
28. 8. Add @HiltAndroidApp
29. GDG Jakarta Generated Code
31. GDG Jakarta Hilt x Android Jetpack
32. Current Hilt x Jetpack Supports Supports ViewModel Supports WorkManager
33. Inject ViewModel Objects with Hilt
35. GDG Jakarta Dependency Graph
36. Application Component Dependency Graph
37. Hierarchy
38. ActivityComponent Dependency Graph
39. Conclusion • Hilt simplify the DI process compares to Dagger. It is even easier to you if you have any experience working with Dagger previously • It provides predefined components, scopes, bindings and qualifiers through annotations for Android Classes that helped us much! • Can be coexist with Dagger especially in DFM • It is still new and will be coming more features. So Give it try!
40. Reference https://developer.android.com/training/dependency-injection/hilt-android https://codelabs.developers.google.com/codelabs/android-hilt/ https://arunkumar9t2.github.io/scabbard/
41. GDG Jakarta Source Code : bit.ly/di-tamvan
42. GDG Jakarta Thanks