4 ms·

Android 4 does use the GPU for some things, however scrolling performance is still nowhere near as good as it is on iOS. The "unmodified Halo theme" is referri

by dcurtis 15y ago

Android 4 does use the GPU for some things, however scrolling performance is still nowhere near as good as it is on iOS. The "unmodified Halo theme" is referring to the icons and interface elements included with the operating system that developers can use when building their apps. Google even said this: "We have no desire to restrict manufacturers from building their own themed experience across their devices." (http://android-developers.blogspot.com/2012/01/holo-everywhere.html http://android-developers.blogspot.com/2012/01/holo-everywhe...)

yesimahuman 15y ago
I guess that means my horrible cyan "design" on my Motorola Atrix (Gingerbread) isn't going anywhere..
there 15y ago
Your article complained about manufacturers implementing custom, poorly designed interface changes which make testing difficult. Google remedied this by telling manufacturers they cannot modify Halo, and so every app developer can use Halo and get the same result on every device. Google even said this: "We have no desire to restrict manufacturers from building their own themed experience across their devices." That is talking about a different theme called DeviceDefault. Why would any app developer use DeviceDefault instead of Holo when it would make testing difficult and give an inconsistent look to their app?
- deleted 15y ago
  [deleted]
edderly 15y ago
It's worth reading Diane Hackborne on this topic https://plus.google.com/105051985738280261832/posts/XAZ4CeVP6DC https://plus.google.com/105051985738280261832/posts/XAZ4CeVP...
mrich 15y ago
Have you actually used the Galaxy Nexus (which should be the only 4.0 phone) It has no lag/ stutter. The same goes for most of the dual-core Android phones.
- potatolicious 15y ago
  I've used the Galaxy Nexus, it very rarely stutters, but it's still laggy. Note the distinction - Android 4.0 can keep a consistently high framerate on the newest dual-core hardware, but there is still a noticeable delay between input and output. This is most noticeable when dragging things around - the output always trails your finger movement by just that much - not enough to appear extremely egregious, but enough that iOS still feels more responsive. Google has done great work, but they ain't done yet.
  - mrich 15y ago
    This may be the case, and I admit Android is still a little bit behind iOS in that regard. What I despise, however, is the article's tone, which tries to make it look like this minor difference is important to the user, and he will hate Android for it. I would guess the percentage of users disturbed by this is maybe 1%. There are so many other major differences between Android and iOS that are much more relevant to the user, like lock-in, choice of different handsets etc.
    - potatolicious 15y ago
      I strongly disagree with this sentiment. The "little things" is what has put Apple so far ahead of the competition in so many places. While other companies are content to reach the 90% product, Apple has consistently achieved the 99%, and consumers have answered with their wallets. The key to beating Apple, or even just matching Apple, is to deliver the same attention to detail, and things like touch lag is a major component of this. Think about the MacBook sleep indicator. It has a soft "breathing" rhythm modeled on the frequency of human breathing. How many users do you think are actively looking at the sleep indicator on their laptop? Yet it has become an iconic and beloved feature of the product. Many competitors have tried to clone the "sleeping light", yet none of them could even be arsed enough to get the feel right. Same goes for the "shines through metal" indicator lights on MacBooks webcams/battery indicators. Would a user consciously notice if they got rid of it? Probably not, but its presence lends a fit and finish that communicates quality. > "which tries to make it look like this minor difference is important to the user" That's just it though. It is important to the user, though you'd never know it if your only metric for measuring user happiness are conscious observations. Very few users can articulate "the time lag between input and action is too great" in those words - but I'm willing to bet 90% can feel it, and will fail to articulate it to a focus group or similar. The difference is magnified if the user is comparing the two products side by side. I've heard it expressed in many ways. It's "laggy" (which is the most accurate term for it), it's "not snappy", it's "slow" (which is inaccurate, but the layman generally doesn't know the distinction between speed and lag). Sometimes a user will feel it and can't articulate it at all! I'm willing to bet, if you could find someone who has never used either iOS or Android, and hand them one of each device, loaded with just a simple scroll list. Let them interact with it, and ask them something as simple as "which one felt better to use". Who do you think will win? One product has just won the entire contest by visceral reaction alone, before the conscious brain has even kicked in. Details matter. > "There are so many other major differences between Android and iOS that are much more relevant to the user, like lock-in, choice of different handsets etc." This is the RIM angle, and I'd have thought that by 2012 we'd have put this one to rest already. Competing on functionality and features doesn't win anything. "No wireless. Less space than a Nomad. Lame", anyone? The iPod, the iPhone, and hell, the MacBook all came out into a market where there already exist functionally superior products. Remember the guffaws when Steve marched on stage with an EDGE phone when the industry was already rolling out 3G? That sure put the kibosh on the iPhone launch, eh? This is the problem with most technical types - we think the decision matrix is 80% function 20% experience, but in reality it's the opposite. Apple has taken this realization and made hundreds of billions betting on it. The whole point I'm making is much better communicated in a great book: The Design of Everyday Things by Donald A. Norman. If you haven't read it, I highly recommend it. He's not a software or even electronics guy, but rather industrial design. In the book, he posits a thesis: that a product is perceived at three levels: visceral, behavioral, and reflective. We're talking about the visceral reaction here - the immediate, subconscious reaction a user gets when they interact with Android vs. iOS. The texture of the screen, the responsiveness of the UI, the reaction of elements to touch. Without locking down the visceral reaction, your product will never feel "right".
