5 ms·

I had to scroll back up while reading this to see how old it was. The bug linked to is now closed, and the interview is from last year. Android 4 does use the

by there 15y ago

I had to scroll back up while reading this to see how old it was. The bug linked to is now closed, and the interview is from last year. Android 4 does use the GPU for more GUI operations and Google has mandated that 3rd parties must not modify the default theme (http://www.thevarguy.com/2012/01/06/google-imposing-gui-restrictions-on-android-4-0-devices/ http://www.thevarguy.com/2012/01/06/google-imposing-gui-rest...).

Xuzz 15y ago
That's not completely true. They can't (feels weird to say "can't" and "mandate" for an open source project) now replace the Google UI, but they certainly can add their own modifications. (And that's only on 1% of devices, too, running Android 4.0.) Also, while the GPU is now used to accelerate the UI, it is still simply not as smooth. The single-core Nokia Lumia 800 with Windows Phone is noticeably smoother at scrolling than my top-of-the-line Galaxy Nexus was. I'm excited for where Google is going with Android, but it's still not quite there yet.
- there 15y ago
  They can't (feels weird to say "can't" and "mandate" for an open source project) Open source isn't relevant here because that mandate is for any vendor wanting to distribute Google's proprietary apps (Market, Maps, Gmail, Google account sync, Face unlock, etc.) with their device. Every carrier and hardware vendor except Amazon falls into that category and is going to have to do whatever Google says to continue licensing those apps. Yes, they can continue making their own themes, but unless app developers specifically choose to use it with DeviceDefault, those apps will use the unmodified Halo theme which must now look the same on every device.
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.
huggyface 15y ago
At risk of being called on an Ad Hominem, the moment I saw this was from Dustin Curtis I completely discounted everything he has to say: He's trying to follow the path laid by Gruber and Arment, building web credibility on the back of endlessly criticizing Android while holding iOS as the beaken. He has little credible knowledge about Android. Has never said anything interesting or insightful about Android. Why does he bother with Android? I don't get it. There is a massive documented history of discussions with Android engineers (not some second-hand claim of a discussion that reveals absolutely nothing) where they argue their case regarding GUI compromises. This blog entry adds less than nothing because it simply tosses more effluence in the information stream.

by there 15y ago

Xuzz 15y ago

That's not completely true. They can't (feels weird to say "can't" and "mandate" for an open source project) now replace the Google UI, but they certainly can add their own modifications. (And that's only on 1% of devices, too, running Android 4.0.) Also, while the GPU is now used to accelerate the UI, it is still simply not as smooth. The single-core Nokia Lumia 800 with Windows Phone is noticeably smoother at scrolling than my top-of-the-line Galaxy Nexus was. I'm excited for where Google is going with Android, but it's still not quite there yet.

there 15y ago
They can't (feels weird to say "can't" and "mandate" for an open source project) Open source isn't relevant here because that mandate is for any vendor wanting to distribute Google's proprietary apps (Market, Maps, Gmail, Google account sync, Face unlock, etc.) with their device. Every carrier and hardware vendor except Amazon falls into that category and is going to have to do whatever Google says to continue licensing those apps. Yes, they can continue making their own themes, but unless app developers specifically choose to use it with DeviceDefault, those apps will use the unmodified Halo theme which must now look the same on every device.

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.

huggyface 15y ago

At risk of being called on an Ad Hominem, the moment I saw this was from Dustin Curtis I completely discounted everything he has to say: He's trying to follow the path laid by Gruber and Arment, building web credibility on the back of endlessly criticizing Android while holding iOS as the beaken. He has little credible knowledge about Android. Has never said anything interesting or insightful about Android. Why does he bother with Android? I don't get it. There is a massive documented history of discussions with Android engineers (not some second-hand claim of a discussion that reveals absolutely nothing) where they argue their case regarding GUI compromises. This blog entry adds less than nothing because it simply tosses more effluence in the information stream.