No it’s not wrong. Just depends on your audience. If you’re building for devs then they may not care but others would get confused.
Developers have a bias toward their own creations (designers too) but people don’t use products how you want them to.
Discussion
> people don’t use products how you want them to.
That was my point. All your assumptions are wrong, even if you think you know your audience.
If anything you can only place these labels after observing how many real users use the software in the real world.
What do you think we do that causes us to hide things from people ….
My definition would be:
anything goes in there that would lead to the dev feeling bad about a thing if a noob using the software fucked themselves over with a feature that was not tucked behind a “don’t go here unless you know your shit” wall, also known as the advanced menu. Also has become, settings not needed by most people. 🤷♂️
Just depends on the audience and function. If this is a critical feature then it doesn’t have to be hidden or can be abstracted away to just work.
Hard to talk about this without a specific detail. But easy to generalize.
Indeed. Just my general definition of what I’d expect to put/find behind the advanced category.
That's exactly what user research is for. You talk with users and you test prototypes. That's how you know what to hide or abstract