I’m working on a material design menu for a game I am working on the side. It’s going to be seperate from the main game, but the data will connect together. I wanted this part to be super mobile friendly, decided to go with the new material design look that android apps are doing. Still a very early WIP.
This was all made with ROBLOX guis, no extra images or tools used.
I’m not a fan of the placement of the button. Firstly it’s on an element that isn’t the element that it modifies, which is already something you should watch out for. But then it becomes a close button which should always, no exceptions, be located on the element it acts on. Close buttons are pretty important so making sure the user knows exactly what they’re closing should be a priority.
I recommend making it into a little tab that’s attached to the top right of the menu and slides out along with it.
[quote] I’m not a fan of the placement of the button. Firstly it’s on an element that isn’t the element that it modifies, which is already something you should watch out for. But then it becomes a close button which should always, no exceptions, be located on the element it acts on. Close buttons are pretty important so making sure the user knows exactly what they’re closing should be a priority.
I recommend making it into a little tab that’s attached to the top right of the menu and slides out along with it. [/quote]
I’m sorry, I have to disagree with you. A button does not have to be on the same element it modifies. And a close button does not need to be on the element it modifies. I’m not sure where you got this info.
The entire method I’m using is material design, and it seems to be working for everyone else.
[quote] I’m not a fan of the placement of the button. Firstly it’s on an element that isn’t the element that it modifies, which is already something you should watch out for. But then it becomes a close button which should always, no exceptions, be located on the element it acts on. Close buttons are pretty important so making sure the user knows exactly what they’re closing should be a priority.
I recommend making it into a little tab that’s attached to the top right of the menu and slides out along with it. [/quote]
I was actually thinking about writing an API where you can simply “script” a gui very easily,
which would then work on all platforms, maybe looking a bit different on all.
(You would be able to test it in studio, like that “Current Device” emulator thingy)