Compose Manager : Download plugins are empty. How to use them?

[vippium]

How to use the download plugins in RV Manager Compose. There is a option for that but shows No plugins installed.

[optimatrix0]

I also have this same doubt

[optimatrix0]

probably the plugins have not been released yet

[Ushie]

ReVanced Manager Compose is in development and is not ready to be used, plugins have not yet been developed

[optimatrix0]

In my mind, I thought that the webview plugin would be the standard incorporated into the Manager, and people would have the opportunity to download others, but without any plugins to install, it becomes complicated for us to learn how to use it. Of course, I am thinking about new users, not those who already use it. I agree with some developers who said that a webview plugin for users to find and click the download button is ideal to be incorporated. So I believe that creating this type of plugin will solve both problems. The sincere opinion of a user who really likes the project is that they want to see the new version of the Manager soon.

[oSumAtrIX]

ReVanced will offer first party downloader(s) in partnership with sites. APKMirror for example. We will not offer downloaders that abuse a service though. For example for APKMirror we will display a webview or other ways for them to generate revenue instead of abusing their API. The API for downloaders is published eventually so you can write your own downloaders for any site, irrespectively of us.

[vippium]

But atleast you can make compose to support or patch any version of apps. It only patches the recommended version. But if user want to patch higher or lower version (for deprecated features obviously), he can't. After downloading the apk from downloader, it throws error of recommended version. If you prefer, then, creating a toggle for this which will allow user whether he wants to always patch with recommended version or to patch with other versions.

I Hope you'll understand what I want to say.

[oSumAtrIX]

The downloader has nothing to do with deciding which version to patch, that's specified by the patches and for that a toggle already exists

[vippium]

The downloader has nothing to do with deciding which version to patch, that's specified by the patches and for that a toggle already exists

You are still not understanding what I'm saying.
Check this ss:

This shows that downloader completely depends on patches recommended version.
If required, i'll give you the recording of what I want to say,

[oSumAtrIX]

That is unrelated as the downloader requests version X but version Y is returned by the site.

[optimatrix0]

Are you expecting users to manually import a previously downloaded APK if it's not supported? This contradicts the Manager's purpose of simplifying app correction for Android users.

My final question: What's the primary reason for migrating from Flutter to Jetpack in the Manager? Clarifying this would benefit many users, not just me, as the repository explanation remains superficial.

[oSumAtrIX]

Are you expecting users to manually import a previously downloaded APK if it's not supported? This contradicts the Manager's purpose of simplifying app correction for Android users.

Support for a version is determined by the patches. Apps can be selected manually or downloaded via downloaders, as a simplification.

My final question

Flutter is clunky and Jetpack compose easier to use

[optimatrix0]

I appreciate your previous responses. My doubts about migrating from Flutter to Jetpack have been clarified.

I'd like to highlight a concern regarding Manager plugins. Allowing external downloads and updates within Manager is crucial. This ensures Manager fulfills its primary goal: simplifying Android app downloads and corrections.

Looking forward to the project's completion! You're doing great work!

Thanks!

[vippium]

Ya..If users still have to download old version to use them, then what's the objective of using downloader? Instead of using APK Mirror API (obviously for revenue purpose), just add another plugin with uptodown api (or any other) to support old version download also.

[oSumAtrIX]

Downloaders aren't restricted to downloading one version.

[Axelen123]

The reasons for requiring the user to select the recommended version are explained in this issue. An APKMirror plugin is available here. The README explains how to use it.