kmp-networking

Cross-platform HTTP networking in Kotlin Multiplatform uses a shared Ktor HttpClient with platform-specific engines: OkHttp for Android and Darwin for iOS. Configure the client in commonMain with JSON serialization, then inject it into API services for consistent requests across platforms.

Yes. A single Ktor-based HttpClient with platform-specific engines handles both Android and iOS. This eliminates boilerplate, ensures consistent API access and authentication, and reduces duplicate networking code across targets.

Bearer token authentication is implemented via the API service pattern with token refresh and structured error handling. Configure defaultRequest in the HttpClient to include authorization headers, then apply retry logic and error handling consistently across all platform-specific engines.

Use a shared HttpClientFactory in commonMain that exposes platform-specific engine implementations. OkHttp handles Android networking with native performance, while Darwin provides native iOS behavior—both behind a unified client interface for simplified API wrapper code.

No. A shared networking layer with platform-specific engines eliminates duplication. The HttpClientFactory abstracts engine selection, so Android and iOS applications use the same API service wrappers, logging, and request configuration from commonMain.

Error handling is centralized in the API service pattern with structured responses that work across all platform engines. Combine Ktor's built-in error mechanisms with custom handlers in commonMain to ensure consistent error propagation from Android/OkHttp and iOS/Darwin.