docs/html/design/patterns/pure-android.jd

page.title=Pure Android
page.image=images/cards/design-pure-android_2x.png
@jd:body

<p>Most developers want to distribute their apps on multiple platforms. As you plan your app for
Android, keep in mind that different platforms play by different rules and conventions. Design
decisions that make perfect sense on one platform will look and feel misplaced in the context of a
different platform. While a "design once, ship anywhere" approach might save you time up-front, you
run the very real risk of creating inconsistent apps that alienate users. Consider the following
guidelines to avoid the most common traps and pitfalls.</p>

<div class="vspace size-1">&nbsp;</div>

<div class="cols">
  <div class="col-5">

<h4>Don't mimic UI elements from other platforms</h4>
<p>Platforms typically provide a carefully designed set of UI elements that are themed in a very
distinctive fashion. For example, some platforms advocate rounded corners for their buttons, others
use gradients in their title bars. In some cases, elements may have the same purpose, but are
designed to work a bit differently.</p>
<p>As you build your app for Android, don't carry over themed UI elements from other platforms and
don't mimic their specific behaviors. Review the
<a href="{@docRoot}design/building-blocks/index.html">Building Blocks</a>
section in this styleguide to learn about Android's most important UI elements
and the way they look in the system default themes. Also examine Android's platform apps to get a
sense of how elements are applied in the context of an app. If you want to customize the theme of UI
elements, customize carefully according to your specific branding - and not according to the
conventions of a different platform.</p>

  </div>
  <div class="col-8">

    <img src="{@docRoot}design/media/migrating_ui_elements.png">
    <div class="figure-caption">
      Sampling of UI elements from Android, iOS, and Windows Phone.
    </div>

  </div>
</div>

<div class="vspace size-2">&nbsp;</div>

<div class="cols">
  <div class="col-5">

<h4>Don't carry over platform-specific icons</h4>
<p>Platforms typically provide sets of icons for common functionality, such as sharing, creating a new
document or deleting.</p>
<p>As you are migrating your app to Android, please swap out platform-specific icons with their Android
counterparts.</p>
<p>You can find a wide variety of icons for use in your app on the
<a href="{@docRoot}design/downloads/index.html">Downloads</a> page.</p>

  </div>
  <div class="col-8">

    <img src="{@docRoot}design/media/migrating_icons.png">
    <div class="figure-caption">
      Sampling of icons from Android, iOS, and Windows Phone.
    </div>

  </div>
</div>

<div class="vspace size-2">&nbsp;</div>


<div class="cols">
  <div class="col-5">

<h4>Don't hardcode links to other apps</h4>
<p>In some cases you might want your app to take advantage of another app's feature set. For
example, you may want to share the content that your app created via a social network or messaging
app, or view the content of a weblink in a browser. Don't use hard-coded, explicit links to
particular apps to achieve this. Instead, use Android's intent API to launch an activity chooser
which lists all applications that are set up to handle the particular request. This lets the user
complete the task with their preferred app. For sharing in particular, consider using the <em>Share
Action Provider</em> in your action bar to provide faster access to the user's most recently used
sharing target.</p>

  </div>
  <div class="col-8">

    <img src="{@docRoot}design/media/migrating_intents.png">
    <div class="figure-caption">
      Link to other apps with the activity chooser or use the <em>Share Action Provider</em> in the
      action bar.
    </div>

  </div>
</div>

<div class="vspace size-2">&nbsp;</div>

<div class="cols">
  <div class="col-5">

<h4>Don't use labeled back buttons on action bars</h4>
<p>Other platforms use an explicit back button with label to allow the user to navigate up the
application's hierarchy. Instead, Android uses the main action bar's app icon for hierarchical
navigation and the navigation bar's back button for temporal navigation. For more information,
please review the <a href="{@docRoot}design/patterns/navigation.html">Navigation</a> pattern.</p>
<p>Follow this guideline to provide a consistent navigation experience across the platform.</p>

  </div>
  <div class="col-8">

    <img src="{@docRoot}design/media/migrating_ios_galleries.png">
    <div class="figure-caption">
      Android action bar with up caret vs. iOS labeled "Back" button.
    </div>

  </div>
</div>

<div class="cols">
  <div class="col-5">

<h4>Don't use right-pointing carets on line items</h4>
<p>A common pattern on other platforms is the display of right-pointing carets on line items that allow
the user to drill deeper into additional content.</p>
<p>Android does not use such indicators on drill-down line items. Avoid them to stay consistent with
the platform and in order to not have the user guess as to what the meaning of those carets may be.</p>

  </div>
  <div class="col-8">

    <img src="{@docRoot}design/media/migrating_ios_settings.png">
    <div class="figure-caption">
      Android settings without right-pointing carets in line items vs. iOS settings.
    </div>

  </div>
</div>

<h2 id="device-independence">Device Independence</h2>

<p>Remember that your app will run on a wide variety of different screen sizes. Create visual assets
for different screen sizes and densities and make use of concepts such as multi-pane layouts to
appropriately scale your UI on different device form factors.</p>
<p>For more information, read <a href="{@docRoot}design/style/devices-displays.html">Devices and Displays</a> as
well as <a href="{@docRoot}design/patterns/multi-pane-layouts.html">Multi-pane Layouts</a> in this design guide.</p>