Anyways, there is a new dress code for Android. This dress code will make things simple and with its semi-open nature, it will ensure that makers of Android handsets and developers of Android apps have considerable freedom to alter the user interface (UI).
However, Apple’s iOS platform is less open, allowing developers to design apps as they see fit, provided Apple’s UI guidelines aren’t trampled in the process.
There is now a similarity between the two mobile platforms, but the difference still exists. Apple doesn’t have iOS hardware partners, who can re-imagine the basic device interface. After all, many would argue that having a number of hardware partners is for the best, like in case of Android, Google partners HTC and Samsung have done.
Google has started its openness act, but it has still restricted the freedom to some extent by noting that its hardware partners have to include the unmodified Holo theme on Android 4.0 devices, the native theme in Android 4.0 (a.k.a. Ice Cream Sandwich).
Google software engineer Adam Powell said in a blog post, “Before Android 4.0 the variance in system themes from device to device could make it difficult to design an app with a single predictable look and feel.” He continued, “We set out to improve this situation for the developer community in Ice Cream Sandwich and beyond.”
This means that now onwards, devices that ship with Android Market support will be required to include the Holo theme. Basically, every Android device will have it then, until someone like Amazon plans to come up with an Amazon App Store, instead of an Android Market. Thats possible in future.
But recently, Android Market hit the 400,000 mark, in the count for the app titles, according to Distimo. This will prevent Android partners to skip the Holo theme. The number will only increase.
Talking about the developers, it would mean that writing apps for Android 4.0 would be easier, as they can rely on a predictable look and feel even when there’s a custom skin. Why would it help? Mainly because it reduces the amount of testing necessary to ensure that an app will work with a non-standard theme, and it will help apps remain functional in the face of future theme revisions. So, it is definitely a time saver and a few complex hurdles are removed.
One question would still be lingering in the minds of the developers and users, that is, will this really help? The possibility of the same shares a thin line of difference with ‘no real change’. However, one will have to wait and watch the same.