Scribd
Upload
71 views

Platforms HTML PDF

The document discusses how to support multiple Android platform versions in an app by specifying minimum and target API levels, checking the system version at runtime, and using platform styles and themes. It recommends supporting the latest APIs while also supporting older versions used by about 90% of active devices, as shown on the Android dashboard.

Uploaded by

elmejorc
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
71 views

Platforms HTML PDF

The document discusses how to support multiple Android platform versions in an app by specifying minimum and target API levels, checking the system version at runtime, and using platform styles and themes. It recommends supporting the latest APIs while also supporting older versions used by about 90% of active devices, as shown on the Android dashboard.

Uploaded by

elmejorc
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Supporting Different Platform Versions

While the latest versions of Android often provide great APIs for your app, you should continue to support older versions of Android until more devices get updated. This lesson shows you how to take advantage of the latest APIs while continuing to support older versions as well. The dashboard for Platform Versions (http://developer.android.com /about/dashboards/index.html) is updated regularly to show the distribution of active devices running each version of Android, based on the number of devices that visit the Google Play Store. Generally, its a good practice to support about 90% of the active devices, while targeting your app to the latest version.
THIS LESSON TEACHES YOU TO 1. Specify Minimum and Target API Levels 2. Check System Version at Runtime 3. Use Platform Styles and Themes

YOU SHOULD ALSO READ Android API Levels Android Support Library

Tip: In order to provide the best features and functionality across several Android versions, you should use the Android Support Library (/tools/support-library/index.html) in your app, which allows you to use several recent platform APIs on older versions.

Specify Minimum and Target API Levels


The AndroidManifest.xml (/guide/topics/manifest/manifest-intro.html) file describes details about your app and identifies which versions of Android it supports. Specifically, the minSdkVersion and targetSdkVersion attributes for the <uses-sdk (/guide/topics/manifest/uses-sdk-element.html) element identify the lowest API level with which your app is compatible and the highest API level against which youve designed and tested your app. For example: < <m ma an ni if fe es st t xmlns:android="http://schemas.android.com/apk/res/android" ... > > < <u us se es s-s sd dk k android:minSdkVersion="4" android:targetSdkVersion="15" / /> > ... < </ /m ma an ni if fe es st t> > As new versions of Android are released, some style and behaviors may change. To allow your app to take advantage of these changes and ensure that your app fits the style of each user's device, you should set the targetSdkVersion (/guide/topics/manifest/uses-sdk-element.html#target) value to match the latest Android version available.

Check System Version at Runtime


Android provides a unique code for each platform version in the Build
(/reference/android/os/Build.html)

constants class. Use these codes within your app to build conditions that ensure the code that depends on higher API levels is executed only when those APIs are available on the system. p pr ri iv va at te e v vo oi id d setUpActionBar() { // Make sure we're running on Honeycomb or higher to use ActionBar APIs i if f (B Bu ui il ld d.VERSION.SDK_INT >= B Bu ui il ld d.VERSION_CODES.HONEYCOMB) { A Ac ct ti io on nB Ba ar r actionBar = getActionBar(); actionBar.setDisplayHomeAsUpEnabled(t tr ru ue e); } } Note: When parsing XML resources, Android ignores XML attributes that arent supported by the current device. So you can safely use XML attributes that are only supported by newer versions without worrying about older versions breaking when they encounter that code. For example, if you set the targetSdkVersion="11", your app includes the ActionBar (/reference/android/app/ActionBar.html) by default on Android 3.0 and higher. To then add menu items to the action bar, you need to set android:showAsAction="ifRoom" in your menu resource XML. It's safe to do this in a cross-version XML file, because the older versions of Android simply ignore the showAsAction attribute (that is, you do not need a separate version in res/menu-v11/).

Use Platform Styles and Themes


Android provides user experience themes that give apps the look and feel of the underlying operating system. These themes can be applied to your app within the manifest file. By using these built in styles and themes, your app will naturally follow the latest look and feel of Android with each new release.

To make your activity look like a dialog box: < <a ac ct ti iv vi it ty y android:theme="@android:style/Theme.Dialog"> > To make your activity have a transparent background: < <a ac ct ti iv vi it ty y android:theme="@android:style/Theme.Translucent"> > To apply your own custom theme defined in /res/values/styles.xml: < <a ac ct ti iv vi it ty y android:theme="@style/CustomTheme"> > To apply a theme to your entire app (all activities), add the android:theme attribute to the <application> (/guide/topics/manifest/application-element.html) element: < <a ap pp pl li ic ca at ti io on n android:theme="@style/CustomTheme"> > For more about creating and using themes, read the Styles and Themes (/guide/topics/ui/themes.html) guide.

You might also like