
input height - mobile device
-
- Implemented
- 6.0.x
-
Grafidea -
July 11, 2023 at 11:36 PM
-
-
-
are more mobile-friendly. the same goes for the buttons.
-
I can’t really see a difference in size compared to iOS. So I don’t see the point here.
-
This is how mobile-friendly inputs and buttons should look like.
-
Urghs. I’m definitely against it. I like the current size and see no reason to change it for no good.
-
I respect this. However, this is not about individual preferences, but about 2023 UI/UX standards.
-
And where are these standards written down? If they’re standards, they have to be.
To me it sounds more like a personal preference.
-
-
My suggestion button and input sizes:
-
There is a lot of information about everything on the internet. That doesn't mean it is correct. So unless you have a proper source for what you’re saying, I don't believe it’s a "standard".
-
Just take a look at major portals like Facebook and Twitter. They usually have a well-executed UI/UX design.
Input:
- It should have a clear text field with an appropriate label.
- It should be large enough for users to comfortably enter text.
- It should display the appropriate keyboard type for the type of data, such as a numeric keyboard for entering numbers.
- It should provide hints about formatting or requirements, if necessary.
- It can have an icon preceding the text field to indicate the type of data to be entered.
Button:
- It should be large enough for users to easily tap with their finger.
- It should have clearly labeled text that communicates its function.
- It should be adequately separated from other buttons or interface elements to avoid accidental taps.
- It can include a subtle animation or visual effect to indicate its active state after being tapped.
-
- Official Post
We’re already enforcing a larger font size on iOS to prevent the implicit browser zoom to kick in. I can imagine increasing the vertical padding of input elements a bit to accommodate for that increase in font size.
Buttons are a bit of a different story, because their accessibility is not entirely based around one dimension (e.g. only their height) but their entire click area. We have already taken some steps in 5.5 and 6.0 to increase the click area of buttons in the header menu to at least 40px in both directions to comply with the WCAG 2.0 AA specification.
-
I like that the inputs are of the right width, but I would increase their height a bit and make the buttons slightly larger.
-
We’re already enforcing a larger font size on iOS to prevent the implicit browser zoom to kick in. I can imagine increasing the vertical padding of input elements a bit to accommodate for that increase in font size.
Buttons are a bit of a different story, because their accessibility is not entirely based around one dimension (e.g. only their height) but their entire click area. We have already taken some steps in 5.5 and 6.0 to increase the click area of buttons in the header menu to at least 40px in both directions to comply with the WCAG 2.0 AA specification.
I hope that version 7.0 will bring a completely new template
IPS in V5 will have a new template, and XenForo in version 2.3 also plans to introduce a new template. I really like Woltlab from a technical perspective, as it is fast and well-optimized, but a more modern appearance would also be welcome.
When proposing WoltLab software to various individuals, I often come across the response that IPS or XenForo looks nicer. As you know, many laypeople who manage forums are more focused on appearance than technical aspects.
-
Alexander Ebert
July 13, 2023 at 3:59 PM Added the Label 6.0.x -
Alexander Ebert
July 13, 2023 at 3:59 PM Added the Label Implemented -
Alexander Ebert
July 17, 2023 at 6:27 PM Moved the thread from forum Ideas & Suggestions to forum Closed Suggestions.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!