multi-platform library project - separate uis?

[mandrachek]

I've got a kmp library project where we're using room, and want to add support for room-paging. This should be feasible (although maybe buggy) with the latest room alpha. This uses room-paging, which in turn has a dependency on the androidx paging-common. The library doesn't provide any ui, it handles the network and data storage and access layers. The consumers of this library project are native Android and iOS apps, that are each responsible for their own UI.

On the Android, it looks very straightforward (same good old PagingSource) - but things are a bit murkier for the native iOS app. It is feasible for the iOS devs to use the PagingSource directly? Would they make use ofpaging-runtime-uikit in some way?

[mandrachek]

It looks like paging-runtime-uikit can use the androidx paging-common - it's just a bit out of date - 🤞 there's no breaking api changes and I can just drop it into my project.

[mandrachek]

So, unfortunately PagingCollectionViewController has dependencies on androidx.paging.AsyncPagingDataDiffer, androidx.recyclerview.widget.DiffUtil, and androidx.recyclerview.widget.ListUpdateCallback which are not present in the current paging-common (3.3.4 - or 3.3.2).