I came across this really interesting article on mobile typography at the Ministry of Type blog. It spells out the difference between the iPhone and the average mobile phone.

It’s also the only phone that’s been advertised purely on its UI, because that’s what the whole thing is about. 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.

Why is most mobile UI design unusable, unresponsive, and ugly? Here’s one theory: “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.”

I’m not sure if this is a serious theory, but there might be some truth in it. Desperate to upgrade their poor interface experiences to a superior one, users purchase a new theme, hoping it’ll solve their problems. Unfortunately, themes are superficial solutions to mobile interface problems. Anyway, I don’t think this theory works, though it does highlight a problematic approach to interface design.

Manufacturers need to address the deeper problems with interface design on the mobile phone. They must focus on making software and hardware more powerful in order to accommodate users’ needs, as the mobile phone becomes a web-browsing device as well as a phone. Manufacturers will, and are, shifting from seeing a mobile phone as a mobile phone, to seeing it as a mobile internet device as well. Nokia admitted in May that they’re now competing with Apple, Microsoft and Google.

Mobile’s restrictions are frustrating both for users and for designers. One of the most frustrating things for me right now, to use one example, is working with antialiased outlines on mobile phone graphics. For those unfamiliar with the term, antialias means, in plain English, the smoothing process between the object and the background, whether font or graphic element. (Here’s a simple illustration.)

Mobile interfaces, composed of typography and graphic elements, suffer because of this lack of support for alpha antialiasing across devices. When I say mobile interfaces “suffer”, I really mean users. Lack of wide support for alpha antialiasing is just one example of the inadequacies of mobile interfaces. However, inadequacies present new, interesting challenges, both for designers working with the imposed restrictions, as well as companies spotting opportunities for improvement.