TeeWEE 15y ago
@dcurtis is right: In IOS (and Blackberry Cascades UI for example) the animation is done in another thread. For android its done in the UI thread. However in older other aspects android is by far superiour to API and functoinality compared to IOS.

by dcurtis 15y ago

yesimahuman 15y ago

I guess that means my horrible cyan "design" on my Motorola Atrix (Gingerbread) isn't going anywhere..

there 15y ago

Your article complained about manufacturers implementing custom, poorly designed interface changes which make testing difficult. Google remedied this by telling manufacturers they cannot modify Halo, and so every app developer can use Halo and get the same result on every device. Google even said this: "We have no desire to restrict manufacturers from building their own themed experience across their devices." That is talking about a different theme called DeviceDefault. Why would any app developer use DeviceDefault instead of Holo when it would make testing difficult and give an inconsistent look to their app?

deleted 15y ago
[deleted]

edderly 15y ago

It's worth reading Diane Hackborne on this topic https://plus.google.com/105051985738280261832/posts/XAZ4CeVP6DC https://plus.google.com/105051985738280261832/posts/XAZ4CeVP...

mrich 15y ago

Have you actually used the Galaxy Nexus (which should be the only 4.0 phone) It has no lag/ stutter. The same goes for most of the dual-core Android phones.

potatolicious 15y ago
I've used the Galaxy Nexus, it very rarely stutters, but it's still laggy. Note the distinction - Android 4.0 can keep a consistently high framerate on the newest dual-core hardware, but there is still a noticeable delay between input and output. This is most noticeable when dragging things around - the output always trails your finger movement by just that much - not enough to appear extremely egregious, but enough that iOS still feels more responsive. Google has done great work, but they ain't done yet.
- mrich 15y ago
  This may be the case, and I admit Android is still a little bit behind iOS in that regard. What I despise, however, is the article's tone, which tries to make it look like this minor difference is important to the user, and he will hate Android for it. I would guess the percentage of users disturbed by this is maybe 1%. There are so many other major differences between Android and iOS that are much more relevant to the user, like lock-in, choice of different handsets etc.
  - potatolicious 15y ago
    I strongly disagree with this sentiment. The "little things" is what has put Apple so far ahead of the competition in so many places. While other companies are content to reach the 90% product, Apple has consistently achieved the 99%, and consumers have answered with their wallets. The key to beating Apple, or even just matching Apple, is to deliver the same attention to detail, and things like touch lag is a major component of this. Think about the MacBook sleep indicator. It has a soft "breathing" rhythm modeled on the frequency of human breathing. How many users do you think are actively looking at the sleep indicator on their laptop? Yet it has become an iconic and beloved feature of the product. Many competitors have tried to clone the "sleeping light", yet none of them could even be arsed enough to get the feel right. Same goes for the "shines through metal" indicator lights on MacBooks webcams/battery indicators. Would a user consciously notice if they got rid of it? Probably not, but its presence lends a fit and finish that communicates quality. > "which tries to make it look like this minor difference is important to the user" That's just it though. It is important to the user, though you'd never know it if your only metric for measuring user happiness are conscious observations. Very few users can articulate "the time lag between input and action is too great" in those words - but I'm willing to bet 90% can feel it, and will fail to articulate it to a focus group or similar. The difference is magnified if the user is comparing the two products side by side. I've heard it expressed in many ways. It's "laggy" (which is the most accurate term for it), it's "not snappy", it's "slow" (which is inaccurate, but the layman generally doesn't know the distinction between speed and lag). Sometimes a user will feel it and can't articulate it at all! I'm willing to bet, if you could find someone who has never used either iOS or Android, and hand them one of each device, loaded with just a simple scroll list. Let them interact with it, and ask them something as simple as "which one felt better to use". Who do you think will win? One product has just won the entire contest by visceral reaction alone, before the conscious brain has even kicked in. Details matter. > "There are so many other major differences between Android and iOS that are much more relevant to the user, like lock-in, choice of different handsets etc." This is the RIM angle, and I'd have thought that by 2012 we'd have put this one to rest already. Competing on functionality and features doesn't win anything. "No wireless. Less space than a Nomad. Lame", anyone? The iPod, the iPhone, and hell, the MacBook all came out into a market where there already exist functionally superior products. Remember the guffaws when Steve marched on stage with an EDGE phone when the industry was already rolling out 3G? That sure put the kibosh on the iPhone launch, eh? This is the problem with most technical types - we think the decision matrix is 80% function 20% experience, but in reality it's the opposite. Apple has taken this realization and made hundreds of billions betting on it. The whole point I'm making is much better communicated in a great book: The Design of Everyday Things by Donald A. Norman. If you haven't read it, I highly recommend it. He's not a software or even electronics guy, but rather industrial design. In the book, he posits a thesis: that a product is perceived at three levels: visceral, behavioral, and reflective. We're talking about the visceral reaction here - the immediate, subconscious reaction a user gets when they interact with Android vs. iOS. The texture of the screen, the responsiveness of the UI, the reaction of elements to touch. Without locking down the visceral reaction, your product will never feel "right".

TeeWEE 15y ago

@dcurtis is right: In IOS (and Blackberry Cascades UI for example) the animation is done in another thread. For android its done in the UI thread. However in older other aspects android is by far superiour to API and functoinality compared to IOS.