Home | History | Annotate | Download | only in practices
      1 page.title=Best Practices
      2 excludeFromSuggestions=true
      3 page.landing=true
      4 page.landing.intro=Design and build apps the right way. Learn how to create apps that look great and perform well on as many devices as possible, from phones to tablets and more.  
      5 page.landing.image=
      6 
      7 @jd:body
      8 
      9 <div class="landing-docs">
     10 
     11   <div class="col-12">
     12     <h3>Blog Articles</h3>
     13     
     14     <a href="http://android-developers.blogspot.com/2010/10/improving-app-quality.html">
     15       <h4>Improving App Quality</h4>
     16       <p>One way of improving your apps visibility in the ecosystem is by deploying well-targeted
     17 mobile advertising campaigns and cross-app promotions. However, theres another time-tested method
     18 of fueling the impression-install-ranking cycle: improve the product!</p>
     19     </a>
     20     
     21     <a href="http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html">
     22       <h4>Say Goodbye to the Menu Button</h4>
     23       <p>As Ice Cream Sandwich rolls out to more devices, it's important that you begin to migrate
     24 your designs to the action bar in order to promote a consistent Android user experience.</p>
     25     </a>
     26     
     27     <a href="http://android-developers.blogspot.com/2011/07/new-tools-for-managing-screen-sizes.html">
     28       <h4>New Tools For Managing Screen Sizes</h4>
     29       <p>Android 3.2 includes new tools for supporting devices with a wide range of screen sizes.
     30 One important result is better support for a new size of screen; what is typically called a 7-inch
     31 tablet. This release also offers several new APIs to simplify developers work in adjusting to
     32 different screen sizes.</p>
     33     </a>
     34     
     35     <a href="http://android-developers.blogspot.com/2011/03/identifying-app-installations.html">
     36       <h4>Identifying App Installations</h4>
     37       <p>It is very common, and perfectly reasonable, for a developer to want to track individual
     38 installations of their apps. It sounds plausible just to call TelephonyManager.getDeviceId() and use
     39 that value to identify the installation. There are problems with this</p>
     40     </a>
     41     
     42     <a
     43 href="http://android-developers.blogspot.com/2011/11/making-android-games-that-play-nice.html">
     44       <h4>Making Android Games that Play Nice</h4>
     45       <p>Making a game on Android is easy. Making a <em>great</em> game for a mobile, multitasking,
     46 often multi-core, multi-purpose system like Android is trickier. Even the best developers frequently
     47 make mistakes in the way they interact with the Android system and with other applications</p>
     48     </a>
     49     
     50   </div>
     51 
     52 
     53 </div>
     54