1. From a marketing perspective, it incorporates your branding: It has to be easy to decipher, easy to recognize, and it should employ the main strengths of your brand.
   From a usability perspective, it needs to give the users hints about your apps main functionality. But it is strongly advised not to overstimulate this: If the actual app fails to fulfill the expectations that the icon sets, you will burn your users.
2. From a graphic design perspective, the icon has to look beautiful, strong, and not out of place when it is composed into its actual environment (i.e. the iPod Screen, or the Mac OS X Dock).
3. From a semiotic perspective, the signs and symbols that you use should have a shared and distinct meaning in your audience. If you intend to use symbols (like a note, a truck, a cup, a newspaper, or a book) you should make sure that they fit the attribution you are trying to apply in general.
4. Finally, the icon is the entry point into your app experience. And in most App Stores (iPod / iPhone, Ovi, Android …) the icon also represents your advertising in the store. It is the first thing people see, and the icon quality can influence the decision whether people like to request more information or not.

Now, that does not mean that only perfect icons will lead to success (as Google has shown time and time again), but if you have limited other advertising resources at hand, then it is certainly advisable to optimize the hell out of your icon.

For my newest app, my first entry into the Mac App Store, I had to design an icon that had to explain a difficult concept to a mass market. The icon started with a base idea and then was optimized through 8 iterations.One can clearly see its development path, and I would like to explain the process that has lead to the final icon, so others can learn about the thinking behind it.

The App, Clarity

(www.clarity-app.com)
When I designed the app, I had three key features that I wanted to implement.

1. Facebook Stream Client
Facebook offers with its News Streams a feature that is very similar to Twitter but oftentimes succeeds where Twitter fails as more of your close friends are probably on Facebook and so it is easier to feel connected.
However, even though there are a couple of very good desktop Twitter clients (Tweetie, Echofon, Kiwi, etc), there are far less desktop Facebook Stream clients. There are some multi-clients (supporting Twitter, Facebook, and others), but given the huge set of Facebook features, their support is often poor. Therefore, my objective was to develop a Facebook Stream client, that would run on my desktop and inform me of the newest events in my friends‘ lives.

2. Pleasing & Uncluttered Interface
The second key feature has to do with the way news streams are presented on Facebook: Cluttered. The recent font-size change (smaller) did not really help the general impression of unsorted and unstructured heaps of text. For a long time, I longed for a simple interface that omits unnecessary information and just presents key aspects in an aesthetically pleasing interface.

3. Only write to and read from specific social subnets
The third and last key feature is something that I really miss on Facebook but which seemed possible to pull off given their data structures: Posting status messages to subsets of your friends. Many people combine different social networks on Facebook: Work friends, School friends, Football friends, and more. Most of the time, when posting a status update, people have one specific social (sub) network in mind. However, while Facebook allows you to group friends in lists, it does not allow you to just post to one of these lists.

To sum it up, my app Clarity is a Facebook Stream Client that tries to display the information in a simple, structured, and aesthetically pleasing way. It supports the concept of different social sub networks defined through friend lists which allow you to write to or to read from just some of your friends. Furthermore, my goal was to offer a simple and satisfying way to sort friends into these friend lists, since the original Facebook interface is rather cumbersome and has kept me – so far – from actually creating lists for all of my friends.

Key Features the Icon Should Display

The list of features above had to be represented in the icon.

• Facebook News Client
• Simple / Structured Display of the news
• Being able to read from or write to specific friend lists
• A simple way to categorize these friends

Obviously that is not only a lot to display but also incredibly difficult to explain in an icon. Therefore, I decided to group and consolidate these features to just gain three easily identifiable elements.

1. Facebook Client
I decided to remove the ,Stream‘ and tried to explain that in the accompanying text. Even though I could have applied ,Messages Bubbles‘ to explain the ,Stream‘ metaphor, I decided against it as that might have been too far-fetched to understand. Thus, it was only important to see that the app has to do with Facebook.

2. More Structure
Alas, the name of the app, Clarity, already gives strong hints about this feature. So even though this also had to be part of the icon, I could explain it through another, a smaller element / hint.

3. Friend Lists
Instead of trying to explain the ability to create lists, and write to lists, and read from lists, I reminded myself that most people that I introduced to the feature set of my app, did not even know that Facebook supported friend lists as the function is well hidden in the interface.
Given that, I decided that an icon that resembles ordering or sorting of friends would be appropriate.

Identifying Metaphors and Elements

