Description

Considering using Avalonia for my iOS development. Technically, I like what I see and I can see a way through to my completed app. However I'm now wondering if it's feasible to get such an app approved by Apple and in the App Store itself...

First up is the question of using a dylib. I've been looking to do some advanced AVFoundation stuff and the path I'm looking at is to create an Objective-C dylib that consumes AVFoundation and then exposes a PInvoke-friendly API to my dotnet/Avalonia app. Early technical feasibility prototype looks good, but as I researched I ran into "is it allowed to use dylibs in iOS ?". The answer on the thread from the Apple employee is; "You need to build a framework from the source code, starting from the Framework template in Xcode. Technote 2435 has the info you need." Ugh.

Second, I need to consume a 3rd party iOS Framework that exposes some private APIs for some specialty hardware. So far I haven't found any references online to consuming an iOS Framework from DotNet, only PInvoke to Objective-C dylibs per above. Investigations into "can I consume an iOS Framework from a dylib" aren't bearing any fruit either...

Lastly, there's a detailed article on the hoops necessary to make an app bundle for MacOS, but I don't see equivalent documentation for iOS. Similar steps will be needed I assume? Has anyone broken this ground yet to get a signed package that can be uploaded to Apple for App Store submission and review?

Reproduction Steps

Dream of a day when Swift and Objective-C die a well deserved death and dotnet/c# take their rightful throne on the realm of app development.

Expected behavior

Apple submits to the inevitable destiny of C#'s ascendance and stops designing puke-worthy languages because "Think Different".

Actual behavior

"Think Different" means "do it the Apple way, or Take The Highway".

Regression?

Closed platforms that have to deal with arbitrary exclusions like "dylibs aren't accepted, just because we say so" is definitely a step backwards.

Known Workarounds

Convince the rest of the world to stop buying closed ecosystem based products.

Work in progress.

Configuration

No response

Other information

No response