New standard on font height... | developer.brewmp.com New standard on font height... | developer.brewmp.com

Developer

New standard on font height...

Hello everyone,

I have a few doubts on the new text height standard. The standard requires for a minimum height of 3 mm for all texts and menu items throughout the app.

I'm part of the QA at a gaming company. For our games, we've been using graphical fonts instead of system fonts all this while. Some games even have animations with texts and alphabets. This is necessary to give our games a good look. The problem is that all our texts currently measure up to 2 mm thereabouts in height. Yet they are perfectly visible and legible.

Doubt 1: If the text in our game satisfies the motivation (of clarity and visibility), do we still need to increase our fonts to look 3 mm on each phone we support?

Doubt 2: We checked against the fonts seen on the phone's native OS. The texts and menu items look just about 2 mm. Can we refer to the phone's OS as a standard for text visibility?

Doubt 3: How is the 3 mm standard tested at NSTL? Do the testers actually put a measuring scale against the phone screen? Just curious to know if we've understood the term "3 mm" correctly...

Thank you in advance! :)

This standard would be changed to 2 mm from 3mm in near future. Rather NSTL is already using 2 mm to verify.
Developers would be sent a notification for this soon.
Doubt 1: If the text in our game satisfies the motivation (of clarity and visibility), do we still need to increase our fonts to look 3 mm on each phone we support?
[C1:]
Yes you need to keep it to a minimum of 3mm or 2mm(when notified).
That would be a standard now from QC.
clarity and visibility would be considered above that value and not below.
Doubt 2: We checked against the fonts seen on the phone's native OS. The texts and menu items look just about 2 mm. Can we refer to the phone's OS as a standard for text visibility?
[C2:]
Size of Native Device screen Fonts wont matter.
But Yes, if BREW's all default fonts; measure below that value, it would be Considerable.
Doubt 3: How is the 3 mm standard tested at NSTL? Do the testers actually put a measuring scale against the phone screen? Just curious to know if we've understood the term "3 mm" correctly...
[C3:]
Yes they put measuring scales and/or any other methods; but make sure that it greater than or equal to the specified value in mm.
thanks,
Shivendra

This standard would be changed to 2 mm from 3mm in near future. Rather NSTL is already using 2 mm to verify.
Developers would be sent a notification for this soon.
Doubt 1: If the text in our game satisfies the motivation (of clarity and visibility), do we still need to increase our fonts to look 3 mm on each phone we support?
[C1:]
Yes you need to keep it to a minimum of 3mm or 2mm(when notified).
That would be a standard now from QC.
clarity and visibility would be considered above that value and not below.
Doubt 2: We checked against the fonts seen on the phone's native OS. The texts and menu items look just about 2 mm. Can we refer to the phone's OS as a standard for text visibility?
[C2:]
Size of Native Device screen Fonts wont matter.
But Yes, if BREW's all default fonts; measure below that value, it would be Considerable.
Doubt 3: How is the 3 mm standard tested at NSTL? Do the testers actually put a measuring scale against the phone screen? Just curious to know if we've understood the term "3 mm" correctly...
[C3:]
Yes they put measuring scales and/or any other methods; but make sure that it greater than or equal to the specified value in mm.
thanks,
Shivendra

Thanks for the clarification Shivendra! 2 mm seems to be a more appropriate standard. So, until we receive a notification from Qualcomm about the 2 mm change, submitting an app with font height less than 3 mm but more than 2 mm would still fail right? Is there a definite date by when this notification (3 mm to 2 mm) will be out?
Thanks again!

Thanks for the clarification Shivendra! 2 mm seems to be a more appropriate standard. So, until we receive a notification from Qualcomm about the 2 mm change, submitting an app with font height less than 3 mm but more than 2 mm would still fail right? Is there a definite date by when this notification (3 mm to 2 mm) will be out?
Thanks again!

In my app
A,B,C,D,E,f,g,h like character are of 8 pixels
and a,c,m,n,o are of 6 pixels.
For application's target device screen size & resolution 9 pixels forms 2mm.
my doubt is whether the requirement applies to minimum size or average size?
So does requierment say characters like a,c,m,n,o must be of 9 pixels?

