Getting started with dagger 2
2 likes1,048 views
The document discusses Dagger 2, a dependency injection framework for Android applications, emphasizing its benefits such as testability and separation of concerns. It details various injection methods, including constructor, field, and method injection, as well as the role of components and modules in providing dependencies. Additionally, it highlights Dagger 2's performance advantages over other frameworks like Guice.
Getting started with dagger 2
- 1. Getting Started with Dagger 2 Fast dependency injection for Android applications
- 2. Why dependency injection? Separation of concerns Testability Every app has some kind of dependency injection
- 3. Uncle Bob “Depend upon Abstractions. Do not depend upon concretions.”
- 4. A brief history of time JSR-330 Guice Dagger
- 6. Dagger 2 Maintained by Java Core Libraries team at Google Faster than Guice and Dagger Easy to use and to debug Mobile first
- 8. Dagger API @Modules + @Provides @Inject @Component
- 10. Requesting Dependencies @Inject annotations required Constructor, Field & Method
- 11. Constructor Injection @Inject on a single constructor Parameters are dependencies They can be stored in private and final fields
- 15. Dependency Graph EpisodeRepository DataModule#provideEpisodeRepository RemoteEpisodeRepository TraktvApi DataModule#provideTraktvApi OmdbApi DataModule#provideOmdbApi Constructor Injection
- 16. Field Injection @Inject on fields for dependencies Field can not be private or final Inject happens after object is fully instantiated Object is usually responsible for injection
- 17. Method Injection
- 20. Components Bridge between modules and injections The injector
- 21. Components
- 22. Components this notation is optional
- 23. Components
- 24. Components
- 25. How about some live coding?
- 27. Questions?