The reason is simple: the application purchase and installation process just got a million times easier, which for the first time brings it within reach of many users.

The old user journey of installing Mac software

1. Browse the Internet and find a new application’s website.
2. Decide that you want to install it.
3. Download a .dmg file somewhere on your hard drive.
4. Find and open the .dmg file.
5. Drag the .app file to your application folder (or follow the installer wizard process for some applications).
6. Run your application from the application folder.
7. Find how to buy the software from the application UI.
8. Go to the website that handles licensing.
9. Create an account on this website (not systematic, but frequent).
10. Provide your contact details, pay by credit card / paypal to the software developer.
11. Receive a serial number in an email.
12. Copy paste that serial number into the software.
13. Enjoy your app!
14. Optionally, right click on its icon in the dock and select keep in dock.

The new Mac App Store way

1. Browse the Mac App Store and find an application.
2. Decide to install it.
3. Type in your iTunes account password.
4. Watch as the icon seamlessly animates from the app store page to your dock and the application installs in seconds.
5. Click on the new app icon that is immediately visible on your dock.
6. Enjoy your app!

Key advantages of the Mac App Store for the user

Much faster and simpler process

We geeks often forget it, but everything that requires the user to explore the file system (via finder) will be beyond the skills of many users. The MAS (Mac App Store) follows the long Apple tradition (iTunes, iPhoto, iOS in general…) of abstracting the file system away, hiding it from the user fully.

A consistent install and purchase process

No need to learn how each software shop website works.

Cheaper apps making deciding to buy one easier

The price of applications is likely to get cheaper than it used to be, as demonstrated by Apple’s own Aperture which used to retail for $200, but is priced at only $80 on the MAS. The additional volume of sales generated from the MAS.

No need to trust a new third-party with money

It’s much easier to trust Apple Inc. that every little independant software shop.

No worries that installing a new app could mess up your system

Apps have to be approved by Apple first, so there is no (or very very little) risk that it can damage your system.

An easy app update process

Apps can be updated easily as soon as new versions are available, just like on your iPhone/iPod/iPad.

I believe the Mac app Store is removing many of the barriers that until now prevented a huge number of users from installing new applications. This is good news for users who will discover great apps and enjoy their Mac even more, and good news for the developers who will see their addressable market expand considerably.

As Johanna Kollmann (one of the organizers) has already done an excellent job providing an explanation of the concept and a summary of the day on johnnyholland.org, I’ll simply advise you go ahead and read her post first if you did not attend the event.

Leisa Reichelt, one of the roaming mentors of the days, provided her own review of the day’s efforts, kindly phrased as constructive advice. I was going to simply drop a comment on her post, but since I kept rambling and did not want to hijack her post, I’m writing my own thoughts here.

I deeply agree with Leisa’s key points. Most teams assumed that “the problem to solve” was fully formed in the brief, and only worked on a solution, without really thinking what actual issue they where trying to address. The lack of clear solution product statement / elevator pitch in many presentations was just a consequence of a lack of definition of the problem.

I must add that I am worried that the rushed process such an event imposes can give newcomers a wrong idea of what a serious design process is. Today, there has been understandably very little research, and no user testing (at least I did not notice any and none was mentioned). This is not remotely close to real user-centered design.

I do believe that such events can be fantastic introductions to what UX work is, butthere is a need to make much clearer to all that this is NOT the real thing, just like Model United Nations, while a great pedagogic tool, is not an accurate representation of what takes place at the United Nations assembly.

An exemple of this is the repeated used of the word “personas” to described the fake users that were created. While they succeeded in getting the team to focus on a problem, and thus lead to a real and interesting solution, these had nothing to do with ux personas. They were simply stereotypes made up on the spot by participants. But by calling them personas anyway and repeatedly, we undermine the work done by researchers who produce real, deep, research based personas, as some will think they just made these ones up too, and that they can be discarded as simply the researcher’s opinion.

These quibbles being shared, I remain impressed by the capacity of the organizers, their passion, commitment and super human capacity to to simply “make thing happen”.

Please do let me know  what you think in the comments, whether you think I have a point or that I am wildly off the mark.

Previously, iTunes media transfert was either a full sync, meaning you had first to put songs in a playlist then tell iTunes to sync it with the phone, or a full manual process, where you could drag and drop files, but would loose the power of using the sync options defined.

It is now possible to simply drag and drop songs from the iTunes list to the iPhone icon, which which prompt iTunes to immediately transfer these songs to your device.

iTunes 10 will list those songs under a new “Manually Added Songs”  group in the “Music” tab of its iPhone settings.

This new feature allow the best of both modes: full sync while still allowing immediate media transfer on demand. Sweet.

See it the new iPhone sync music settings screen on this screenshot.

PS. I discovered this by chance, and I can’t understand why Apples doesn’t announce such new features somewhere in their release notes.

Read the full post A reading mode for the web? on Flow Interactive’s Think blog

This is an in-depth look at the iPad user interface with guidelines and examples: what’s new, and what lessons were learned from theTablet PC concept and the iPhone’s  user interface.

If you think the iPad is just a bigger iPod, this presentation is for you.

View the slides on Slidshare (and make sure you read the notes!): Why the iPad UI matters, and how it differs from the Tablet PC, but also from the iPhone. 

The iPad is Apple’s Wii.

A massive share of the people offering their thoughts on the iPad compare it in term of technical features to today’s laptop, and find the iPad lacking. What they miss is that with the iPad, Apple is doing the same thing Nintendo did with the Wii, and I am not talking about making an unfortunate naming decision. For years, the video game industry plan was to make next year console more powerful in term of processor speed, with better graphics but similar controller and game mechanics. However, they were only addressing a single market of usual suspects who “play video games”. The Wii, which used to be codenamed “Revolution” for a reason, threw all this logic to the wind. It targeted a much larger and untaped audience made of people such as parents and older users who do not used to play video games. As a result of this decision, they created a new, more intuitive and fun way to control the games. But they also decided that processor and graphic capacities did not really matter, and released a console much weaker on those fronts that the competition, but also much cheaper. The Wii is the opposite of what the video game industry has been producing over the years, yet it sold roughly as much unit as both Xbox 360 and PS3 combined.

Computer are hard to use (really!)

Most of us do not realise how difficult to use our everyday computer really are. However, most of us also spend a good share of our days using our Mac or PC, and we are so well trained in using them that their complexity is not an issue for us anymore. I have the “privilege” to be the one who “is good with computers” in my family, meaning every time one of my relative is stuck, they ask for my help. It turns out they need my help quite a lot. My relative are just like yours, just like so many people out there. They are an untapped potential of users who do not use “computers”, or use them as little as they can, simply because they struggle to use it. Today’s computer are just too complex for them. They do no understand what all those folders are for, or can’t remember where they stored their last file. They do not want to spend their time “making windows faster”, installing drivers, defragmenting hard drive or fixing their computer. They are scared they might do a wrong operation and “break” their computer which is why they can be paralysed by the amount of features, menu items and preferences that are presented to them. They want it to “just work”. With the iPad, there are no such things as a file system to manage or drivers to install. Installing software takes only seconds merely require selecting the one you want to install, and clicking ok. This could not be more simple, and there is absolutely no way for the user to go wrong. Thanks to the way applications are sandboxed, one application simply can not mess up the other. This advantage in ease to use, especially compared to netbooks running windows or Linux, can not be overstated.

The iPad is not a WIMP

Roughly 30 years ago the Graphical User Interface revolutionised the way people used computer, making it much more easier to use than the command line interface that was the standard until then. Since that time, all the mainstream computer platforms have been declinations and improvements of the original ideas of the Windows, Icons, Menu and Pointer (WIMP) recipe. The iPad however has neither Windows, Icons, Menus or a Pointer. This alone should make it obvious that the iPad’s interface is a different beast altogether, in itself deserving a very close look, especially if like me you work in the field of designing digital User eXperiences. On the iPad, there are no windows to manage. There are no files to manage either. The traditional single permanent pointer is not there anymore, replaced by many possible simultaneous finger touches that exist only when you use them, and disappear immediately. This multi touch input provide a much better way to interact with content, replicating the real world experience we are already familiar with. The iPad, thanks to its larger size allowing more fingers to come into play, will go further than the iPhone to bring multitouch interactions to the masses. The multi touch experiences of the future have yet to be invented, and I find that incredibly exciting.

When App. stands for Appliance

With today’s computer, even with the most portable laptops, no matter what application you run, you are stuck with something that looks like a computer, with a keyboard and trackpad that are there even when you don’t need them: when you watch a movie on your laptop, you are not using half of it. Having to use a keyboard and a mouse/trackpad puts another distance between you and the content you are interacting with. There is simply no way to forget that you are actually using a computer. By contrast, the iPad’s hardware is pretty much just a screen, providing a clean slate (pun intended) for you application to turn the iPad into whatever you want. Each app open in full screen, and you can make it look like whatever you want including photo realistic Address Book, Calendar, Books, and so many more thing. Each app has the potential to turn you device into a different appliance. The App store is full of crazy idea that no one would have anticipated would be the features of a phone. I can’t wait to see what new things the iPad apps will bring.

A big iPod Touch?

Of course, most of this is not completely new: while many UI concepts are new and specially designed to accommodate the iPad larger screen (see an excellent UI overview here), the OS and the general ideas behind the iPad UI are not seen as very new, for the simple reason that Apple has been bringing those to the public since the introduction of the original iPhone, almost 3 years ago. Yet to dismiss the iPad as a bigger iPod touch is a mistake: the iPod Touch / iPhone and iPad have a lot in common of course, but the larger size of the iPad changes everything. Yes, size and scale matters.

It’s not pocketable!

Yes, at this size, it is too big to fit in a pocket, and as such is not as portable as an iPhone. This is by design, and I’m sure Apple will not mind continuing to sell iPhones. But have you ever found yourself using your phone at home or at work to do task you could have done on a “proper” computer nearby? You are not alone: most of the time spend on mobile devices is actually spent either at home or at work. A couple of reasons explains why the mobile wins: you can use it wherever you are, sitting more conformably than when using a laptop, you don’t have to wait for it to boot, and you can quickly do what you need with perfectly focused apps. The iPad is designed to improve precisely those experiences. And since this device was meant not to be portable, they made it much larger making it much more comfortable to read a book or browse the web.

When more is more

Technically, a tweet and a book are the same thing: just a succession of letters forming words to convey meaning. Yet I don’t think anyone will deny that a book can offer a depth that a tweet do not offer, which make it possible to handle a much bigger level of depth and complexity. While an iPhone app must really focus on small task given the small size of the display / input surface, the iPad has much more space to play with. Apple is releasing new versions of its word processor / page layout, spreadsheet, and presentation applications especially for the iPad, and the message couldn’t be clearer: the iPad is ready for large and powerful apps that could not have been handled by its smaller relatives.

But wait, the iPad is doomed!!! It does not have…

Multi task!

Despite what has been written times and times again the iPad OS technically supports multitask, and the iPhone has been doing it since day one, for example when it continue to send a heavy email when you switched to read a webpage. What the iPhone OS does not provide is a way for non-system application to run in the background. In effect, every time you press the home button or you receive a phone call, the application you were using quits. However good iPhone apps are designed to save their state when quitting, and to restore it when reopened, and in effect to the user it’s like the app never quitted. Keep in mind also that in 2007, the system resources were so limited that this was necessary to avoid turning your phone in a sluggish mess. The user interface implication of allowing concurrent app also bring a new layer of problem to solve: you need to manage “hide” on top of “quit”, and provide a way to switch between applications. Running too many apps at the same time has a very negative impact on performance and battery life, so how do you help uninformed users to avoid having too many open? The last thing you want is to force the user to spend time managing his running applications. Those are non-trivial design challenges that deserve attention, and I’m glad Apple is not rushing a bad implementation, but taking as much time as needed to provide a great solution, just like they did with copy and paste. But eventually, Apple will come up with such an implementation, and with the iPad and the next iPhones, the hardware will probably be able to handle two or more non-system app running at the same time. My guess is that this will appear in the next revision of iPhone OS, due around june. I do not think however that this has been a big issue hurting the sales of the iPhone.

A Camera!

Another “disappointment” is that the iPad does not have a camera. I do not find it personally to be an issue, as I got tired of the novelty of video calls after a couple of Skype calls on my laptop. I do think iChat on the iPad can have an audience. My guess (supported by the presence of UI code implying a camera is the iPad SDK) is that a camera was originally included, but was cut out in order to keep the price under the $500 psychological barrier. It will probably be added somewhere down the line, maybe next year.

Adobe Flash!

To me, not having flash is actually a feature! I even disabled it on my main laptop browser. The reason is simple: most Flash content on the web is more annoying that helping. “Skip intro” useless animation before a web site open. Blinking video adds everywhere, some with sound. I don’t want any of that, yet it consume vast amount of system resources on my Mac. Having those on the iPhone or iPad, with their much more limited system resources, would be a nightmare making everything sluggish and draining the battery really fast. There is the reason why the Mozilla team working on Firefox mobile also disabled it. Additionally, most of the Flash content I do care about can be better implemented with HTML 5’s <video> tag, or even better by a native iPhone app. I believe that most websites will do one or the other (or both, as YouTube as done). Another type of desirable flash content are the many games written in Flash, but they very often rely on keyboard presses, mouse over event and drag and drop, which do not translate easily to a touchscreen only interface. Just “running” the flash plugin would not solve these input issue, and those game would probably need to be rewritten. A sweet solution for me would be something like ClickToFlash ported on the iPhone: flash content is not loaded by default, but can be displayed on demand. But this would introduce an additional level of complexity that is contrary to Apple’s ethos, so I am pretty sure this will never happen.

Conclusion

If you’ve read it this far (than you!) it should be clear to you that I think the iPad has an incredible potential. It offer a brand new, easier, and more enjoyable way to accomplish most of our daily computer tasks that will make it a hit among people who never tough they would ever use a computer so much. In 2007, someone reacted to the iPhone by saying to Steve Jobs “Make the screen five inches by eight inches, and you’ll rule the world.” These happen to be the dimensions of the iPad, which is no coincidence. That person was Alan Kay, arguably the main force behind the invention of the GUI all those years ago. He might know a thing or two about computers. Remember also how Slashdot, the self-titled “news for nerds” site and king of the tech-savy blogs, first reacted to the iPod in 2001: “No wireless. Less space than a nomad. Lame.” The geeks weren’t impressed, but we all know what happened next.

I actually agree with many of Jude’s points:

1, 2 & 5) Typing is in some ways harder than it used to be when you were used to physical keys and T9 text-prediction.

3) The switch between portrait and landscape mode can be annoying, especially when lying down. There should at least be a preference to disable for in each app.

4) When the iPhone is off, it is off, and will not start itself up on time to wake yourself up as an alarm clock. Which also means it is totally off, not in some standby mode.

7) The battery life is not great: my iPhone 3GS last little more than a day in normal use, years ago I had a Nokia 3210 that lasted 4-5 days.

So the iPhone is not a great mobile phone, I would actually agree with that.
Many users who only need a simple basic mobile phone, would be better served by cheaper and less fragile devices, such as my old Nokia 3210.

But what surprised me in that post was that it was not mentioning what makes an iPhone so much more than a mobile phone.

The iPhone is not just a mobile phone

The iPhone is a mobile phone (calls, SMS), but that is not all.

It is a song jukebox (the iPod app).
It is a live TV (see (live UK TV).
It is a TV/VCR combo (the videos in the iPod app).
It is a photo album (the photo app, or Flickr’s app).
It is a pocket translator that speaks foreign words for me. (iSpeak serie).
It is a networked computer (mail, safari).
It is a photo camera.
it is a video camera with built-in editing facility.
It is a book that can display thousands of titles (Classics).
It is a map that always knows where I am and how to go where I want to go (Map app with GPS, Sat Nav apps ).
It is a game console (too many games to link!).

And all of this in the volume of a deck of cards.

For me, the small dose of usability that has been lost from simpler phones is much more than compensated by everything else that this device can do. Even in Star Trek, they didn’t foresee such advanced technology.

The iPhone is not perfect and there are tons of things than it could do better. But yes, for everything that it does, I do love my iPhone.

Sponsored categories ask for example how to provide a demonstration on how a sponsor’s product / API can be used. For example “Best BBC. com hack”, or “Best Lonely planet hack”. There are also general categories “Best use of WebApp/widget”, “Best hardware hack”, and the weirdly phrased “Best User Experience / Service Design”.

Sounds cool? Yeah, kind of. But to me such competitions, hackday or hackathon tend to encourage the worse of the typical developer mindset, which is often antinomic to delivering a good UX.

Developer are gods

Developers have advanced skills that allow them to give life to applications: before their work there was nothing, and once they are done, there is something that works. They have the ability, unlike graphic designer or UX people, to create a functioning application on their own. This god-like power on software should not be underestimated.

But the issue is that too often, developer think that the important issue, no, the only important issue, is one of functionality. So the first thing they do when starting a project is jumping on their code editor, and when they manage to have the key functionality part working, they think the application is mostly done, only lacking a superficial layer of polish.

UX is more a differentiating factor than functionality.

This is what this kind of hackaton encourage: the idea that the basic functionality is the most important thing. Well this can very well be true if you are curing diseases, but in the world of software, there is a very strong chance that a competitor proposes or will soon propose the same core functionality. What will really make one product successful over another is its user experience. And you simply can not create a good UX in a day or two.

A frequent developer misconception

This is what Alan Cooper describes in “The inmates are runing the Asylum”) as the “dancing bear” phenomenon, typical of a developer driven mindset: too much focus is on solving a functional problem (“making a bear dance”). No time is spent thinking how to make it dance better, or even why it should be made to dance at all.

This remind me of the time some developer complained about the Siteoverflow.com website, and despised it saying basically he could redo the full site in a weekend. I recommend you read the full reply from Stack Overflow’s Benjamin Pollack, it is well really worth it. The gist of it: there is more than meet the (developer’s) eyes, and by seeing only how to solve the basic functional problem, you ignore all the refinement that make the site actually enjoyable to use, and ultimately successful over its competitors.

Another good insight is Brent Simmons’s “Anatomy of a feature”, where he discusses the inclusion of the “Send to instapaper” command in his RSS reader NetNewsWire. This is another post that was written to placate to developer comments saying “Oh, it’s easy, just a quick http call. I could write a script to do it in like 20 seconds.”
Except implanting this feature involve making a very long list on hard decision on how precisely this feature should work. A menu item? An Icon? How / when does it syncs?…
Eventually, the devil is in the details of the interaction design which end up taking much much more time than solving the basic technical issue.

And neither of those two cases seems to be doing any real User Centered Design, so they risk building their product for themselves instead of for the actual target users. A proper UCD process would have lasted very much longer than the time it took the developer to solve the main technical issue. But it would also deliver a better product, that delight its users.¹

Boys will be boys, and developers will be developers.

Is it an issue that developers love to take part in hackathon, or like to code something just for fun?

Of course not.

Developers will always play around with code, basking in the wonderful pride provided by seeing your application “work”. Instant gratification!
Playing around with new functionalities is one of the best thing about being a developer and this can be a good way to learn new APIs, and simply coding is making them better coders.

Developers and their skills are absolutely necessary to the development of software. We all need them to be the best at what they do, and hackaday, or coding for fun can help with that.
Nonetheless, we need everybody, especially developers, to understand that this is not the way to create quality products.

As always, I’d love to get your feedback on this, especially if you are a developer (or have been in a previous life), so please let me know what you think!

If there was any doubt about the audience being developers, just counting the number of ladies would remove it. I estimate the ratio to be close to 1 woman for 15 guys, a very far cry from the approximate gender parity of UX crowds.

The session were mainly technical, full of info about APIs, (in-)compatibilities, standards etc. Some UX session were also present, but I have to say I was a bit disappointed by them. It’s not that they were not good, far from it actually, special props to Bryan Rieger with his incredibly clean, beautiful, and effective slides. It’s just that given my background in UX and the MSc I just finished, none of this was really news to me: I was simply not the intended audience.

Like any good event, #ota09 got me thinking on a couple of points, that will be the basis of a few blog post.

First up: Hackathons, developer’s conceptions, and how it negatively affect good UX

Zune are an interesting breed. The first one was just fugly (remember brown as *#&* and lime green?). The second one looked better, and I have to say I quite like the hardware design of the Zune HD. FINALLY some device with its own design personality, not another iPhone cheap look alike.

Reading the review, and watching the videos of the UI, it seems Microsoft’s team produced a beautiful UI, full of eye candy and animation. However, it presents a really glaring flaw.

the Zune HD new UI offers a nice way to quickly access favourites (or “picks”) or recently added media, straight from the start menu. iPod users traditionally need to have manually put their own smart playlists, and then dig down into music > playlist > to find them. This is definitely a good idea that Apple would be wise to take inspiration from.

Now let’s focus on the screen that will be displayed the most on a portable music player: the “now playing” screen. Here is photo, sorry I couldn’t find a better screenshot.

Take a good look at it. I’ll wait.

Image "courtesy" of PCmag

It doesn’t look bad at first glance. I won’t go into details and esthetics, probably largely a matter of personal taste, but there is a glaring omission on this screen.

Let’s see what the same screen looks like on an iPhone.

Oh, and BTW, Muse's new album rocks!

Do you see what the Zune UI is missing?

It does not have any controls! No way to directly play/pause, adjust volume or change track!
The one and only way to do that is to press a hardware button to open a new screen / menu with those features.

Such simple, obvious, and very frequent actions are hidden away!

When I read about this (on Ars), I just couldn’t believe it. I do not think it takes extensive user research to find out that controlling what’s playing it a frequent user need, yet Microsoft ‘s Zune UI team did not realize this.

Well, as far as I’m concerned, I would give up all the nice animations and background pictures for direct access to those elementary controls.

So the lesson of the day: all graphic work is pointless if you can’t figure out what the user needs to do, and prioritize access to those features accordingly.

By comparison, newer iPhone/iPod allow you to use all those control without even taking the device out of you pocket, thanks to their very handy and light remote built-in on their earphones.

On a side note, while Zune quality keeps improving, it still seems they are competing with last year’s iPods. An iPod touch is now much more than a portable media player, thanks to its App Store and the 60k + applications it offers. On the Zune, there are now plans for third party apps, and the few ones Microsoft themselves will offer will be ad-suported. Yes, first party apps with ads, this might be a first.

More than apps, devices keep pilling features, in a very tangible show of the much heralded “convergence”. Even the tiny iPod Nano record video now!
It seems clear to me than single purpose devices are a dead end. I can’t wait to see what the much rumored Apple tablet will look like, but you can be sure it will do more than just a web/eReader.