Hi, thanks for the elaborate comment.
I will try to address some of your points :)

The adapter is written in full Kotlin, the examples are in Java and Kotlin.
(see the Git repo and the example app)

I’m familiar with the arch paging library, not a big fan, too complex for this adapter use cases. I did not want to introduce a third party library just for this case. If you have a complicated scenario and you need a finer control this adapter is not the solution.

Regarding the API, I agree.
But, not everyone is developing with modern architectures.
When writing a library you should try to get as much reach as you can, so if a developer is used to writing in the old ways he can still do that with this adapter.
Inside the adapter, every API call goes through the same “setItems” call exactly as you wrote.

Cheers