Dependency Injection (DI) is a design pattern used to implement IoC (Inversion of Control), allowing for better decoupling of code and easier testing. Many production Android apps leverage DI frameworks like Dagger, Hilt, or Koin to manage dependencies effectively. Below are a few examples of how DI is used in popular Android applications.
// Example using Hilt in an Android app
@HiltAndroidApp
class MyApplication : Application() {}
@Module
@InstallIn(ActivityComponent::class)
object NetworkModule {
@Provides
fun provideRetrofit(): Retrofit {
return Retrofit.Builder()
.baseUrl("https://api.example.com")
.addConverterFactory(GsonConverterFactory.create())
.build()
}
}
@ActivityScoped
class MyRepository @Inject constructor(private val retrofit: Retrofit) {
fun fetchData() {
// Implementation for fetching data
}
}
@AndroidEntryPoint
class MainActivity : AppCompatActivity() {
@Inject lateinit var repository: MyRepository
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
repository.fetchData()
}
}
How do I avoid rehashing overhead with std::set in multithreaded code?
How do I find elements with custom comparators with std::set for embedded targets?
How do I erase elements while iterating with std::set for embedded targets?
How do I provide stable iteration order with std::unordered_map for large datasets?
How do I reserve capacity ahead of time with std::unordered_map for large datasets?
How do I erase elements while iterating with std::unordered_map in multithreaded code?
How do I provide stable iteration order with std::map for embedded targets?
How do I provide stable iteration order with std::map in multithreaded code?
How do I avoid rehashing overhead with std::map in performance-sensitive code?
How do I merge two containers efficiently with std::map for embedded targets?