The first obvious feature of Motorola XOOM is the screen size. It measures 10.1 inches diagonally and displays 1280 x 800 physical pixels. This could impact your application in various ways as described throughout this article.
Because there is no physical keyboard on XOOM, the touch surface becomes the primary point of contact for users. The tablet supports a new feature added in Android™ v2.3 called
android.hardware.touch.multitouch.jazzhands, where 5 or more touchpoints, or pointerIds, are independently tracked. Updates made to the MotionEvent API to support this feature include extensions to pointerId information. To take advantage of this feature, ensure your understanding of multitouch with resources such as Making Sense of Multitouch by Adam Powell on the Android Developers blog.
Resolution and Resources
XOOM runs at a resolution of 160 dpi. If your application uses images, these images will, by default, be chosen from the
/res/drawables-mdpi directory. Up until now you could get away with full screen graphics for a 160-dpi resolution sized around 512 x 512. Without resizing them on the tablet, you’ll get something similar to the following results. http://developer.motorola.com/docstools/library/motorola-xoom-tablet-programming-tips/images/unscaled_bkgd.png/
Keep in mind that the platform still provides support for multiple screen sizes and resolutions. Your application can provide drawables for any of the four generalized densities—ldpi, mdpi, hdpi, and xhdpi. When creating your images, create them with these resolutions in mind. For background images, the physical dimensions of the image (or images) may need to be scaled if the baseline set of images is smaller than the physical size of the screen. You can create a new set of baseline images with larger general dimensions, or you can scale the images you have from within your application.