Enjoying breakfast now.
@Ulrich B will kick off today with his presentation about Accelerate Framework.
The delay was mostly due to the fact that the first two approaches did not lead to the expected success.
The solution was not to work with the LLVM compiler for Android, but with the Kotlin compiler (which gives you an .apk).
That is more work but it leads to a better experience
Optimisation happens at install time, so that the code is optimised for the device it is running on.
The result of doing it "the Google way" is that it will run on whatever google decides in the future
The Android Framework
What we've seen demonstrated:
Not sure if Camera support will be in the first version.
InterOps not needed to compile to Android, but it is still needed to talk to the OS
It will be Mobile as a platform (not just android)
The "new framework" for iOS will disappear
There have been lots of changes since May and many more changes will come by Xojo Connect, but still no promises about when it might be released.
@Paul B progress with Android, especially seeing the compiled app downloaded to a connected phone for testing purposes rather than an emulator.
For developing purposes and debugging, everyone expects an emulator, the run "in device" can be done for an optional test phase. No devs must have multiple real devices with such diverse form factors, but they must be able to emulate them. But as said in the blog, that's what happens.