I have an Android-first mobile application that now needs clean, well-tested Kotlin bindings for a remote API. The exact protocol (REST, GraphQL, or even SOAP) is still being finalised, so I’m looking for someone comfortable working across these flavours and able to pivot quickly once the spec is confirmed. Your job is to translate the API specification into idiomatic Kotlin code that my app can call without caring about the underlying transport details. That includes creating data models, request/response mappers, authentication hooks, and robust error handling built around coroutines and Flow. Retrofit, OkHttp, Ktor, or a solution you prefer is fine as long as the final interface is simple to consume from the mobile layer. Deliverables • Typed Kotlin client library with clear function signatures • All necessary data classes and serialization adapters (Moshi/Kotlinx) • Interceptors for auth, logging, and retry logic • Unit tests covering happy paths and edge cases • A concise README with sample usage Acceptance criteria: drop-in integration within my existing Android module, all tests passing on CI, and clear documentation that lets another developer extend the bindings later. If you enjoy crafting clean API layers for mobile apps and can start soon, I’d love to hear how you’d approach this.