3 ms·
Microsoft Band, curved screen, tiny DPI, and we initially were using raster fonts, not true type. 4 bit alpha for anti-aliasing. Primary glyphs were hand hinte
by com2kid 5y ago
Microsoft Band, curved screen, tiny DPI, and we initially were using raster fonts, not true type. 4 bit alpha for anti-aliasing.
Primary glyphs were hand hinted, with glyph of each font size custom made to fit on our grid.
For v2 we ended up using Monotype's awesome embedded font engine that let us have real true type font rendering in just kilobytes of RAM with a 96mhz CPU. Insanely cool tech, I believe we were the first adopters of it, we helped them optimize a fair bit of the underlying engine code, and fixed some bugs along the way.
Still a custom font file though. Both the true type and raster fonts were variants of Segoe, Microsoft's main UI font. We wanted it to be on brand, but also look great on our screen.
So tl;dr that is why the MS Band 2 had really good looking CJK glyphs and it is how we pulled off anti-aliased fonts on a tiny LOL CPU with next to no RAM. :)