The Base Design
After lots of thinking, I settled on an open book with varying elements and clearly visible friend profiles as the basis of my icon. On the one hand, the book resembles the actual physical facebook that Facebook originated from, and on the other hand, it offers a big canvas upon which I could try to employ symbols to explain other meanings of the app. With just this basis, I had already hinted at key feature #1, the ,Facebook Client‘.

In the beginning, I thought that it would suffice to layout the contents of the two open pages of the book in a very structured way to hint at feature #2, but I realized that that was not the case as a good structure is the standard and not the exception in books.
Other options would have been to add a ruler, structure markers, or color labels, but neither of these seemed to be easy understandable enough.
I then tried to see this key feature from a benefit-oriented point of view. The main benefit of having a cleaner and more structured interface is that it is easier to find and read information. Thus, I decided to use a loupe since these characteristics apply to loupe very well. The loupe could be placed on the book and hint at the ability to focus on friends, too.
Finally, pulling off feature #3, the Friend Lists, was easy. As I already had an open book with profiles, I could just draw some circles to indicate the creation of friend lists. In order to support the understanding that these lists are being created by the user, I also added a text marker.

First iteration

With this in mind, the first iteration of the icon looked like this:


Clarity Icon Version 0.1

On the left page it reads ,Clarity‘, and on the right side it reads ,Book‘. You can find a big version of the icon here.

This was the start of a series of iterative improvements since there were manifold things, that I did not like. Nevertheless, you should not concentrate on changing details too early in the design process, you will not end up with a solid end result. Instead, you need to start working on the main proposition: The first thing that the user should grasp about your icon. In my case, what I found most unsatisfactory was (1) that the whole icon had an unstructured feel to it, and (2) that the icon paled size-wise in comparison to other Apple icons:

Here, all the icons are 128 x 128. My icon looks so small because it does not really use perspective to its advantage.

Therefore, in the next version I tried to enlarge the icon through a different perspective. I also changed the border color to something less obtrusive, and moved the circles so they were not overlapping – as that seemed to add to the unstructured feel.


This version already looked better but I still was neither happy with the perspective, nor with the clutter, and I found that the elements of the icon did not occupy the available space. If you look closely at other Apple icons, you will find that if there are additional elements, they will be big and clearly visible:

So for the next iteration of my icon, I decided to shift the perspective again, remove one of the friend circles, and enlarge the loupe. Also, I decided to remove the ,Book‘ word to omit even more unnecessary clutter.


Once again, this looked better, but I felt that I had not gone far enough with the sizing, and it still felt cluttered and unstructured. Thus, I enlarged the loupe even more and changed the perspective again.

Next, Iremoved the text markers‘ lid, and also decided to remove the middle line of profile pictures as these did not contribute to the actual understanding of the meaning – since there were more than enough of them. Finally, I found that other Mac icons often had thicker lines so I enlarged the book cover.

This was actually the first time, that the icon started to please me. There were still rough edges, but in general I felt it was going in the right direction, meaning it was going to start looking more “Mac-like”.
Now, that I had the basics in place, I needed to get back to my original key features, and see if they were still being represented well enough.
Beta testers confirmed at this stage that they did not think that the resemblance to Facebook was immediately visible. Thus, for the next version, I decided to settle for a even more “facebooky” look by installing a rectangle filled with the Facebook color to simulate the basic layout of the Facebook homepage. Since I had already been using that color for the book cover, I had to find a different color for the book cover. I settled for a light gray as that matches well with almost any other color.

In addition to that I had the nagging feeling that the hand-drawn circle on the right side was part of the general cluttered feeling that the icon (at least in my point of view) still inhibited. Therefore, I replaced the circles with rounded rectangles as that seemed to fit the overall cubic form of the icon.

This one looks far better. The contrasting blue toolbar really helps the icons‘ appearance. What I did not like was the area where the loupe and the blue headline background overlap in the book middle as that looks very dark and gray. Additionally, the icon still did not feel ,right‘ compared to other Apple / Mac icons as it still seemed to have an awkward position:


In order to fix these problems, I had to do two things. First, I corrected the perspective of the icon again, to make it more akin to XCode‘s. Second, I heightened the pages so that I gained more contrast to the binding.


This result looked really good, and I was already very happy with it. Next to other Apple icons one can see that it looks more at home than the older icon:



Feedback from the beta testers indicated though that they thought that it still did not look as if it was an app for Facebook. I decided to replace the ,CLARITY‘ word with a simple ,f‘ to resemble Facebook.
Now, that it seemed as if the icon was almost done, I could finally take care of the really small tidbits that had annoyed me all the time but were not worth investigating until I reached the semi-final version. First, I thought that the loupe needed a nice shine on the glass. Second, I did not like the overall brightness / shadow composition of the image as that looked rather out of place on my Mac, and third, the book cover had a small, disturbing noise on it. So, with these changes, the final logo looks like this (I also added a shadow):

