AndroidX is a new way of organizing support libraries. To make it possible, Kodular Creator should have AndroidX library.However, Google announced that AndroidX library is now open source and is available on AOSP.
You can compile the library if you will create extension in your own environment.
Thanks @golumaths100, I will think about it
You can use the Extension Template Respository which uses AndroidX libs.
Extensions built with it (and imported AndroidX libs) won’t work with Kodular that is still using the Support Library.
My extensions use AndroidX and work perfectly fine with Kodular.
That shouldn’t be possible. Which extensions? So they work with Kodular & AI2?
If so, then there shouldn’t be any problems with the current version of the ExoPlayer (which requires AndroidX).
See e.g. here:
But maybe you can make an extension for the ExoPlayer (with AndroidX).
That would be great, but I have little hope.
See also here:
They work with Kodular, so yes they work with AI2 as well.
With the latest update, Kodular brought support for newer APIs… Which means there (is) support for AndroidX.
Who does that say from the Kodular team?
Where can I read this?
my extension ZxingView version 2 -not released yet- uses androidX support library and works in AI2 and Kodular.
Maybe someone from the Kodular team can shed some light on this.
No one needs to confirm anything. If you paid attention to App Inventors GitHub, you’d see that AndroidX was added.
The question is it won’t compile with appinventor-sources. Will it work with extension-template?
Everyone knows that AI2 has been updated to the AndroidX libs since the
nb184 release, but Kodular has not yet. So what are you trying to explain?
See also here:
I had a chat with Diego (maybe in last month, iirc) where he mentioned that they haven’t migrated to AndroidX yet.
Although, as you might be aware that this will break all the extensions that rely on support library, I don’t see the possibility of Kodular migrating to AndroidX anytime soon (unless they find a way to Jetify the extensions and the libraries they use).
Like some users mentioned, it’s possible to use the AndroidX libraries in Kodular as well, but that will only result in increase in extension’s size as you’ll have to pack the desired library along with the extension like you normally do with any other library.
@Shreyash Thank you for the detailed explanations!
In summary / conclusion:
All extensions using AndroidX or support libraries should be compiled / published with a version for AI2 and a version for Kodular in order to keep the respective extensions as small as possible
(as long as Kodular is still using the support library).
But this is your opinion. Many developers may choose to do the opposite (such as me) to provide benefit to the user.
And what are these benefits?
That the extension is bigger should hardly be an advantage.
Well for example, you’re having issues installing APKs with your extension on versions of Android below Q or above Pie… But my extension includes AndroidX to fix that issue.
It’s worth having something that works in your app.
I may have spoken too soon
Why should that fix the issue?
What does this have to do with AndroidX (and depending on the Android version)?