oSumAtrIX

If ReVanced implements split APK patching it will very likely not merge APKs but instead simply support the split architecture.

Pre releases should not be downloaded at all except by involved developers. It is not something the end user is suppose to see but by nature of GitHub and auditing...

GitHub actions isnt intended to use as a releases source. Actions are pruned after a certain time, cant be tagged or have a release note, etc.

@Axelen123 > I don't think webviews need to be part of this API. I believe it would be more readable and expressive if you "installed" a strategy via the DSL....

> Yes, that is fine, it either continues the patching process undisrupted or requests user interaction, temporarily suspending the patch process until the result is obtained I don't understand. The...

> until it finds a suitable download This implies making calls to `get`. So I assume you are talking about `get` being called after the user selects a non installed...

> calling get in the patch process I think its better to check if the downloader can get the download after selecting a non installed app. Once get returns non...

The strategy is just an abstraction of the get() api. As you can see the api strategy has a readable and to an api domain specific find function. The webview...

> Manager shouldn't care about the implementation of your plugin and we shouldn't assume specifics about implementations either That is correct. Downloader only sees: `downloader.get("pkg", "version").download()`. As you can see,...

Can you explain why we give plugins low-level APIs, such as when launching an activity? To me, it sounds like they will never need that. A small and concise API...