xamarin-macios VS uikit-sys

Xamarin.ios y Xamarin.Mac: Licencia MIT.

Try to build the project for Android and iOS respectively. If you suffered from the iOS build issue Error MT4109: Failed to compile the generated registrar code caused by Xcode 14, you can visit https://github.com/xamarin/xamarin-macios/issues/15954 to find the solution. The issue can be fixed by installing xamarin.ios-16.0.0.72.pkg. To run the app on iOS 16, turn on Settings > Privacy & Security > Developer Mode.

See this for more info.

There is nothing planned. Downgrade immediately https://github.com/xamarin/xamarin-macios/issues/15954

MAUI on iOS and MacCatalyst use: https://github.com/xamarin/xamarin-macios

You can see in old issues like this how uncertain even the core team was about it. It's not really tenable to fly that blind.

I think they're still doing tooling updates for Xamarin for a while. For one, there are platforms that for now aren't (yet) moving to .NET 6 at all, such as watchOS. And second, they seem to have changed their Apple platforms tooling to basically dual-target Mono (for Xamarin) and .NET 6 (for MAUI).

Microsoft decided not to support the Apple Watch in .NET 6 (https://github.com/xamarin/xamarin-macios/issues/8955), which made me uncertain as to its future on the Apple Watch - I was also interested in learning Swift and SwiftUI.

With uikit-sys, the build is very slow as it's all generated from bindgen and includes uikit as well as any of the framework dependencies required for it. I'm yet to figure out how to reduce how much stuff is generated as well as a reasonable way to wrap it in safe rust and ensure there's no memory leaks.

Nice! Welcome to the small group of rust iOS people! I'm the author of uikit-sys which really is just using the rarely used objective-c features of bindgen (plus an unmerged PR to bindgen) to generate bindings to to basically all the iOS objective-c frameworks.