Disclaimer, I use an iPad 9th Generation with iPadOS 16.7
Q1) What does your feature entail?
The feature will allow users to lock the extensions settings specifically with a password so that no one can toggle any extensions on/off or disable them without the device's owner's consent.
Q2) What is it for?
The feature is useful for a parent like me who sets up extensions to control their kid's exposure to content they should not be accessing. I know there are "Screen Time" settings in iOS devices but they are only limited to website blocking. For example- My kid wants to use youtube for learning maths from youtubers like Prof. Leonard but then he gets distracted by other entertaining content, loses interest and ends up wasting the entire day on non educational content. That's where I use extensions to block specific youtube channels and categories within youtube but my kid can just turn off extensions to bypass this restriction. Hence, a password lock on extensions would be really helpful in this situation and I believe it will be helpful in many other use cases as well.
Q3) How will it affect existing workflows or user experience?
The ability to password protect extensions' settings from the "3 dot menu on top right ---> Extensions" should have an option to turn it ON or OFF so it doesn't affect anyone's workflow. As for the user experience, I believe it would be a great addition to the list of advanced features Orion already offers on iPadOS. I think it will not ruin the user experience for anyone who doesn't need it.
Q4) What are the exact ways you see a user using your proposed feature?
This is how I think this feature should be implemented:
1) This feature should prompt a window asking for password whenever someone tries to access extensions settings from "3 dot menu on Top Right ---> Extensions", before giving them access to the list of extensions installed with toggle On/Off switches next to them.
2) Users should be able to Enable password for extensions from the main settings where we enable chrome/firefox extenions i.e. "3 dot menu on Top Right ---> Settings ---> Extensions Subsection"
*Also, To Disable password for extension settings from the same path mentioned above, there MUST be a requirement to provide the current password which should have been set up at the time of enabling password protection for extensions.
Q5) If your feature suggestion adds to an existing feature, how would it work into it to extend its usefulness?
I personally do not think my feature suggestion adds onto any other feature. Sure there is browser lock but users should be able to password protect extension settings without having to set up a browser lock.
