azrienoch · Jan 4, 2012 at 10:00 am

Holo Theme Compatibility Standard on Android ICS Explained

Adam Powell explained on the Android Developers Blog how to maintain a consistent look on Ice Cream Sandwich between your apps and the general user interface with a line or two of code.  And he explains the improvements in ICS to streamline theme porting.  The goal here is design consistency wherever possible within a device interface.

He explains that all devices running Android 4.0+ with the Android Market installed will necessarily have the Holo theme installed.  That doesn’t mean there will be only one look to ICS devices.  It means that all have these streamlining improvements, which are formal separation of theme families in the manifest.  You can call on the Holo theme, or DeviceDefault theme, which is the theme you (or a manufacturer looking to differentiate the look of their devices from other manufacturers’ devices) create.  Powell says, “Formally separating these theme families will also make future merges easier for manufacturers updating to a new platform version, helping more devices update more quickly.”

The neat thing about ICS forcing the availability of the Holo theme is that that app developers may be certain they maintain the look of their apps across device manufacturers by using the Holo theme.  Or, of course, you can choose to make your app consistent with the rest of the system by using DeviceDefault.  Lastly, Powell covers supporting themes for your app in older versions of Android using the resource system.   “Using Android’s resource system you can define themes for your app that are selected automatically based on the platform version of the device it’s running on.”

But not everyone thinks the added functionality and choice that comes with this change is a good idea. XDA Recognized Developer and Senior Moderator Chainfire said on Twitter, “This change breaks things. If it were made in a non-breaking manner, I would agree.” Chainfire wrote a post on his own blog explaining how to theme an app across Android versions to help developers with whatever the Holo compatibility standard breaks.

What do you think? Let us know in the comments.

Via: Engadget
Source: Android Developers Blog, Chainfire[dev~blog]


_________
Want something on the XDA Portal? Send us a tip!
Emil Kako · Jan 31, 2015 at 02:59 pm · 2 comments

Do You Prefer Physical or on Screen Buttons?

More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.

DISCUSS
Pulser_G2 · Jan 31, 2015 at 02:08 pm · no comments

New AOSP Branch Details Potential Build System Upgrades?

While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...

XDA NEWS
GermainZ · Jan 30, 2015 at 09:29 pm · 1 comment

Send Links to Any Nearby Device with CaastMe

There already are many solutions on the Google Play store if you want to send a link to one of your devices -- but what if you wanted to do it quickly without having to install any software or logging in to a website on the recipient end? Most apps require you to do either or both, which can be a hassle (or even a security risk) in some cases. Luckily, XDA Forum Member wyemun has developed CaastMe. Inspired by...

XDA NEWS