Can't easily check script version in iOS version

[ACTCD]

Since the iOS version does not have an editor view, the only way to view detailed information such as the script version is to open the corresponding script file in the system's file application.

This is very inconvenient, and many times just want to check whether the update is successful, or the user needs to check whether the corresponding version is running, there is no convenient way.

Maybe consider adding some information to the popup view, or bring the Extension Page to the iOS version. I know that this question may involve a larger aspect, this is more just a record, from the aspect of a daily experience to show the current user interface deficiencies, looking forward to more opinions.

[quoid]

Just a thought on this, I think repurposing the Install View to show detailed info about the script could be a good place for this. Right now it doesn't show @version but that could be added.

I also think this could help with this issue: https://github.com/quoid/userscripts/issues/225

This still just an idea, but perhaps when the user is viewing the popup, on mobile, and they click into a script, rather than toggling the script, it takes them to a Single Userscript View and they can see detailed info on the script have available options for that script such as Toggle Off, Toggle off for this website, Check for updates, Update script (if available) etc...

It's a lot of work, but could be a big benefit to the UX of mobile.

[ACTCD]

This still just an idea, but perhaps when the user is viewing the popup, on mobile, and they click into a script, rather than toggling the script, it takes them to a Single Userscript View and they can see detailed info on the script have available options for that script such as Toggle Off, Toggle off for this website, Check for updates, Update script (if available) etc...

I totally agree with the proposal to add a script details view, it could even exist in a desktop extension, but I think the action of clicking to toggling the scripts should be kept, which is a very common operation, and instead, add a button (e.g. > or ⓘ or ⚙) on the right side of each script to go to the details/settings view of an individual script, in this view you should also add a link to directly open the edit view for this script in the extension page (for review code or editing).

Although most users will not review the code during installation and update, we should encourage users to review the code to check if it adds malicious behavior, so we should provide a button to the source code view in the installation and update interface .

This involves a lot of new work, but it does bring great convenience to users.

[ACTCD]

I show a simple demo, it might work like the image below. On the basis of keeping the existing click toggle script, add a button to the right to enter the single script view. Do you think this is good?

[quoid]

Thank you for the mockup, that is certainly a viable option and could simplify the experience across both platforms (desktop and mobile). I do wonder if it could be cumbersome on mobile, but if it is, that would be exposed during testing.

The above mockup should be one of the first goals for the UI/UX improvements.

[ACTCD]

I was thinking maybe we could enhance the existing script install view to make it a common single script view. It will display an install button when installing, a delete button when viewing the details of an existing script, and an update button when an update is detected, which may reduce some workload, only need to maintain a unified single script view, while providing users with a consistent experience.

[quoid]

@ACTCD

Yes, that sounds like the goal. It was what I was mentioning here, but I guess it wasn't very clear.