Lato perfectly matches the iOS7 style of the Streamline icon collection, especially when using the thinnest font weight. The iOS7 style is based on a thin monolinear style with slighty round corners and a lot of white space inside the icons.
That’s why Lato, with its almost geometric style and a beautiful counterspace and generous aperture was a perfect companion for the icons. A great benefit of using Lato: it’s provided via Google fonts. Most users would have it already downloaded in their browser cache when they visit the website, make it faster to load.
Morenita shares the same monolinear style but adds a retro touch, which is reminiscient of the streamline architectural style from the 1930s.
Lato is a popular font among the google web fonts, so it’s used on a lot of websites. Strong chances that the visitor of my website already loaded on a previous website, and have it on his browser cache loaded already.
Well, Google explains it better than me: “After that initial download, they will be cached in the browser. As the Google Fonts API becomes widely used, your visitors will be likely to already have the font you’re using in their browser cache when they visit your page.”
That’s Google doing self-promotion. It should be taken with a grain of salt. While it is true that Lato is among the more popular (and better) fonts served by Google, saying that it is “likely” that a user already has it in the cache is wishful thinking, and does not correspond to my observations. It certainly is not an authoritative criterion in picking a font. Not that Lato was a bad choice for your website.
The other statements in that performance section of the Google Fonts FAQ are reasonable. They should probably just strike the bit about the likelihood of Google fonts cached from other sites.
Why do you think it is unlikely? Lato has been served 32,065,139,807 times total, 3,458,087,535 a month, 861,318,380 times per week, 127,398,593 times per day.
5 Comments on “Streamline”
Lato is a popular font among the google web fonts, so it’s used on a lot of websites. Strong chances that the visitor of my website already loaded on a previous website, and have it on his browser cache loaded already.
Well, Google explains it better than me: “After that initial download, they will be cached in the browser. As the Google Fonts API becomes widely used, your visitors will be likely to already have the font you’re using in their browser cache when they visit your page.”
That’s Google doing self-promotion. It should be taken with a grain of salt. While it is true that Lato is among the more popular (and better) fonts served by Google, saying that it is “likely” that a user already has it in the cache is wishful thinking, and does not correspond to my observations. It certainly is not an authoritative criterion in picking a font. Not that Lato was a bad choice for your website.
The other statements in that performance section of the Google Fonts FAQ are reasonable. They should probably just strike the bit about the likelihood of Google fonts cached from other sites.
Why do you think it is unlikely? Lato has been served 32,065,139,807 times total, 3,458,087,535 a month, 861,318,380 times per week, 127,398,593 times per day.