Print 16 comment(s) - last by cruisin3style.. on Oct 8 at 3:10 PM


Google illustrates the single pane/multi-pane approach of condensing pop out selections into screen transitions when switching from tablet to smart phone.  (Source: Google)

The action bar will now be on smart phones in pint size form, so beware.  (Source: Google)
Android devs are urged to make their tablets apps friendly for small screens

Google Inc. (GOOG) is giving developers their first of the next version of Android, Ice Cream Sandwich.  Ice Cream Sandwich will merge together the tablet and smartphone branches of Android.  This is a drastic departure from the current situation where Android tablets are powered by the closed-source Android 3.0 "Honeycomb" (latest version 3.2), while smartphones are powered by a separate open source, Android 2.3.x "Gingerbread".

Ice Cream Sandwich is set to release in October or November 2011, according to Google's Eric Schmidt.  When that release occurs, Google will become only the second major smartphone and tablet maker to use a single source to support both tablets and smart phones.

That creates both a unique opportunity and a unique challenge for developers of Android, the world's most used smartphone and second most used tablet operating system.  

Android Developers Blog
 carried a special post entitled "Preparing for Handsets."  The post is written by Scott Main, lead technical writer for Android's developer site.  It offers a useful guide of how developers can minimize the pain of the multi-size transition.  His guide offers suggestions for streamlining the "Action Bar" tablet-centric interface element, which will now appear in pint-size form on smartphone apps.  The post also suggests that secondary menus now be placed alongside the main screen, for tablet devices, but use a screen transition in smartphones (a single pane/multi-pane approach).

The alternative to making a fully compatible app is to use techniques to prevent your tablet app from being installed on smart phones/small slabs.  Android 3.1 and older apps bin screen sizes into four general classes and allow apps' xml code to define which sizes are supported via the "supports-screens" attribute.  In Android 3.2, the latest version of Honeycomb, the "support-screens" entry sticks around, but its format changes.  Now instead of bins, users define a specific minimum size they wish to allow.  Setting this high enough will essentially disallow most smartphones.

An example of the code to ban smartphones in both 3.1 and 3.2 (and forward compatible with 3.x Ice Cream Sandwich) is:

?manifest ... ? 
   ?supports-screens android:smallscreens="false"
                                 android:requiresSmallestWidthDp="600" /?
   ?application ... ?

Canadian smartphone maker Research in Motion, Ltd. (TSE:RIM) may soon follow Google's example and offer a homogenized OS for its tablets and smartphones.  Currently, the company's PlayBook tablet runs on QNX, an OS RIM recently required.  RIM is porting the OS for use in its BlackBerry business-minded smart phones.  It plans to switch to QNX for its new smartphones in 2012.

Apple Inc. (AAPL), who sits in second place in the smartphone market, and first place in the tablet business, was the first vendor to offer a single operating system for both its tablet and its phone.  Thus far this approach has appeared to overall be beneficial to developers.  Like Ice Cream Sandwich, iOS reserves certain functions for tablets, but have large overarching similarities between tablet and smartphone code within its SDK.

By contrast Microsoft Corp. (MSFT) appears to be the odd man out in insisting on keeping its tablet operating system and smart phone operating system separate.  While Windows 8 will borrow Windows Phone 7's Metro UI look, there's no plans to make the WP7 smartphone operating system run on tablets, or to have the Windows 8 tablet-geared OS run on smartphones.

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

pixel scaling?
By alu on 9/20/2011 4:13:07 PM , Rating: 1
This doesn't address the question about displaying an app on multiple resolution. Does Android resorts to Apple's pixel scaling aka doubling?

PS. Jason, fix the encoding of that XML snippet.

RE: pixel scaling?
By JLL55 on 9/20/2011 4:50:01 PM , Rating: 2
Android Naturally has a scaling ability through the use of resources (HDPI,MDPI,LDPI) which allows for different resolutions. You can also do the apple method and double/half based on resolution.

RE: pixel scaling?
By JasonMick on 9/20/2011 5:46:41 PM , Rating: 2
This doesn't address the question about displaying an app on multiple resolution. Does Android resorts to Apple's pixel scaling aka doubling?

This is already present in Android -- it's called "compatibility zoom". It was added with Android 3.2.

It's essentially the same as pixel doubling, but it supports variable scaling for multiple resolutions besides just 2x (not sure how this stacks up to OpenGL scaling+custom XML layouts for different screens sizes in graphical quality).

As for the encoding issue, I'll forward it along to the web dev, sadly I put the correct HTML tags for angle brackets and they previewed fine, but the site code appears to be mangling them... sorry about that. :(

"If you look at the last five years, if you look at what major innovations have occurred in computing technology, every single one of them came from AMD. Not a single innovation came from Intel." -- AMD CEO Hector Ruiz in 2007

Latest Headlines
Inspiron Laptops & 2-in-1 PCs
September 25, 2016, 9:00 AM
The Samsung Galaxy S7
September 14, 2016, 6:00 AM
Apple Watch 2 – Coming September 7th
September 3, 2016, 6:30 AM
Apple says “See you on the 7th.”
September 1, 2016, 6:30 AM

Most Popular ArticlesSmartphone Screen Protectors – What To Look For
September 21, 2016, 9:33 AM
UN Meeting to Tackle Antimicrobial Resistance
September 21, 2016, 9:52 AM
Walmart may get "Robot Shopping Carts?"
September 17, 2016, 6:01 AM
5 Cases for iPhone 7 and 7 iPhone Plus
September 18, 2016, 10:08 AM
Update: Problem-Free Galaxy Note7s CPSC Approved
September 22, 2016, 5:30 AM

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki