I mentioned something in relation to this here Original Developer's Participation but veered of topic slightly, nevertheless this is around design.
Alex said, ‘it’s really just a function of priority vs user signal & time/resources available…In enabling a particular extension, there is some checking to make sure it doesn’t compromise user security or privacy.’
I was curious how the design of how about:preferences#extensions is going to look and work when its finally competing with Firefox and Chrome because I realised after checking all those requests which would take an awful lot of time after all users suggestions are applied which is the plan but how will it look and similarly to the bookmarks issue currently facing Brave, are we going to face a similar issue especially considering extensions are heavier.
It seems that modification/design of the about:preferences#extensions is best done soon so when users extensions are fully implemented it doesn’t look as unorganised as some of the other, obviously it doesn’t look untidy now because there’s only a hand full of extension.
I don’t want to veer too of topic again but could user soon develop applications/extensions primarily for Brave and not orientated around Google’s Chrome? This question can also be juxtaposed with How will you push updates for future extensions?