http4k-connect VS redwood

http4k-connect is a set of lightweight (zero-reflection) API libraries for connecting to popular third-party cloud services using http4k clients, along with Fake implementations for usage during local testing. It is based around the Connect pattern, which allows you to express client-side adapters in modular and composable way.

Great stack! Just out of interest , any reason you don't use Http4k connect for your AWS needs?

TBH, the official SDK dynamo client library isn't great for either. If you're looking for something lightweight, you could try http4k-connect - the dynamo client API is much nicer, does type-safety by plugging into the http4k lens system, and is zero reflection (using Moshi and generated adapters), which means you can simply cross compile to GraalVM. We're using it for native Kotlin Lambdas using the custom http4k Lambda runtime and it's 🚀🚀🚀. You can also use it backed by the OkHttp client wrapper if you want.

Now what if apple kills UiKit and keeps only SwiftUi, won't happen but lets assume that it does. Compose can use SwiftUi under the hood. Its already there as a prototype .

This is a great open-source implementation of the same concept! https://github.com/cashapp/redwood

There's also the Compose compiler based approach redwood that uses native UI on iOS.

Sharing UI code is definitely feasible though. Look at Redwood for example. It isn't really a general purpose UI library as-is, but someone could (in theory) build a library of cross-platform widgets that work a lot like React Native widgets, and that would enable you to build UI entirely in multiplatform Kotlin.

Jake implementing Compose to render Compose into ComposeUI and XML views https://github.com/cashapp/redwood/tree/e69a54e71222ab1a170a35ddabfed9611c761ac8/redwood-layout-view

Redwood exists, though it takes a bit of a different approach.