Initial support for compose multiplatform

[theimpulson]

What is it?

• Bugfix (user facing)
• Feature (user facing) ⚠️ Your PR must target the refactor branch
• Codebase improvement (dev facing)
• Meta improvement to the project (dev facing)

Description of the changes in your PR

• Adds a new module net.newpipe.app to host new compose code
• Introduces support for compose but with multi-platform support:
  • Supported targets include: Android, iOS and Desktop (Windows, MacOS, and Linux)
  • Android changes are packed into a library using the new library plugin and thus can be accessed by the existing module containing legacy code

APK testing

The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR. You can find more info and a video demonstration on this wiki page.

Due diligence

• I read the contribution guidelines.
• The proposed changes follow the AI policy.
• I tested the changes using an emulator or a physical device.

[theimpulson]

Most libraries are preferred from JetBrain's fork instead of Android for proper multi-platform support for the new compose and Kotlin code we will be introducing going forward.

[absurdlylongusername]

Shouldn't this target the refactor branch?

[theimpulson]

Shouldn't this target the refactor branch?

refactor branch already has a different compose setup specific to android and is using navigation2 while navigation3 is now stable. I don't want to spend time on writing migration for it and thus decided to use dev as a base for a clean state while picking code which can be reused.

[Stypox]

Cool, thanks! This ideally would go into refactor though. Can't you convert the refactor setup? Or is this supposed to be just a PoC to see if it would work and the actual conversion of the current refactor branch setup would be done once we see it's viable?