Oh, no no, that’s fine. You don’t have to update your code; that’s just a suggestion from myself. People like myself tend to encourage proper practice when replying to DevForum requests and this is one of them.
I don’t encourage using mouse events for mobile, but I’m just saying. In this case, as mobile input is also registered as a click for GuiObjects, it’s fine. Just be wary down the line when working with mobile. There are cases where you don’t have a choice between using mouse or mobile events or it might cause you problems that you could easily avoid.
You can also consider it for the sake of code organisation, neatness and knowing what you’re working with. I tend to separate my input handlers by device or input type so I know explicitly what I’m working with. For example, if I just have a click function, then I get lost in trying to find where I handle mobile input. If I explicitly have segments for mobile, then I can view that piece and say “oh, that’s where my mobile input controls are, I can change the behaviour for mobile now”.
As for the category guidelines, just be more mindful of them in the future. You should always try and see if you’re able to resolve your problems first by searching for similar problems on the DevForum or via the API reference on the Developer Hub. You can also review your own code and debug it with the various tools available - even just printing is good enough for Roblox.
If you’ve tried things out and you can’t resolve the problem, posting here would be fine.