It’s just a few semantic steps from icon to saint to death. A couple of weeks ago (in the previous post, in fact) I called the Nexus One iconic. Now arises the question: should Google kill the Nexus One?
Early responses to the question (over at GigaOm) tend toward the emphatic no. Some emphasize that it’s only been out for a couple of weeks: good point. Others praise the NexusOne as a good or better smartphone: may be a good point, I’ve yet to use one.
I like Evernote as a lightweight means of capturing notes on the Android, and having them available when I’m on the web via laptop (or desktop, if I ever use one again).
I’d like this blog to look Androidesque, and not only on an Android. One way of getting the Androidesque aspect is using Droid fonts on all platforms. One step toward that is using TypeKit.
TypeKit is a web service that allows you access to hundreds of fonts for your websites. The Droid fonts are available, even in the Trial/free plan.
I’ve started using Typekit to put Droid fonts on this blog, starting with Droid Serif for post content. That doesn’t guarantee that you’ll see this in Droid Serif, though. See the note on browser support.
My very early impression of Typekit is that it’s at the stage meriting labels such as: early; very promising; currently frustrating. As an illustration of the last label, I tried to make a support suggestion, but couldn’t because I wasn’t signed in. WTF: I was signed in to Typekit. That’s all it should take. I shouldn’t have to use some other id/password combination.
The Android icon is a specific shade of green: #A4C639 (source: brand guidelines). It’s already referred to as Android Green (source/example: Wikipedia).
I tweaked the theme of this blog to use that very green for the blog title. I mean the main theme, PrimePress; I’ve yet to touch the mobile theme. That got me thinking of changing the other colors used in the theme, and about a palette featuring Android Green.
Before Droid was the name of an Android phone from Verizon and Motorola, it was the name of this collection of fonts.
These fonts are available under the Apache license. There will be more about this license, and Android’s use of it, in a future post; for now, I’ll just remark that it’s a free software license.
Ascender Corporation developed the Droid fonts. It continues to work on them. Some versions of Droid fonts will be available under commercial licenses.
The Droid fonts should not be confused with the Android Custom Typeface, which is used in the Android logo. I am prevented from showing you the Android Custom Typeface by two things: first, I like you too much to inflict it upon you; and second, the Android brand guidelines forbid me from doing so.
The Droid fonts are key to the Android experience – yes, even more than the Iconic Android is. And I rather like them.
Brief review so far: good phone, in terms of the device itself and in terms of service from T-Mobile; useful for checking email, and for some other webby things; decent camera; weakest point is the GPS.
There are many other Android phones, with more on the way. I’ll link to TechCrunch’s list, since it includes remarks on each phone, and the promise of updates.
Here are Boto and his friend Botaka enjoying the current season (usually called fall here in Boston, although I consider autumn to be a far better word). I recently bought this print from the artist, Chen Reichart. Much of her work is about the adventures of Boto (the male robot) in Japan. See her blog and store for more.
The picture is obviously relevant to the Android icon theme. In fact, it’s even more relevant to the Android phone, in that we may well become a two-Android family soon.