What Can Google Learn from Apple by KLP (5.0)?

The post about what Apple could learn from Google also made me think of the reverse.

iOS's main advantages are smoothness and refinedness of the experience. So what could Google learn to improve upon what it has?

1. Smoothness

iOS is very smooth, often more so than Android. While Android is not laggy per say on most high end devices, low end devices struggle. Currently Android just implements orders in first come first serve fashion. Instead Google could prioritize certain commands coming through and maybe reserve a little CPU cycles for the UI thread. The rumored low level graphics optimizations in 4.3 will help too.

2. Battery Life

iOS gets good battery life by strictly managing resources, notifications, and how much apps can run in the background. Devs for Android often implement inefficient real-time notifications systems even though Google has its own cloud messaging system that is more battery efficient. Google could restrict the polling intervals of apps not using the GCM system unless the user explicitly exempts the app. That would create a powerful incentive for devs to go with GCM. Android also has a problem with apps running in the background longer than they should. If an app runs in the bg for more than a defined period of time after the user has dismissed it from the multi-tasking menu, Android should alert the user and give the option to do nothing once, do nothing permanently, kill it once, or kill after X amount of time in the future. Google also needs to find a way to clamp down on wake locks.

3. Media Sharing

Apple really nailed it with Air Play. All the iDevices, Macs, and Apple TV worked with it easily. Google almost nailed it with Miracast but fell flat because only the Nexus 4 supported it. Google must update all their devices to harness Miracast (including the Chromebooks) and leverage the OHA commitments to force companies to make their devices ship with Miracast and no proprietary blocks like All Share.

4. App Store Curation

Apple's ability to reject apps does force devs to design better apps and reduces malware. Google should go that route too, although not to the extent of Apple. Pre test apps manually to check for malware, spyware, copyright violations, scams, and poorly designed apps. If an app does not meet Holo standards, the dev must explain why and the app should get rejected if the design is crap and the dev can't explain why it's necessary.

5. Unified Design

When Google updates its apps to a new design, it does it piecemeal. For example, Play Books and Music got updated to Card UI but Play Movies got left in the cold. And Play Magazines still hasn't arrived on Chrome OS. Google Maps is yet to receive its update. Google must coordinate its releases.

6. Web App Support

Ironically, iOS supports web apps better than Android does. An iOS bookmark on the homescreen launches its own broswer window with the url bar removed making it a full screen app like experience. Google should do the same for Chrome and eliminate lag. IMO, it should scroll first, load what's viewable at the moment and load anything else last. Loading top to bottom is inefficient for usage.

7. Tag System

Apple introduced the tagging system for its file manager and I've been praying for this forever. Tagging is much superior to a folder system. Instead of navigating a hierarchy, There could be a straight up list of tags and multiple tags could be checked, which is equivalent to viewing files in multiple folders at once and having a simpler navigation system.

8. Flatter and consistent icons!

iOS actually has flatter home screen icons than Android! Google should flatten out all its icons in the Chrome OS style and create a consistent design language for icons in the future.