Have a look at these great typographic maps of city neighbourhoods from ORK. There’s only Chicago and Brooklyn at the time of writing, but coming soon are Manhattan, San Francisco and Boston. I can’t wait for the Manhattan one.
They remind me a little of this typographic map of London, though I’d be interested to see London represented in the same style as the ORK ones. Well, that and other cities of the world too.
So, as postedelsewhere, the Android platform now has its own set of fonts, created by Ascender Corp. They look pretty good from what I can tell from the PDF sampler, though only time will tell how they’ll be used. I’ve writtenbefore on the subject of mobile typography, and it’s clear that the problems with it are rarely down to the actual font - Nokia Sans is, after all, a rather pleasant face. What I’m really interested in is if the Open Handset Alliance will create a strict set of UI guidelines, with a grid, and whether any of the manufacturers will adhere to them.
So here’s the sampler from the PDF, without the hideous distracting colours (the fact that they were displayed thus doesn’t bode well to my mind):
Well, based on this fabulous brochure, who could blame them? Found on the Old Car Manual Project, another of those collections-of-things sites that you bookmark because you know you’re going to find them useful someday. This site is a great resource for 20th Century typography, illustration and layout, not to mention car design.
Long ago, I used Moveable Type for my other site, so I’m always interested in how it continues to develop. Hearing that MT 4 was out, I headed over and had a look. Oh my word, what a mess! Just take a look at this, then compare with one from Expression Engine, below.
After writing the big piece on mobile phone typography, I came across this odd little concept phone from BenQ. I can’t find out much more than that it has a touch screen, and it looks rather lovely. No typography required when you’ve got beautiful, expressive icons! OK, OK, you need it for messages and stuff… but hey.
I love the koi! It looks like this icon (at right) you used to be able to download here.
Another thing I came across. These watches labelled as “The SEIKO Electronic Ink watch for women”. Why specifically for women though? Apart from what the display can show, these don’t look particularly feminine. I think the e-ink watch idea is a good one though, and somewhat related to my post about mobile typography and manufacturers’ seeming obsession with 7-segment-style characters for showing the time, I think there’s a real opportunity to use non-lining numerals to display the time. At right, some examples.
I already wrote about typography on mobile devices, with a focus on the S60 platform and obligatory mentions of the iPhone and non-obligatory mention of the LG Prada phone. What I failed to mention was the current state of play over in the world of Windows Mobile. I don’t intend to write an exhaustive review of the OS, or of every screen; this is more of a first impressions piece.
Microsoft have recently released the latest incarnation of the platform with Windows Mobile 6. I’ve seen adverts for version 5 (I think) around the place, and the shots that they’ve been using to advertise it (what’s this, using the UI in ads? Encroyable!) are fairly attractive and well laid-out. At right is a screenshot from a landscape-format device, and it looks quite similar to the S60 layout, though perhaps making a better use of space.
What’s the rest of the OS like though? Looking at some screenshots from mobile-review.com I have to say it’s not too bad at all. The type looks like Tahoma and is of course rendered using ClearType, which raises an important question; Why don’t more mobile devices use some form of smoothing? It’s not down to processing power surely? S60 devices used SVGs for their OS elements (all vector) and are smoothed rather nicely, so why not the type? Very odd indeed. So, apart from the type rendering being good, as I said, the layout and typography of WM6 is generally OK, but has a few odd inconsistencies. The main home screen (bottom left, below) has that rather odd search bar cutting across it, and then, apparently for the sake of cramming in the Windows Live icon, the left margin is broken, ruining the layout and making it difficult to ‘scan’ the screen - something that should be a paramount concern for any mobile device. The odd placement of the search bar might be down to user preference, but the Windows Live block should have been better to start with. It makes it look like someone designed it nicely, then extra stuff was just thrown at it til it stuck. Mind, the left margin itself is defined by the unnecessary divider line between the Windows logo and the ‘Start’ label, rather than the left edge of the label itself, which is typical of a design process that fails to operate on a strict principle of less is more. The type defines the margin! You don’t need an extra line! Grr.
The email screen (top left, below) is interesting just for the different sizes of the type used. The ‘from’ field looks fine (though any UI designer might ask why the field is needed at all) but for some reason the ‘to’ field is set in a larger type, and doesn’t share the same left margin. The mobile review people seem to be of that accursed group that sends emails with no subject (or maybe they got confused and ‘news’ is meant to be the subject) so we can’t really tell what that would look like. The keyboard stands out from the whole set of screens. It looks like it was grabbed wholesale from a different device entirely - it doesn’t match the green glassy theme at all, and I can’t really see why. I could get all Tufte about it, but do the buttons need to be all embossed with rounded corners and gaps between them? It all conspires to reduce the apparent click area. In fact, do the buttons Fitt’s Law right up to each other, or if you were to hit the three pixel gap (2 for borders, 1 for background) between them, would nothing happen?
I’ve recently started on designing a theme for the Symbian 60 platform. The software from Nokia, Carbide, is reasonable enough, providing access to almost every part of the UI for editing. All the elements of the UI are built using embedded SVGs, allowing them to scale to any resolution and meaning that themes can be used across a variety of devices without needing to be redesigned or rebuilt. However, as I said, the app only provides access to almost all parts of the UI. The one (to me) all-important omission is access to the fonts and typography of the UI. All Nokia S60 phones appear to use the company’s own font, Nokia Sans. It’s not a bad font by any means, it’s suited to low resolution applications and scales up to medium resolutions fairly well, but it’s just so dull and looks just so Windows 3.1 clunky. Also, the font that’s used for the standby ‘screensaver’ clock, Series 60 ZDigi, is just utterly vile. I don’t get why product designers have this obsession with making high resolution full-colour LCD screens look like ancient 7-segment displays. The numbers in Nokia Sans are perfectly readable and reasonably attractive (for a standby clock, it would be just fine) but instead the phone uses this horrid thing and you can’t change it.
So, in the process of trying to make a new theme I was looking into “alternative” ways to change the system font, and David of typographer.org pointed me at this hack. All very promising, but it didn’t work on my 3rd Edition phone. I suspect they’ve locked down the system files a bit more, though why they let you modify the theme at all and then get all protective about the fonts I have no idea. For them to allow (and encourage) people to make themes, but not change the font, it seems inconsistent and unnecessary - after all, if you screw up all the icons, backgrounds and menus, or just make something hideously ugly, it would make the phone just as unusable as copying over a duff TrueType would. By comparison, both Apple and Microsoft are very protective of their OS look and feel, only allowing very minor changes - you essentially can’t change anything, so I guess it’s better than nothing.
While I was rooting about in the S60 system files I noticed that as well as the four font files listed on the darlamack page, there were four others. I copied them over to have a look, and these look to be the fonts used on the Messaging and Web applications, and are suspiciously similar to Arial. At first I thought they were a Helvetica clone, given the name of SwissA, but a closer look (below) shows they are in fact clones of Arial. Interesting.
I could hardly make a post about Mobile Typography without a reference to the Apple iPhone. The UI of that object of desire is really quite beautiful, and graced with true, genuine, honest-to-God Helvetica. Now, as far as I know, it’s also the only phone that’s been advertised purely on its UI, because that’s what the whole thing is about. Behold:
The adverts for the Samsung D840 showed you the hardware buttons and how the glossy front of the phone is so reflective it can be used as a mirror, but with no showing off of the UI. The Motorola RAZR had a similar set of ads - you’re invited to gawp at the thin, sleek hardware, but you’re not shown the UI. Same for most of the Nokia ads in fact. That’s because the default UI is at best workable, at worst, hideous. Maybe it’s deliberate? If the UI of these other phones was usable, responsive and beautiful, there’d be little need for themes and a big source of revenue (from advertising on the theme sites alone) would disappear.
Well, it’s a theory.
And while we’re on the topic of phone UIs not being shown in adverts, here’s one that should have been. The Prada phone by LG. Follow that link, and once the great chunk of Flash has loaded, try and find some shots of the UI. They’re not there. And yet, courtesy of this article about the LG Prada on GSM Arena, you can see that it’s absolutely nothing for them to be ashamed of. I love the typeface too, especially the ‘w’. Not that you can see it too well on the examples. There are some close up photos in the article, mind.
This is what’s inspired me to create the theme for the S60, in fact.
Ah, the joy of technology. Posted from an e61 while sat in the pub. Sadly the phone is not mine… It’s bloody good though. I want the successor to it, the e61i. Then I could take pictures and blog those too!