My thoughts on naming in general.
The plugin’s name should help to indicate what the plugin’s main feature or benefit is.
… and these names.
‘[SU]CH’ doesn’t tell me anything about the plugin, even though it might be an acronym that means something ( I don’t know what.)
“Style”, “Styles” and “Styling” has specific meaning within the SketchUp interface.
Naming an extension Styler to me is misleading and confusing. It suggests a more generic control over styles (which it does not appear to be, rather a fixed set of preset styles used for export.)
This plugin is really in the export or rendering support realm.
Could you come up with a better name that would indicate “export” “rendering” and/or “compositing” ?
Absolutely NOT. The userbase does not need to contend with a bunch of unique and special GUIs !
The dialog interfaces should reflect the GUI of the Operating System. This is what users know and expect.
As an aside, … the shade of red and blue you chose is revolting. These are not colors associated with SketchUp.
This is fine. However try to regulate your price(s) against what other extensions are charging and for what they do to enhance the user workflow.
Also keep in mind how the extension’s cost compares with the SketchUp license fee and maintenance subscription.
Ie, you’ve set this cost at 12.5% of SketchUp’s yearly maintenance subscription, …
and 2.6% of the SketchUp base license fee.
Perhaps this is worth it to someone who does a lot of rendering outside of SketchUp, … (I don’t know as I’m not a “renderer” myself.) Only time will tell.