LiteNetLib VS okio

I personally use this LiteNetLib

Been using LiteNetLib for our current project and it is pretty nice

Currently I'm using LiteNetLib (https://github.com/RevenantX/LiteNetLib) and it's working pretty well. There is a little input lag but it's more than acceptable.

Check LiteNetLib. Judging by your requirements simply passing coordinates back and forth between two clients should work. Designate one of the games as host and the other as client, but just pass coordinates would work over LAN. Optimise from there if gameplay isn’t thet smoot by lerping between past and newly received coordinates.

For networking, file IO, and streams in general, there's Korio and for Java; for just networking, there's LiteNetLib for C#; for what looks like data streams in general, there's Okio also for Java; and Tokio for multi-threaded IO in Rust.

I've been a bit "Unity offline", and even more so when it comes to networking solutions, because of my real job :), but LiteNetLib is quite good. There's also a new HLAPI solution called FishNet which seems very interesting.

This might be handy for you :) https://github.com/RevenantX/LiteNetLib

they might be using LiteNetLib as their low level transport.

You definitely want to a low level API (LLAPI) instead, like f.ex. LiteNetLib, ENet, lidgren or similar. I haven't touched anyone of these recently, except the first one a year-ish ago, so I won't say anything about where they stand today.

I am involved in the development of Android application which is a rather "thick" mobile client for a Web service. It heavily communicates with the server but also has a lot of inner logic too. So, I decided to use some features of Google Guava library to simplify development process. Here is a list of features I'm very interested in: immutable collections, base utils, collection extensions, functional programming sugar and idioms (common.collect and common.base), primitives utilities (common.primitives), hashing utilities (common.hash), concurrent utils (futures and AsyncFunction). Things I don't want to use in Android: common.cache (see question below), common.eventbus (we have better Android specific libs for this, such as Otto), common.io (we can use okio for Android now).

Yeah Kotlin's own standard library is a lot smaller than Java's currently so you'll need to use something third-party for this. Okio is a popular option https://square.github.io/okio/ it has a Buffer type which is pretty similar to Java's ByteBuffer

Use okio, it is Multiplatform now. I use this for my own library KStore

For networking, file IO, and streams in general, there's Korio and for Java; for just networking, there's LiteNetLib for C#; for what looks like data streams in general, there's Okio also for Java; and Tokio for multi-threaded IO in Rust.

Okio is nice for input/output streams, and sockets.

Sounds like you want https://square.github.io/okio/

On JVM, there is plenty of existing solution already on for multiplatform uses I'd suggest checking amazing Okio library by Square, that seems to cover most of basic use-cases.

I think the main multiplatform library for I/O currently is okio, https://github.com/square/okio. As for compression, you should probably create an expect class for the compressor and use platform specific calls for actual compression. Take a look at https://kotlinlang.org/docs/mpp-connect-to-apis.html.