It certainly looks like Apple has cooked the goose that lays the golden eggs for dinner.

So, what is this alternative platform, exactly?

I mean, you don’t want users to have to jailbreak their iDevices to be able to install the next big serendipity app, right?

Let’s take one step back.

In the blue corner, we have native frameworks and languages. These are vastly different from platform to platform – in other words, once you’ve finished coding an iPhone application, you still have to code a version for Android from scratch, as well as a version for Blackberry, a version for Windows Mobile, and every single update you release, has to be ported to all these platforms.

In the red corner, we have good old HTML5, CSS3 and Javascript. It works the same in all browsers on all devices, with minimal styling adjustments between different platforms. In other words, a mobile web app is easier to build than a traditional desktop website.

This is mainly due to the fact that, on mobile, there is no equivalent to Internet Explorer version 6, 7 and 8. Hallelujah!.

The main trade-off here is native app styling, which is quite design-heavy, and has had a lot of thought and development put into it.

And here jQuery Mobile provides us with a true Silver Bullet.

The jQuery legacy

jQuery, self-branded as the write less, do more javascript library, has all but re-invented Javascript in the past six years. Based on, and improving on a discontinued library called Behaviour, jQuery treats Javascript development as a bag of functions tied to HTML elements. This results in a much more organic development paradigm for the web.

This all sounds pretty technical, but all you need to know is, once you’re used to jQuery, it makes previously complicated things very simple. In a very big way.

jQuery goes mobile

In August 2010, jQuery announced an alpha version of their new library, jQuery Mobile.

Everything jQuery does for the desktop also applies to mobile, so what does jQuery mobile add to the mix?

Styling and behaviour. With some Javascript and CSS magic, jQuery Mobile turns this:

into this:

without any work on the developer’s part.

Pretty nifty eh?

In the Interim …

While the app store is still alive and well, HTML5, CSS3 and jQuery Mobile can be used in conjunction with platforms like Phonegap or Appcelerator Titanium to actually compile HTML5/jQuery apps down to native apps on most of the main mobile platforms.

Hopefully, before too long, one of these will happen:

• Someone will start an alternative, hugely adopted HTML5 app store (quite likely)
• Apple will come to their senses and try and save the app store by including HTML5 apps (less likely)
• The entire app store paradigm will die, and people will install apps from a variety of third party providers (not very likely at all)

So … while we keep on building HTML5 apps and mincing them into apps through Phonegap, won’t someone please go ahead and start up an HTML5 app store, please? (and make it hugely popular, of course … )

It was BBH Labs’ logo project back in April 2009, where they got 1,700 logo submissions and chose one, that got us fired up about including the public in the creative process. Since then we’ve learnt a thing or two from using the crowdSpring platform and did our very own logo experiment, where we got ordinary people to design us an R, an A or a K without them knowing what it was for  (using Amazon’s Mechanical Turk platform).

Now we’re taking it a step further: a never-ending RAAK logo project that integrates individual letter submissions into a perpetually changing logo made by (hopefully)  hundreds of people.

A company for everybody – A funny take on corporate logo design

We were inspired by designer Phil Seddon’s enthusiastic feedback on our initial branding experiment. So this time, we are setting restrictions as to what people can do. After many discussions about grid patterns and freestyle, Phil has created a framework for design that we think will integrate submissions in our new website look and feel.

Still, if an identity is about making a fancy logo, then we’ll probably fail. But if branding is about

• 1. making you stand out
• 2. making people remember you
• 3. communicating the core values of the business

then we’re doing quite ok.

We want our brand to reflect what we’re about:

open, social, digital, participatory, creative and constantly changing.

So this branding exercise is as much about the process of open collaboration as about the result.

And all the designs will sit in our Logo Archive, with links to the URL of choice of their creators.

You can find more practical info about how it all works and submit your design on the Logo Project page.

PS: We reserve the right to delete really egregious designs.

And that’s the whole point.

In the retail and service sector, there’s a well-known, yet unexpected way in which new customers are turned into loyal customers. It works as follows:

• A customer has a complaint. They see someone at customer support.
• The person at customer support solves their problem as well as possible, but above all, treat them with the highest of respect and dignity. The customer support officer needs to be a senior employee with advanced people’s skills.
• The customer leaves, not only with their problem solved, but with an unbreakable mental association between your business and the person who treated them so well. This instantly turns them into a loyal customer. They feel that they have seen the guts of your business, and not just the carefully manicured face. And they liked it.

How does this apply to websites?

Error message copy

When something goes wrong, like your website’s database server crashing, your pages getting corrupted, or even just when the user forgets to fill out a required field in a form, they are put in a situation where they see something different than the carefully designed front end of your website.

They see some kind of error message. How do these error messages treat them?

• Error message should not contain detailed technical information (or some cryptic phrase) that the developer used to debug the site, none of which makes any sense to the user. This is intuitively wrong, but so often the case. This is what happens if no copy is written for error messages, and it’s left up to the developer.
• Error messages could be funny (do resist the temptation to crack an in-joke, though).
• If at all possible error messages should go as far as providing an alternative way of leading the user to that which they have looked for in the first place. This is ideal, and this is what every error message should strive to achieve.

Error Message Design

Error messages should stand out (maybe even jump out), especially in the case where the user is required to fix some input errors (like on html forms). It’s not necessary to make it too ugly or out of step with the rest of the design, but do make it the most obvious item on the page.

Crowdsourcing is a reality that won’t go away just yet and instinctively we’ve always leant towards to the first group, but divisive issues need to be tried and tested.
We already used crowdsourcing techniques very succesfully in our RAAK logo experiment, but that project was of course of a more personal, a more creative nature.
So when we got the chance to apply the concept on a commercial project, with a real client, we jumped at it.
And this is what we learnt.

The job was to design a website and a brand identity for a start-up consultancy agency called Consultifi. Because of our plug-in model, we don’t work with in-house designers and normally we would tap into our network and instruct the most suitable designer for the job. But this time we decided use the Crowdspring service, boasting more than 45,000 designers.

After a good 10 days, we ended up with no less than 218 entries. Some of them were variants on the same theme or re-workings, but we did have about 120 unique designs. Not bad for an unglamorous, serious business consultancy company.
The client was happy and we thought it was quite a success, so below are a few things we learnt from our experience.

* Consider paying more
We analysed the mean and average of the budgets of similar concepts. We decided to stretch our budget a bit. Because by doing so, we would sit in the top 5 of ‘logo and stationery’ projects and not amongst those other $500 briefs.
Also, we do believe in the motto “you get what you pay for”, so by increasing the amount we were hoping to reach out to better designers. Crowdspring says their stats confirm that: the more you pay, the more entries you get.
But of course, more doesn’t necessarily mean better.

* Include things you don’t want in your brief
Saying that the brief is important is stating the obvious, but I was surprised to find how few people include what they don’t want.
Creatives will only send in a design if they think they have a chance of winning. Remember: they see this as a competition. They’re up against 45,000 other designers. So the more doubts you can take away from them, the more likely it is they will have a shot at your brief. If you don’t want black-and-white, spell it out from the start. If you don’t want capital letters, tell them.
The brief for a boring immigration law job did just that and despite the relatively low budget, they got over 200 entries.

But won’t that close off certain routes, I hear you think? Nah.
Even though we briefed the creatives to create a logotype and ignore a non-text logo, some of them still sent one in. And even though we asked them to avoid the word ‘consultifi’ in all lowercase, some still used it.
If creatives feel strong about their idea, they will go off-brief. I’ve experienced this with music video directors, with graphic designers,…: if they think it works, they will try and convince you.
In this project, one of the designers even wrote a long email about why he thought we were wrong.
You can’t always predict what will work and what not, so we did consider some of these entries.

* Set aside enough time for feedback
On that immigration law job I mentioned above, the client also gave lots of feedback on each design. Another a reason of the quality of their entries, I think.
Crowdspring recommends you give ratings. One, because it’s only fair to the designers and two, because it will improve the designs. Other designers go and read your feedback on other entries and learn what you want and -again- what you don’t want.
As a comparison: a more creative, exciting project (for a media agency) with a similar budget only got 60-odd entries. But they did stop rating and giving feedback after a few days.

I found the rating system quite hard to manage, because a 3-star rating in the beginning might only have been a 2-star later on, once we got better entries.
But the feedback opportunity is very useful. It does give you the chance to finetune designs directly with creatives. And it does make the process more human.

* Don’t end your project on a Monday
Simply because there’s a chance you will receive a massive amount of entries in the last few days. In our case, a good 40% of the entries only came through in the last day. Not sure if this is because creatives fear being copied or simply because deadlines are there to be pushed.
But it does leave you with little time for feedback. Especially if those last days are a Saturday and Sunday and you don’t want to spend that time rating almost 100 designs.

* Be prepared to make quick decisions at the end
Especially if you work for a client. We sort of missed that you’re meant to make a decision within 7 days. And we hadn’t anticipated our client going on holiday. We were open about it and told the creatives, but then realised Crowdspring’s terms state that they have the right to chose a winner on your behalf if you take too long. Admittedly, when we contacted them, they got back to us really quickly, assuring us that we were doing the right things. So I’m not sure if they ever apply that power.
From a functionality point of view, Crowdspring could make the decision-step a little bit easier by adding a shortlist functionality. That way you can compare all your ‘shortlisted’ designs on one page; and share that page with your client.

* Buy the URL from the company you’re working for
A lesson we learnt the hard way. While we were running the project, someone bought the dot-com and dot-net urls for the company and then tried to sell it to us.

Is the Consultifi identity the best logo since the Swoosh? Probably not.
Will we use it again? Probably, yes.
Is it a replacement for design agencies? I doubt it very much. I would think that developing a brand identity that really makes a difference does benefit from a more traditional, in-depth (and thus more expensive) approach.
But it does offer a good opportunity for smaller companies or start-ups, who get the chance of getting a very decent design done for a very decent price.
And for creatives from all over the world (our ‘winner’ alexe is from Romania) to be exposed to briefs.

So it’s definitely a force to be reckoned with.

Why?!?

We had a challenge, you see.
We needed to get RAAK up and running as soon as possible. After we finished our inaugural CanEUhearme project, we had new jobs coming in. And jobs require setting up a proper company. And proper companies require a proper logo.
But we couldn’t wait a few weeks/months on developing a full brand identity and spend lots of time (and money) on a full website design. We needed to get going now. So we decided to get a little creative.
Rather than tap into our network of designers or crowd-source amongst the design community (like BBH Labs did when they started up), we decided to go one step further. We would plug into the crowds big-time.

How did we do it?
Inspired by Aaron Koblin’s Sheep Market project, we got interested in experimenting with Amazon’s Mechanical Turk in some shape or form. For those who don’t know Mechanical Turk: it’s a website where ‘Requesters’ post little tasks that are more suitable to be done by humans rather than by a computer. ‘Workers’ from all over the world then choose and execute these jobs at the fee the Requester is prepared to pay. Typical tasks range from doing online surveys to transcribing a little audio excerpt. Generally quite mundane stuff.

For this logo experiment we posted a task on MT, asking ‘Workers’ to design one letter: an R, an A or a K. Just one. We’d pay 1 dollar. Which, we found out, is not a bad amount of money on Mechanical Turk. And we didn’t tell the Workers what this was for.

The first letter, a cute little ‘A’, came in a mere 15 minutes after we published the task. We were shocked and exhilarated. 4 hours later, we had our 40 letters. Not one of the ‘designers’ asked us what this was about.
The designs ranged from the ridiculous to the cute. From the blatantly opportunistic to the not-that-bad. 10 were not usable for copyright, technical,… reasons.

12►

More questions
Is this a diss at designers? That they’re all useless? Not at all.
Is it meant to start a discussion about the relevance of brand identity? And the validity of an all-encompassing, everlasting logo? Sure, go ahead.
Is it ugly? From a design point of view, quite possibly. But that’s not really the point. Put these designs next to each other, add the element of randomness and you have a crowd-sourced, ever-changing mash-up of a logo, designed by 30 non-designers. How beautiful is that?

But above all, it’s our little ode to creative problem solving.
As everybody is talking about new ways of collaborative thinking, social media and crowd-sourcing, this was a good moment to experiment with the concept.
Also, as a new company, we’d like to be known for turning theory into practice in a creative way. And this was the most practical creative solution to get a relevant logo.

Anyway, we have another 10 dollars left on our Mechanical Turk account, so if you’re a ‘designer’ and would like to take part in this experiment, email us your R, A or K. Once we have 10 designs we like (we’re gonna be more strict now), we’ll set up a new Mechanical Turk task and tell you how to claim your dollar.

After that we’ll try and make a Mechanical Turk version of our ‘mechanical musical logo’, which you can admire in our little video. If you feel inspired, let us know.