This is honestly just good etiquette, and is also true for the Fediverse and Bluesky. Open source in general, really.
Being able to write a good issue for a repo's tracker is crucial. You need context: what steps did you take to make it happen? Can you recreate it? If there was an error message, either in a GUI or a terminal, what was it? What was your OS / browser setup? Did you have to use something specific to get the app to work on your device, like Homebrew?
It can become kind of a rabbit hole of "What info do I need to bring with me?", but any supportive information is better than nothing.
i suspect a lot of people feel like they should know how it works already or that they’re probably doing something wrong.
if you’re confused about anything ask the question. other people are probably similarly confused and the developer who looks at it every day probably doesn’t know about the confusion.