Just had a meeting with Yuvi and we decided that we should keep the fonts consistent on android app with android mobile web for the time being, and not introducing another font (Open Sans) in the mix. The changes will take a few minutes of work, and Yuvi has already made a card for it on trello.
The changes include keeping page styling consistent with mobile web on android using Roboto for text and using Roboto for app chrome typography too.
On 05/28/2014 07:55 PM, Moiz Syed wrote:
Just had a meeting with Yuvi and we decided that we should keep the fonts consistent on android app with android mobile web for the time being, and not introducing another font (Open Sans) in the mix. The changes will take a few minutes of work, and Yuvi has already made a card for it on trello.
The changes include keeping page styling consistent with mobile web on android using Roboto for text and using Roboto for app chrome typography too.
Roboto for text? We don't use Roboto for text in mobile web.
On Wed, May 28, 2014 at 11:13 AM, Juliusz Gonera jgonera@wikimedia.orgwrote:
Roboto for text? We don't use Roboto for text in mobile web.
We don't specify Roboto, but it's the sans-serif that matches the current stack, correct?
That's correct
On Wednesday, May 28, 2014, Steven Walling swalling@wikimedia.org wrote:
On Wed, May 28, 2014 at 11:13 AM, Juliusz Gonera <jgonera@wikimedia.orgjavascript:_e(%7B%7D,'cvml','jgonera@wikimedia.org');
wrote:
Roboto for text? We don't use Roboto for text in mobile web.
We don't specify Roboto, but it's the sans-serif that matches the current stack, correct?
-- Steven Walling, Product Manager https://wikimediafoundation.org/
Not really. Firefox and Chrome give me different fonts on Android, using their own default configurations...
-Liangent
On Thu, May 29, 2014 at 2:28 AM, Steven Walling swalling@wikimedia.orgwrote:
On Wed, May 28, 2014 at 11:13 AM, Juliusz Gonera jgonera@wikimedia.orgwrote:
Roboto for text? We don't use Roboto for text in mobile web.
We don't specify Roboto, but it's the sans-serif that matches the current stack, correct?
-- Steven Walling, Product Manager https://wikimediafoundation.org/
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
On Wed, May 28, 2014 at 11:33 AM, Liangent liangent@gmail.com wrote:
Not really. Firefox and Chrome give me different fonts on Android, using their own default configurations...
A bit of poking around shows that Firefox on Android may ship with Clear Sans. In any case, Firefox is such a small proportion of mobile browser share that it's kind of a non-issue. In either case, we're stuck with a much more limited font stack on Android unless we decide to provide a font with the app.
On Wed, May 28, 2014 at 10:47 PM, Steven Walling swalling@wikimedia.org wrote:
A bit of poking around shows that Firefox on Android may ship with Clear Sans. In any case, Firefox is such a small proportion of mobile browser share that it's kind of a non-issue. In either case, we're stuck with a much more limited font stack on Android unless we decide to provide a font with the app.
Right now, we are providing Open Sans with the app. Now we are removing that to just use the same stack as MobileFrontend for consistency.
On Wed, May 28, 2014 at 2:50 PM, Yuvi Panda yuvipanda@gmail.com wrote:
On Wed, May 28, 2014 at 10:47 PM, Steven Walling swalling@wikimedia.org wrote:
A bit of poking around shows that Firefox on Android may ship with Clear Sans. In any case, Firefox is such a small proportion of mobile browser share that it's kind of a non-issue. In either case, we're stuck with a
much
more limited font stack on Android unless we decide to provide a font
with
the app.
Right now, we are providing Open Sans with the app. Now we are removing that to just use the same stack as MobileFrontend for consistency.
Thanks for the context Yuvi.
BTW, an interesting discussion to compare to is this Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=958879