In my app
A,B,C,D,E,f,g,h like character are of 8 pixels
and a,c,m,n,o are of 6 pixels.
For application's target device screen size & resolution 9 pixels forms 2mm.
my doubt is whether the requirement applies to minimum size or average size?
So does requierment say characters like a,c,m,n,o must be of 9 pixels?

Below UI test cases are not mandatory now. These test cases will be run and any apps that don't comply will pass but with notes.
2.3.5.4 – User Interface Controls – Minimum Text Height
2.3.5.5 – Touch User Interface Controls
If your application failed solely based on the UI test cases, it will not fail TBT. The results will be documented and the Application will be passed with notes.

Below UI test cases are not mandatory now. These test cases will be run and any apps that don't comply will pass but with notes.
2.3.5.4 – User Interface Controls – Minimum Text Height
2.3.5.5 – Touch User Interface Controls
If your application failed solely based on the UI test cases, it will not fail TBT. The results will be documented and the Application will be passed with notes.

Hi ,
I have a point to make regarding the minimum font height. I feel that the font height of 2mm standard should be phone specific and not common for all phone types.
We have a product on BREW phones and we do porting on phone with various pixel sizes eg 128*148/240*298 etc.
The font height of 2mm is too big for small LCD phones. Making app with the font height of 2mm makes the app less usable as less data will be accomodated in one screen.
I also feel that this limitation should never be mandatory by Qualcomm and to be left on to developers. Let developer feel free to make his/her application usable. If he will make the app will too small font, users wont see the data on screen and if he makes too big then less data would be visible on screen. In both these cases developer will be at loss.
Please share your comments on this.
Thanks
Sam

Hi ,
I have a point to make regarding the minimum font height. I feel that the font height of 2mm standard should be phone specific and not common for all phone types.
We have a product on BREW phones and we do porting on phone with various pixel sizes eg 128*148/240*298 etc.
The font height of 2mm is too big for small LCD phones. Making app with the font height of 2mm makes the app less usable as less data will be accomodated in one screen.
I also feel that this limitation should never be mandatory by Qualcomm and to be left on to developers. Let developer feel free to make his/her application usable. If he will make the app will too small font, users wont see the data on screen and if he makes too big then less data would be visible on screen. In both these cases developer will be at loss.
Please share your comments on this.
Thanks
Sam

This has got to be one of the most absurd requirements that I've seen yet out of BREW/Qualcomm/NSTL, whoever it is that's running this show. I could understand them making a subjective statement about the use of a readable font, and that could be helpful in the notes section of the testing results. But for them them to call it an 'error,' give me a break. NSTL's job should be to check the stability of the app and make sure that it plays nice on the device, not to mandate UI requirments. If a carrier sees the note and still wants to pick up the app, that's their choice and shouldn't need some waiver nonsense. Not only that, but the idea of your app being flagged with an error for using something that is packed into the BREW SDK, which many OEM system fonts do fall short of this req, is laughable. We had an app get poo-poo'ed on for having a font < 2mm, and it was using the system *normal* font, not even anything custom that we created. And they wonder why people are fleeing BREW development for other mobile platforms that are more consistent and easy to develop on without having to play the game of dealing with all these ridiculous device-specific problems and moving NSTL targets. :mad:

This has got to be one of the most absurd requirements that I've seen yet out of BREW/Qualcomm/NSTL, whoever it is that's running this show. I could understand them making a subjective statement about the use of a readable font, and that could be helpful in the notes section of the testing results. But for them them to call it an 'error,' give me a break. NSTL's job should be to check the stability of the app and make sure that it plays nice on the device, not to mandate UI requirments. If a carrier sees the note and still wants to pick up the app, that's their choice and shouldn't need some waiver nonsense. Not only that, but the idea of your app being flagged with an error for using something that is packed into the BREW SDK, which many OEM system fonts do fall short of this req, is laughable. We had an app get poo-poo'ed on for having a font < 2mm, and it was using the system *normal* font, not even anything custom that we created. And they wonder why people are fleeing BREW development for other mobile platforms that are more consistent and easy to develop on without having to play the game of dealing with all these ridiculous device-specific problems and moving NSTL targets. :mad: