Matias Duarte on the philosophy of Ice Cream Sandwich
thisismynext.com
thisismynext.com
1. Unlike Apple, which apparently eschews formal user research, Google relied on "ethnographic research" to shape Android 4.0.
2. In between Apple's hyper-realistic UI and Microsoft's Spartan aesthetic, Google is trying to find a middle ground in Android 4.0 that facilitates new approaches and new experiences.
From the screenshots alone, it's hard to tell what it actually will be like to use Android 4.0. But it's great to see that Google is thinking so deeply about user experience.
Matias should be replaced ASAP and the weird fascination with black/dark themes should be tossed into the trash.
But the visual stuff is almost beside the point. I've been an Android user for a couple of years now, and the sense I always got was that the OS was very engineer-driven, with plenty of interesting features piled on, but no real sense of user experience. Duarte is clearly bringing a lot of focus on UX, by optimizing real usage patterns, making them fast and delightful.
I'm actually pleasantly surprised at where Android is going.
http://arstechnica.com/apple/reviews/2011/07/mac-os-x-10-7.a... http://pttrns.com/woodenshelfs http://pttrns.com/profiles#/detail/5e8603b7b0c551b85fcade3d1... http://pttrns.com/calculators#/detail/697d4e1cf6b7561bffcbbf... http://pttrns.com/widgets#/detail/4f83d8375a7f0a8a079dac5dd1... http://pttrns.com/widgets#/detail/6b5f0e73657ddaca447f84f73c...
As a rule, Apple minimizes these kinds of things in the core interface and often moves quickly to reduce them as new features become common knowledge. For example, the "dock" in the original iPhone looked like a speaker grill - it was probably a useful convention to denote to people that had never used OSX that it was a special section at the bottom of the phone/screen. Now it's a glassy reflective surface that subtly denotes the dock area and nicely borders the screen (much more subtly than the ICS dock, IMO). The scrollbars in OSX were once colorful and rounded, but steadily and gradually became flatter, grayer, and then basically invisible. I wouldn't be surprised if the now prevalent "fabric" pattern sees a similar fate.
Apple tends to make the metaphors glaringly obvious and keep them around in a certain class of very simple apps (the compass and calculator fall under this). It's funny that Duarte mentioned wood because Apple nerds have been arguing about the wood trim in Garageband (a spinoff from the sleek, German designed Logic app) since it launched. For power users, these things are a stupid distraction, but for the %90 of the population that is boggled by the idea of using a completely new class of software, they denote that this is fun, easy-to-use software. Google, who've made plenty of great products that have gone relatively unused, could probably learn a few things here.
There's a certain logic to the anti-skeutomorph thing, but it gets weird when it leads to dismissing Apple offhandedly. Mastery of these metaphors is a good part of the reason Apple are where they are today. It's amazing how consistent these textures, gestures and animations are across three platforms (and how smoothly they reached this point) while the other platforms are having identity crises.
I should add that I'm enormously tempted to get the Galaxy Nexus, so please take this as pro-Apple, not anti-Google.
I definitely think this idea has began to take a life of its own so to speak. I've read that Apple doesn't do Usability testing, doesn't do market research or user research. All of the points can be summed up with the "Apple knows best" idea. But, I'm sure Apple does user research - just not with a consultancy, or by asking users what they want. They focus on users' behaviour and their needs and incorporate it into their vision.
I don't think Google's core approach this time around is that much different from (what I presume is) Apple's approach. Google is using their ethnographic research to figure out what users do and what users need. I'd wager that Apple's own 'research' has focused on that all along.
* Enforcing a minimum hardware level, eg opengl es2 acceleration (eg no more cheap&slow androids that do the brand no favours) * Making it so that software updates cannot by stymied by hardware makers and carriers any more, so that as soon as google makes a new version, anyone can update to it without needing to root their device.
Are these true does anyone know?
Example: samsung wrote their own camera app. For reasons that are clear only to them, it refuses to work (literally, it pops up a message box and exits) if the battery charge is less than 15%. I'm sure they thought they were "conserving" battery (because clearly they know better than me how I want to spend my battery energy). But of course the real effect is that this is a $250 phone that won't take pictures in the evening. And this is routine in the market, Samsung is hardly the only offender. That's the disaster Google is hoping to avoid.
I thought Honeycomb was garish and the futuristicity forced. This tones it down quite a bit, but also moves away from Apple's kitschy skeuomorphism. I like it.
I also really like the new typeface.
Optimize your fonts and visual style all day long but at the end of the day the magic of the OS is dispelled if the OS doesn't respond to input properly. Jellybean I guess...
The Galaxy S2 is perfectly smooth. I guess it's the combination of the multithreaded garbage collector that came with 2.3, the dual core processor, and a very fine Android implementation from Samsung that solved the problem.
I also think that Android does benefit a lot from every MB additional RAM, because it gives both the application scheduler and the garbage collector more room to manage app lifecycles.
That's an interesting point of view.
All wood behind one arrow.
Yeah, it's not their general strategy. They are a software company commoditising hardware etc etc. But cannibalising that strategy could really make Android as great a product as Google Search.
Imagine.
You get the effect you want already, there's been a number of "official Google phones": the G1, the Nexus One, the Nexus S, and soon the Galaxy Nexus. These are Google-only, no-crapware phones, designed to showcase the newest Android offerings in the best light.
With iOS, there's only the one blessed option. You get one new phone a year. If it's a feature-bump like the 3GS or 4S, then that's what you get.
With Android, you not only get the Google-branded Official Phones, but you also get an entire ecosystem of devices to suit any taste. Want a hardware keyboard? You got it. 4.5-inch screens too big for you? Not a problem, plenty of options.
Can someone explain why? I'm not a mobile developer.
(Android digs being cluttered and confusing, Apple digs being kitschy and fake. And I’m not happy about the direction each OS is going.)
Its not just a checkbox for "yep, does multitasking", but how that is presented to the user. The "card" metaphor is very different than iOS "double click home, show row of icons"
The competition between the mobile OS is driving innovation and movement toward better design patterns that will be common between them. Notifications is a good example of something moving that way already and how iOS has copied notifications that are similar to Android, but also more so webOS.
I'm not sure whether the restriction is design-driven or business-driven (or both). It may just be an expression of Apple's preference for minimizing options and customizations. Alternatively, it might be that Apple wants to control the sharing menu "real estate" and require Google, Facebook and others to make individual deals to get a spot. Twitter might know (since they should have first-hand experience with the integration interface).