Motorola Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Saturday, 4 April 2009

The ugliest logo ever, but maybe it makes sense

Posted on 20:36 by Unknown
Logo creation is a thankless task. Almost all of the interesting shapes and doodles were trademarked years ago. Unless you have hundreds of thousands of dollars to spend on artists and lawyers, and a lot of time, you usually settle on using your company name with no artwork at all.

Or you can take the approach adopted by the newly-formed Symbian Foundation, keeper of the Symbian OS:



Yes, that's really the new Symbian logo. I guarantee no one's going to sue them for it, unless it's the producers of the movie Juno:



I've already gone through a couple of stages of reaction to the logo. The first was horror. Not only is the font something out of 1974, but the color is one of the least popular in the world (step outside and count how many yellow cars you can see, or click here or here). I know I've seen uglier logos in the past, but I can't remember where, probably because I tried to block out the memory.

The discussion on All About Symbian has been amusing (link).

Once I got over my reaction, I reminded myself that the folks at Symbian are smart and very deliberate. Let's assume they have a good reason for choosing this logo. What would it be, and what would it tell us about the company and its business strategy?

The new Symbian is an open source software project. They need to appeal to open source developers, many of whom have a reflexive hatred toward slick and calculated marketing. After all, these are the sort of folks who, when allowed to choose their own logos, spontaneously chose a fat, stoned-looking penguin and a drunken ox:



The GNU Gnu Head and Tux the Linux penguin (link)
Tux drawn by lewing@isc.tamu.edu. Gnu head reproduced under the copyleft license (link).


To the open source community, Symbian has historically been kind of an antichrist -- controlled by some of the biggest tech firms in the world, bureaucratic, closed, and incredibly complex. If you're going to win over the open source crowd, you have to overcompensate by being excessively informal, friendly and "childlike." (That's Symbian's word for it, not mine.)

Here's how Symbian explains the logo (link):

It is a brand that’s human and playful and friendly, where you feel the human hand. A brand that enables you to discover unlimited creative possibilities, that wants to share and talk A brand that’s fun, that isn’t fixed, but free to constantly evolve. A brand that’s owned by all the people that create and build with Symbian. A brand that celebrates new ideas and creativity in all forms. A brand that’s truly alive and refreshingly different, because it is! A brand that’s human to the core and that underneath beats a human heart.

In other words, the slick and calculated marketing approach is to give the company the most artless logo imaginable. And from that perspective, I think they succeeded.

I am wondering, though, what they'll do when it's time to use the logo for something other than just decorating a website. OS logos are generally used as compatibility marks. In that role they need to be displayed on screen, and preferably printed on the back of the phone, to let the user know that he or she can run Symbian applications on the device.

Picture a meeting where the folks at Symbian try to convince a product manager at Nokia or Samsung or SonyEricsson that they should print that logo on the backs of their phones, or that it should be displayed prominently on the screen. I don't think it'll go over very well. And even if they did agree to include the logo, the tiny details in the lettering won't show up well when reduced in size. The logo just isn't designed to travel.

So Symbian app developers should ask how they'll be able to market their applications when Symbian OS users don't even know what their OS is. Symbian has never had a good answer to that, and I think the new logo doesn't move them any closer to solving that problem.

Maybe the assumption is that all Symbian phones will have application stores built in, so developers won't need to communicate compatibility. Maybe, but that will still put a big marketing burden on an application developer to explain model by model which phones their apps work on.

The bottom line is that any logo artless enough to please the open source community would be problematic as a marketing tool. As is often the case in marketing, you can't please all your audiences, so you can either be universally bland or you can optimize for one audience. I think the folks at Symbian decided that open source street cred is the thing they need most.

And maybe they're right.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in symbian | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Google Video: Is that all there is?
    Google's new video store seems to be up and running. I say "seems to be" because when I looked at it my first reaction was, ...
  • RIM's Pearl: Splendid hardware, unfinished software
    For me, the highlight of fall CTIA this year was that I finally got to play with a Pearl, RIM's latest smartphone. It has more media fe...
  • A new way to measure the popularity of the iPhone
    True story: Back when I was working at Apple, we received a report that there had been a burglary at a company that had a lot of Macintosh c...
  • "Social" as a Business Tool, and Richard Windsor Unchained
    I'd like to call your attention to two new information resources on the web. "Social" as a business tool.   First, my friend a...
  • Why Apple + RIM would be a bad idea
    Several days ago a financial analyst in Canada floated the idea that Apple and RIM might collaborate to create the merger of an iPod and a ...
  • What does Google want?
    I’ve been doing a lot of networking in the last couple of months, meeting new people and getting in touch with old friends and co-workers. I...
  • Mobile phones and navigation: I've seen this movie before
    Reuters published an article saying that navigation features are the hot new data function on mobile phones. News.com picked it up, and by...
  • Motorola Rokr: Instant Failure
    I did an online search today for the words “Rokr” and “failure” together in the same article. There were 49,700 hits. I don’t want to pic...
  • Look what's number one
    The image above was sent to me today by a former PalmSource colleague. Yes, that's a list of Amazon's best-selling consumer electron...
  • The river and the dam: CTIA and The Future of Web Apps
    I went to two conferences this week: the CTIA telephony conference in Los Angeles and The Future of Web Apps in San Francisco. It's al...

