Home | History | Annotate | Download | only in practices

Lines Matching full:devices

32 <p>Android is designed to run on many different types of devices. For
33 developers, the range and number of devices means a huge potential audience: the
34 more devices that run Android apps, the more users who can access your app. In
40 what types of devices your app is available to. With a bit of forethought and
42 whose devices can?t run your app will never see it in the Android Market, and
44 control which devices have access to your apps, and how to prepare your apps to
60 devices. Every compatible Android device your app will land on will include
65 Android to prevent apps from being visible to devices which don?t have features
72 only the devices capable of running them.</p>
82 <li>Devices are required to declare the features they include to Android
84 <li>Android Market uses your app?s stated requirements to filter it from devices
89 devices. As long as you accurately describe your app?s requirements, you don?t
98 it?s impossible to keep up with all the Android devices being released, you
111 their devices.</p>
130 some devices don?t have the hardware horsepower to display Live Wallpapers
146 Market uses to match your app to devices that can run it. For instance, if you
148 to devices that don?t support Live Wallpapers.</p>
198 <p>Simply put, Android commits to not making existing apps available to devices
204 However, with version 1.6, Android devices were permitted to omit the auto-focus
209 auto-focus. This allowed Android Market to filter those apps from devices that
213 devices, such as set-top boxes. Android 2.2 included a new feature ID for the
218 require it; but unless you do that, your app won?t be shown to devices without
224 don?t end up being available to devices where they won?t work.</p>
235 developers know which kinds of devices their apps make sense on. We?ve built in