And here next to other Mac icons:


I started developing the logo on the 27th of December, next to continued programming on the app, and I finished the logo on the 29 of December. Given the short time frame, I am really happy with the outcome. Future upgrades to the app will probably also alter the icon, just as the iTunes icon has changed over time.

Here is a comparison of the first version to the final version of the icon. The most important changes were probably (in descending order) the right perspective, the bigger loupe & text-marker, and the removal of clutter.


Finally, if you design Mac icons, Apple will encourage you not to create only 128px x 128px icons, but to also include a version with up to 512px x 512px. In this big version, of course, one can add far more detail. Here is the big version of the Clarity icon:


You can see that the big version entails more details: One can see the leather from the book cover, one can see the names below the profile pictures, one can see the text on the text marker, and one can see a small descriptive text at the top left.

Oh, and because it sounded like such a funny idea, I also added an animation that shows the iterative development:

The icon was created in Blender 3D, the textures were created in Photoshop, and postproduction was also done in Photoshop.

I disagree, however. As splendid, as the idea actually feels, the characteristics of the two Windows user bases (Developers and Users) won’t resonate with such a setting. Let’s call the two versions “WIN” (New, no legacy code, cool) and “Classic” (Current Windows) Developers only invest their time and money up front if there is a viable market available (or to come), so that the investment is at least likely to generate a positive outcome. They won’t start developing for a new system until the user base is of a certain size (or a huge growth is expected, see iPad). Windows users, on the other hand, are not really known for their progressiveness. I usually tend to divide them into three groups:

1. Business users, who have no choice anyway since IT installs their machines. As businesses are actually the main force behind Microsofts keen upholding of legacy code, there is little reason for them to ever leave Classic. So here we have a very low adoption rate.
2. Non-Computer users: The kind of people who almost accidentally bought their PC at Walmart, still run Windows XP (maybe even 98SE), and mostly use the system to print ugly birthday flyers or play Solitaire. They would probably enjoy WIN, but they won’t ever notice it exists until they go and buy a new PC at Walmart. Here, we have another low adoption rate.
3. The enthusiast Computer user: These are people that grew up with Windows, know (and sometimes love) all of it’s kinks and quirks, and use it for a variety of tasks. They’re its avid defenders in Engadget comment threads and tend to be a tad regressive, since Classic has always worked for them quite well and as they fear loosing the high investment in Windows knowledge that they accumulated over the years. The less regressive, the higher the chance that this particular person has already switched to Mac or Linux. The more regressive, the higher the chance that he/she would actually reject or even despise WIN as it deviates too much from her/his well known Classic. The adoption rate should be pretty solid, but this market segment is also heavily courted by the alternatives.

The problem with the above scenario is that the actual market for a brand new cruft free Windows deems me not big enough to attract enough developer traction to get a larger user base to switch over. One possibility, of course, would be to leverage .NET so that new applications would natively work on Classic and WIN sans problems (much like Apple did with Carbon). This, however, would disable any chances for Microsoft to radically change the user interface, accommodating usability research and results of the past decade.
Instead, I think it would make more sense for Microsoft to create a brand new OS that still runs old apps by means of a virtual machine or something resembling the classic environment in Mac OS X. Microsoft needs to enforce adoption as much as they can, otherwise most of their user base simply won’t switch. (Even the almost 10 years old Internet Explorer 6 is still being used way too much. This simple fact is telling about the Windows demographic)

Let’s move back, for a minute, and consider the state of the music industry, ca. 2001. Napster had moved the task of finding, downloading, and sharing digital mp3 music from the realm of hackers and nerds to the broad public. Suddenly everyone was able to get music in an instant. For free. For years to come, the music industry, and its legal companion, the RIAA, tried everything imaginable to hinder mp3 music sharing, and lecture (or even force) people to buy expensive CD’s or download incompatible music instead. As indicated, by this quote from Jimmy Lovine – Founder and chairman, Interscope Records, it wasn’t until the advent of the iTunes & iPod behemoth, that the market of legal digital music exploded. By now, iTunes has surpassed CD sales and is the worldwide major music distribution platform.

