repository-remote

A safe Kotlin repository for Retrofit splits interface and implementation into suspend functions returning ApiResult. It wraps every Retrofit network request with safeApiCall to handle errors automatically and ensure clean separation.

The best way to structure a remote API repository in Kotlin is using a strict Interface + Implementation pattern. You define XxxRepository and XxxRepositoryImpl, ensuring all remote calls return ApiResult wrapped with safeApiCall for clean separation.

To bind a remote repository using Hilt, create a RepositoryModule that injects XxxRepositoryImpl as XxxRepository and binds it to Singleton scope. This ensures your interface and implementation are properly provided for dependency injection.

This remote repository pattern is designed exclusively for features interacting with a backend. It handles network calls and error handling without mixing in Room or DAO logic, keeping your local and remote data sources strictly separated.

Wrapping Retrofit responses in ApiResult for remote API calls enforces safe network operations. The safeApiCall wrapper maps Retrofit responses to ApiResult, standardizing error handling and ensuring your repository layer manages failures consistently.