Roman Nurik | b99ae73 | 2012-03-06 12:26:15 -0800 | [diff] [blame] | 1 | page.title=Backwards Compatibility |
Scott Main | 64d5103 | 2013-04-12 14:00:30 -0700 | [diff] [blame] | 2 | page.tags="support" |
Roman Nurik | b99ae73 | 2012-03-06 12:26:15 -0800 | [diff] [blame] | 3 | @jd:body |
| 4 | |
Scott Main | cbcd17d | 2013-05-14 08:46:55 -0700 | [diff] [blame] | 5 | <a class="notice-developers" href="{@docRoot}training/basics/supporting-devices/index.html"> |
| 6 | <div> |
| 7 | <h3>Developer Docs</h3> |
| 8 | <p>Supporting Different Devices</p> |
| 9 | </div> |
| 10 | </a> |
| 11 | |
Roman Nurik | b99ae73 | 2012-03-06 12:26:15 -0800 | [diff] [blame] | 12 | <p>Significant changes in Android 3.0 included:</p> |
| 13 | <ul> |
| 14 | <li>Deprecation of navigation hardware keys (Back, Menu, Search, Home) in favor of handling navigation |
| 15 | via virtual controls (Back, Home, Recents).</li> |
| 16 | <li>Robust pattern for the use of menus in action bars.</li> |
| 17 | </ul> |
| 18 | <p>Android 4.0 brings these changes for tablets to the phone platform.</p> |
| 19 | |
| 20 | <h2 id="older-hardware">Adapting Android 4.0 to Older Hardware and Apps</h2> |
| 21 | |
| 22 | <div class="layout-content-row"> |
| 23 | <div class="layout-content-col span-6"> |
| 24 | |
| 25 | <h4>Phones with virtual navigation controls</h4> |
| 26 | <p>Android apps written for Android 3.0 and later display actions in the action bar. Actions that don't |
| 27 | fit in the action bar or aren't important enough to be displayed at the top level appear in the |
| 28 | action overflow.</p> |
| 29 | <p>Users access the action overflow by touching it in the action bar.</p> |
| 30 | |
| 31 | </div> |
| 32 | <div class="layout-content-col span-7"> |
| 33 | |
| 34 | <img src="{@docRoot}design/media/compatibility_virtual_nav.png"> |
| 35 | |
| 36 | </div> |
| 37 | </div> |
| 38 | |
| 39 | <div class="layout-content-row"> |
| 40 | <div class="layout-content-col span-6"> |
| 41 | |
| 42 | <h4>Phones with physical navigation keys</h4> |
| 43 | <p>Android phones with traditional navigation hardware keys don't display the virtual navigation bar at |
| 44 | the bottom of the screen. Instead, the action overflow is available from the menu hardware key. The |
| 45 | resulting actions popup has the same style as in the previous example, but is displayed at the bottom of the screen.</p> |
| 46 | |
| 47 | </div> |
| 48 | <div class="layout-content-col span-7"> |
| 49 | |
| 50 | <img src="{@docRoot}design/media/compatibility_physical_buttons.png"> |
| 51 | |
| 52 | </div> |
| 53 | </div> |
| 54 | |
| 55 | <div class="layout-content-row"> |
| 56 | <div class="layout-content-col span-6"> |
| 57 | |
| 58 | <h4>Legacy apps on phones with virtual navigation controls</h4> |
| 59 | <p>When you run an app that was built for Android 2.3 or earlier on a phone with virtual navigation |
| 60 | controls, an action overflow control appears at the right side of the virtual navigation bar. You |
| 61 | can touch the control to display the app's actions in the traditional Android menu styling.</p> |
| 62 | |
| 63 | </div> |
| 64 | <div class="layout-content-col span-7"> |
| 65 | |
| 66 | <img src="{@docRoot}design/media/compatibility_legacy_apps.png"> |
| 67 | |
| 68 | </div> |
| 69 | </div> |