okio VS imgui-rs

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.

there is a good bindings for imgui

There are rust bindings for Dear Imgui. It's a great immediate mode gui that has been used in the gaming industry for tooling. It supports floating windows and such. And there is a lot of customisability to be had. The benefit of the immediate mode gui is that it is constructed and rendered separately from the rest of the logic. Allowing you to build out whatever the gui is for, separately. Then, the gui can be removed from the final build if that is what you want.

Looks like the culprit is imgui-winit-support: https://github.com/imgui-rs/imgui-rs/pull/716

I am trying to use the imgui crate (along with imgui-winit-support and imgui-wgpu) with wgpu. I have followed the imgui-wgpu example and have gotten everything to work on the native version of the project.

Currently, I have narrowed potential libraries to: 1. Flutter 2. FLTK 3. Relm (GTK) 4. iced 5. Slint 6. Imgui, Imgui-rs 7. and gtk-rs

Imgui, Imgui-rs

To move on to GUI dev, there's the Qt Framework, Eto.forms for C#; Rust has the ImGui wrapper for the C++ Dear ImGui library.

Have you looked into the imgui bindings for rust? imgui-rs

All the examples in the imgui repository use glium