I could see using that library later for web concerns but that is not the goal

The issue with pulling in a built framework, from my perspective, is you can’t really debug anything at that point, and from a team dynamics perspective, the “iOS devs” never really get on board with Kotlin. We’ve done configs where it works that way by default, but you can flip a switch and build Kotlin locally. Not sure how you’d configure that outside of cocoapods, but you could I’m sure.

I had a long thought piece that I was typing, but I’ll skip it. I think to get started it would be better to describe your source organization and desired build process, and see if anybody’s used that. You might luck out and find a detailed, “Here’s how we did this with monorepo and Carthage…“, but I don’t think theres’s a ton of production build config content out there yet, although there’s some. You’ll almost certainly have more luck finding somebody who’s done Carthage (or whatever) in the slack.

Yes, I need to narrow down the use case like you are saying... envision how the org and build process is going to play out. Thanks!

I don’t know your particular situation, but I’d try to find somebody on the iOS side who’s at least curious. Get some collaboration.