Categories

  • Adobe
  • Air
  • Amazon
  • android
  • Apollo
  • apple
  • applications
  • April 1
  • att
  • avatar
  • blackberry
  • cera
  • China
  • Chrome
  • clearwire
  • community
  • conference
  • content
  • convergence
  • ctia
  • design
  • developers
  • devices
  • digital chocolate
  • ebook
  • entertainment
  • eTel
  • foleo
  • GMR
  • google
  • HP
  • htc
  • IBM
  • influencers
  • info ecosystem
  • info pad
  • information overload
  • intel
  • internet
  • ipad
  • iphone
  • japan
  • kindle
  • linux
  • Logitech
  • metaplatform
  • Metro
  • microsoft
  • mobile
  • mobile data
  • mobilists
  • motorola
  • N95
  • nano
  • net neutrality
  • netbooks
  • new media
  • Nintendo
  • nokia
  • O'Reilly
  • O'Reilly TOC
  • operators
  • oqo
  • OS
  • Palm
  • PDF
  • platforms
  • Pre
  • PS3
  • psion
  • qualcomm
  • RIM
  • rubicon
  • samsung
  • search
  • security
  • semantic web
  • Silverlight
  • smartphone
  • smartphones
  • Sony
  • speech
  • sprint
  • symbian
  • tablet
  • traffic
  • treo
  • twitter
  • verizon
  • video
  • virtual reality
  • vista
  • web
  • Web 2.0 summit
  • web apps
  • webos
  • wimax
  • windows
  • Windows Mobile
  • yahoo
  • zekira

Blog Archive

  • ►  2013 (10)
    • ►  September (1)
    • ►  July (1)
    • ►  June (2)
    • ►  May (1)
    • ►  April (2)
    • ►  March (3)
  • ►  2012 (17)
    • ►  October (2)
    • ►  September (1)
    • ►  August (1)
    • ►  July (1)
    • ►  June (1)
    • ►  May (2)
    • ►  April (4)
    • ►  March (2)
    • ►  February (2)
    • ►  January (1)
  • ►  2011 (28)
    • ►  December (1)
    • ►  November (1)
    • ►  September (2)
    • ►  August (7)
    • ►  June (4)
    • ►  May (1)
    • ►  April (4)
    • ►  February (7)
    • ►  January (1)
  • ►  2010 (20)
    • ►  December (1)
    • ►  November (2)
    • ►  October (2)
    • ►  September (1)
    • ►  August (1)
    • ►  July (1)
    • ►  May (1)
    • ►  April (3)
    • ►  March (1)
    • ►  February (2)
    • ►  January (5)
  • ▼  2009 (22)
    • ►  November (3)
    • ►  October (1)
    • ►  September (1)
    • ►  August (2)
    • ►  July (1)
    • ►  June (2)
    • ►  May (1)
    • ▼  April (5)
      • Microsoft: What could have been
      • The lesson from OQO
      • Checking in on smartphone and Twitter usage
      • The ugliest logo ever, but maybe it makes sense
      • Thoughts on the tech industry bailout
    • ►  March (1)
    • ►  February (1)
    • ►  January (4)
  • ►  2008 (32)
    • ►  December (4)
    • ►  October (1)
    • ►  September (1)
    • ►  August (2)
    • ►  July (1)
    • ►  June (3)
    • ►  May (3)
    • ►  April (3)
    • ►  March (7)
    • ►  February (4)
    • ►  January (3)
  • ►  2007 (61)
    • ►  November (8)
    • ►  October (1)
    • ►  September (5)
    • ►  August (4)
    • ►  July (4)
    • ►  June (2)
    • ►  May (4)
    • ►  April (5)
    • ►  March (10)
    • ►  February (6)
    • ►  January (12)
  • ►  2006 (73)
    • ►  December (7)
    • ►  November (4)
    • ►  October (7)
    • ►  September (6)
    • ►  August (4)
    • ►  July (4)
    • ►  June (7)
    • ►  May (5)
    • ►  April (8)
    • ►  March (6)
    • ►  February (6)
    • ►  January (9)
  • ►  2005 (22)
    • ►  December (9)
    • ►  November (6)
    • ►  October (7)
Powered by Blogger.

About Me

Unknown
View my complete profile