From 44108b54543c87e2c46a6d5d4339b3c4e06373de Mon Sep 17 00:00:00 2001
From: Dirk Dougherty
Fortunately, Android has built-in tools and support that make it easy for -your apps to do that, while at the same time maintaining control of what types -of devices your app is available to. If you do your work properly, users +your apps to do that, while at the same time letting you maintain control of +what types of devices your app is available to. With a bit of forethought and +some minor changes in your app's manifest file, you can ensure that users whose devices can’t run your app will never see it in the Android Market, and will not get in trouble by downloading it. This page explains how you can control which devices have access to your apps, and how to prepare your apps to make sure they reach the right audience.
-A device is “Android compatible” if it can correctly run apps written for the Android execution environment. The exact details of the Android execution diff --git a/docs/html/guide/practices/screens_support.jd b/docs/html/guide/practices/screens_support.jd index 45e3e49..2863fb2 100644 --- a/docs/html/guide/practices/screens_support.jd +++ b/docs/html/guide/practices/screens_support.jd @@ -171,7 +171,9 @@ device screen, and adapts them to the actual pixel map of the screen.
The table below lists some of the more common screens supported by Android and illustrates how the platform maps them to generalized screen -configurations.
+configurations. Some devices use screens that are not specifically listed +in the table — the platform maps those to the same set generalized +screen configurations. diff --git a/docs/html/sdk/android-1.5.jd b/docs/html/sdk/android-1.5.jd index ab74631..1d6e0ad 100644 --- a/docs/html/sdk/android-1.5.jd +++ b/docs/html/sdk/android-1.5.jd @@ -10,25 +10,31 @@ sdk.platform.deployableDate=May 2009