How did Apple achieve this? First of all, there seemed to be a latent demand for legal digital music. People oftentimes claimed that they’d buy music in an instant, if it was available in something other than the arcane CD format. It was, however, possible to buy digital music online before the iTunes Music Store came along, a fact that diminishes the strength of the ‘legal music’ argument. Another important reason was of course the combination of iPod, iTunes, and iTunes Music Store. While previous approaches to selling music online were limited & rather unknown, the widespread success of the iPod brought access to millions of potential customers. Finally, there’s an often-overlooked but very important reason: The ease and comfort of Apple’s solution.

Napster reached such a wide audience not only because of the simplicity of the task, but also because the availability of of music. One could enter an artists name, find tons of related (or unrelated) tracks, and download them with a click. But Napster also had a ton of problems: Many tracks weren’t available at all, it was nearly impossible to get complete albums – mostly only a small selection of tracks, the files were not always in good quality, and almost every download took ages because the sharing party was accessing the Internet by modem.
Whereas iTunes brought best-of lists, fast downloads, high quality files, cover art, a big database of content (except for the Beatles), complete albums, reviews, and much more. And best of all, it was only one click away from the regular iTunes music experience.
I’m fairly confident, that the superior success of the iTunes Music Store lends itself a big deal on the usability of Apple’s solution.

So, going back to the future (or rather lack thereof) of journalism, how can we apply the merits of the digital music solution to newspapers? Since news is already free on the Internet, this market lacks a significant demand for ‘legal’ news. However, as explained above, this wasn’t a big deal for digital music either. The difference is actually marginal: Before iTunes, people could buy digital music, but illegally downloaded free stuff instead. After iTunes people could still buy digital music, but did download far less illegal music. Now, people can buy paper news, but they access free, digital news instead.
If Apple really was to try to reinvent the newspaper, it would need to offer a seriously simplified, less cumbersome, very usable interface. But is this possible? Online newspapers have been evolving for years, the NY Times employs a constantly growing team of web developers to optimize it’s site. These sites still follow a model that lends its basics from the classic newspaper. A frontpage, departments, current articles in chronological order, features, and a ton of adds.
These simple thoughts establish a basic framework which allows to draft a set of requirements for a device that could establish itself as a news platform:
- The perfect size: It certainly has to be bigger than an iPhone. It needs space for a splendid layout, big fonts, high quality pictures, and a general feeling of comfort. However, it shouldn’t be so big as to be considered clunky.
- The layout: Visit Google FastFlip), which introduces a blazingly fast way to read news. Instead of html content, the site serves screenshots of news sites. I’m hardly convinced that Apple will not use WebKit for the iTablet newspapers, but that’s not the point: They just need to find a way to make the browsing and loading of articles incredibly fast.

When I applied the probable factors of success of the iTunes Music Store onto journalism, I left one factor out: The giant userbase of the iPod. The Music Store not only did benefit but wouldn’t have been possible at all without the already available incredible amount of iPod owners. The iTablet, on the other hand, isn’t even on the market yet. So, in comparison to the iPod, where the physical product helped sell the digital content, with the iTablet the digital content would need to help sell the physical product. I imagine newspaper access to be one of Apple’s arguments for the iTablet. While this certainly limits the applicability of the thoughts above, the App Store has shown that even a new content platform can quickly become a selling argument.

If only a bit of these thoughts apply, it would be a chance for journalism. The iTablet scenario won’t help solve many of its inherent problems, like bias, uneven news distribution, or the rise of entertainment, but it might at least help journalism to stay alive – maybe until a conclusive ‘future of news’ has been found. Because weblogs, social news, or Twitter cannot replace journalism.

(1) Apple has steadily improved and refined its brand. Most current consumer ratings place the Apple brand at the top of the list. Our modern society introduced and needs brands as a method of reducing the complexity that the free market as well as globalization bring along. An unbelievable huge amount of slightly differing and ever updating products for any kind of problem can’t hardly be understood and processed by a single person. We’re using mechanisms like journalism / reviews, peer information / opinion leaders or brands in order to artificially limit the range of choices we have to process for coming to a purchase decision.
Brands are especially interesting as they allow to overshadow primary product dimensions: A great brand makes up for product features, product price or product support. If we have a no-name product, we scan for technical features or price. If we have a branded product, most people don’t.

This means that jumping the Apple brand bandwagon sounds like an excellent opportunity to improve sales without improving products (covering problems, so to say). This is why WWDC was almost overshadowed by companies and people trying to feature their products in context of the Apple brand momentum. Around Moscone there were literally tons of people handing out flyers describing interesting up to weird services. There was a truck featuring a big advertisement for a flight simulator game that drove around Moscone all day all week – talk about saving the frakin environment. I even got approached by a 11 year old (or what) advertising his iPhone App Review club or something. And apart from that, there was the weirdest thing of them all: The iPorn Party; a desperate attempt to get developers into a strip club and (sucessfuly!) land articles for a small porn portal in the main Apple related media. The idea of a porn company trying to improve its perception by advertising in the context of WWDC – a conference geared around Mac Development – would have sounded very very awkward just two years ago.

(2) There was a tangible and visible change in the actual people attending WWDC. Sure, there were still the regular geeks with funny hats, witty (in a technical fashion) shirts and (not seldom) interesting beards. But more than ever before, there were two new types of attendees: Women and business people. I think two years ago I could count the attending women by hand. This year there were far more. As someone on Twitter wrote: This was the first time that, in a WWDC session, two girls were sitting next to each other. Probabilistic factors hadn’t allowed for such an event to happen in previous years. Not that I want to conclude anything from the looks of a person, but many of them were good looking too, and dressed in a way that, if you’d see them on a street, wouldn’t let you think they knew how to fire up XCode (please bear with me here, I’m not in any way misogynic).
Apart from this, there were lots of business people around. Wearing suits, sometimes even walking around with Thinkpads and Windows.
I conclude from this, that the iPhone halo has put the conference in a light, that will bring along fundamental changes. For next year I expect more business, and all in all a more heterogenous audience. The Mac & iPhone are strongly moving away from a niche or geek market to big money.

Summarizing just like shit attracts the flies money attracts the big business. Let’s hope they don’t corrupt the very nice Apple culture with their processes, calculations, economics and no fucking clue for interface design.

Yeah sure. So he doesn’t like Apple at all, but wants Microsoft to copy everything Apple is. Maybe it would be best for Microsoft to just buy Apple Hard- and Software and exchange the Apple for a Microsoft Logo. I guess that’d make Paul’s day.

via OSNews Thom Holwerda

I do think he’s right in that many developers will want to target both plattforms. In this case the Cappuccino Web Framework seems to be godsend. It doesn’t feature everything that Objective-C 2.0 and Cocoa on the iPhone offer, but it should seriously ease transitions. Actually, if I was 280 North, I’d try to add the Palm Pre Javascript extensions to Cappuccino as quickly as possible in order to attract that horde of iPhone developers on their gold rush.

I for one am happy that I can target Mac OS X, the iPhone and Web Applications with one framework (more or less) and one language (more or less). Sometimes it drives me crazy to jump between PHP/Symfony, Python/Django, JS/Prototype/Ext and Objective-C/Cocoa.

A dedicated website for the application is here, and the direct link to the iTunes Store Page can be found here.

Happiness is build around the concepts of Dolf Zillmann’s Mood Management Theory and further research in the area of mood modification through media. The basic and empirical verified (in many many studies) idea is that the exposure to funny, sad, frightening or suspenseful media can modify our mood in specific ways (that is, funny or sad, f.e.).
Build around this idea, Happiness aim is to enhance one’s mood in a very positive way through the exposure to nice imagery and the sound of laughing people. There’re different options which allow to optimize the usage behaviour.
While this is certainly not a complex application, it taught me nontheless a lot about the whole iTunes Application Store experience.
The App is really cheap (almost a bargain!), and I’d love if those of you, who own an iPhone or iPod touch, could try it and give some feedback, so I can enhance the app.

However, that’s only part of the story: The first time I remember seeing a Netbook was in 1999 or 2000. It was the Sony VAIO C1XD, a beautiful, small, Pentium machine running Windows 98, even featuring a Webcam. I immediately fell in love. The heavy price tag as well as a lack of real-world usage scenario kept me from buying it though. I’ve been checking ebay again and again in the following years, always tempted to buy one of those. That was difficult however, as their prices (even years old and technologically rather aged) hardly changed. Now, years later, the industry finally realized that there is a big market for small laptops, and finally I could buy the machine I always wanted to buy, at a price I always wanted to buy. I didn’t and don’t though. Because I already have a Macbook Pro and a iPhone.

What I wanted to say is: The iPhone is no Netbook, but the iPhone sufficiently substitutes many of the Netbooks features. And these areas, where the iPhone lacks a Keyboard or a Mouse, get covered by a regular laptop. So instead of having a mediocre Netbook for everything, I have a big laptop for all desktop and most mobile cases, and an iPhone for the rest. And for me, that’s the perfect setup.

(Albeit I’d give a cheap Apple Netbook running OSX a second thought. But not because I need it, rather because I always wanted it)