Skip to content

feat: Improve trust plugin dialog design #2420

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: compose-dev
Choose a base branch
from

Conversation

Ushie
Copy link
Member

@Ushie Ushie commented Feb 12, 2025

Closes #2061

image
image

@Ushie Ushie added the ReVanced Manager Compose Regarding the Compose rewrite of ReVanced Manager label Feb 12, 2025
@Ushie Ushie marked this pull request as draft February 12, 2025 12:47

This comment was marked as off-topic.

@validcube

This comment was marked as off-topic.

@Ushie Ushie marked this pull request as ready for review March 5, 2025 15:43
@validcube validcube linked an issue Mar 8, 2025 that may be closed by this pull request
3 tasks
@Ushie Ushie requested a review from Axelen123 May 4, 2025 22:41
@oSumAtrIX
Copy link
Member

Offtopic, but why does it say "ReVanced Manager: ..."?

@oSumAtrIX
Copy link
Member

I think the importance of this screen and dialog is enabling and disabling plugins. Trusting them is a secondary task to achieve that main objective. Strings can be renamed to say "Enable" or "Disable" plugin. And the dialog can mention that enabling the plugin can run arbitrary code and need to be trusted as a "side notice"

@@ -137,7 +137,10 @@
<string name="downloader_plugin_state_untrusted">Untrusted</string>
<string name="downloader_plugin_trust_dialog_title">Trust plugin?</string>
<string name="downloader_plugin_revoke_trust_dialog_title">Revoke trust?</string>
<string name="downloader_plugin_trust_dialog_body">Package name: %1$s\nSignature (SHA-256): %2$s</string>
<string name="downloader_plugin_trust_dialog_body">By continuing you\'ve agreed to running external plugins.\n\nDo not allow any suspicious plugin(s) to be installed as they can run arbitrary code.</string>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like youre signing some legal document. Probably different wording would be better here.

@Ushie
Copy link
Member Author

Ushie commented May 5, 2025

Offtopic, but why does it say "ReVanced Manager: ..."?

Placeholder representation of the app name

@oSumAtrIX
Copy link
Member

I am not sure what you mean by placeholder. What would be written there if others develop plugins?

@Ushie
Copy link
Member Author

Ushie commented May 5, 2025

The app name of the plugin — for example, the APKMirror plugin would be named ReVanced Manager: APKMirror. This accurately represents what the app is and its purpose. If it were just APKMirror, you wouldn't know it is for ReVanced Manager in the app list, and that it isn't actually by APKMirror.

@oSumAtrIX
Copy link
Member

It should probably say "ReVanced: APKMirror downloader" or "Ushie: Some other downloader"

@Ushie
Copy link
Member Author

Ushie commented May 5, 2025

Would Ushie make sense here? It serves no purpose knowing who the developer is, knowing what app it's for is what makes more sense

@oSumAtrIX oSumAtrIX force-pushed the compose-dev branch 3 times, most recently from 7338157 to 70a6950 Compare May 22, 2025 12:16
@brosssh brosssh force-pushed the compose/feat/improve-trust-plugin-dialog branch from ba1271b to 47129cd Compare May 30, 2025 10:10
@brosssh brosssh requested a review from Axelen123 May 30, 2025 10:12
@brosssh brosssh requested a review from oSumAtrIX May 31, 2025 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ReVanced Manager Compose Regarding the Compose rewrite of ReVanced Manager
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: Improve trust plugin dialog design
4 participants