[okamiueru]

> However I don't think most people care.

I think everyone cares, whether they know it or not. Which sounds like an oxymoron. But my point is that inconsistent UX might not be glaringly noticeable, but it can still give a feeling of messiness and add to cognitive load.

"Native widgets" is just a way to achieve "consistent widgets". A good tradeoff IMO is to at handle as many things with native UX (e.g. window decorations, menus, etc.), as possible without compromising on function.

To avoid the latter, custom GUI is arguably necessary, as is the case with Blender, while OBS arguably doesn't need its own handling of the menu / window decoration.

These things matter very much to some people, as consistency affects how well certain accessibility tooling can understand the contents of applications. UI customization also matters for similar reasons. Certain things like scaling or theming, might rely on native GUI libraries.

To summarize, if the discussion is what is "best", and you don't have a functional reason to justify custom UX, and you disregard development cost, then the best solution is a consistent UX, i.e. native widgets.