Interest in Native iOS Version #1058
Danielku15
started this conversation in
Polls
Replies: 2 comments 1 reply
-
Pinging some potential stakeholders. @Ltty @gburlet @zhouhao27 @kiketen |
Beta Was this translation helpful? Give feedback.
0 replies
-
Currently I'm trying to use Javascript to implement the score rendering in iOS built-in browser. But I have problem to pass the data (for example, tab file) from iOS to browser. I notice there are some code in
But it needs to drag the file to browser. My intention is to load raw data in native side and pass it to Javascript. Any idea how to do it? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey alphaTabbers!
It turns out that supporting a version of alphaTab in native iOS apps becomes and more of a challenge. This Poll shall give me a better insight if there is even interest in such a version before investing hours/days/months of work to get something working which might result in problems. Here some words on the journey:
Kotlin Native
Kotlin claims to be a good foundation to develop cross platform apps so we thought it would be a good choice for targeting Android and iOS native versions. So the journey on Kotlin JVM began and already it turned out much of a pain Kotlin can be. Its super strict mentality on null and thread safety delayed a lot the progress building an Android version. The performance of the tooling is comparably very poor (compiling the same codebase takes even with caching usually a lot longer than compiling JS or .net). Nevertheless we managed to build an Android version which seems to be working in its basics.
So I started diving into Kotlin Native afterwards and we instantly got stuck because the GC of Kotlin Native had many restrictions (e.g. only thread local statics). Only lately those restrictions were lifted allowing me to progress. All in all the Kotlin tooling seems often on a alpha or beta stage only which implies a huge risk of bugs. Every time I advance one step I run into more bugs in Kotlin and Android Studio making it a huge pain to develop those versions. Some key problems currently are:
.net 7 AOT Compilation on the rise
Lately .net 7 was released and with it the amazing .net Native AoT. Being a .net developer since long time, I was eager to give it a try. In only 1 weekend (~5-6hrs of work overall) I managed to compile a native Win-x64 version of alphaTab and run it in a C++ project as Shared Library (.dll). It is lacking still the features to generate an API Layer for Libraries which can be used in apps.
.net 7 AoT being used across the whole .net ecosystem (Xamarin/MAUI, Blazor/WASM, normal app native compilation) should give a trustworthy base for also making iOS Libraries.
3 votes ·
Beta Was this translation helpful? Give feedback.
All reactions