Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 1 | page.title=Program Overview |
| 2 | page.metaDescription=Welcome to the Android M Developer Preview, a program that gives you everything you need to test and optimize your apps for the next version of Android. |
Dirk Dougherty | 7470945 | 2015-05-15 00:51:24 -0700 | [diff] [blame] | 3 | page.image=images/cards/card-preview_16-9_2x.png |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 4 | page.tags="preview", "developer", "android" |
Joe Fernandez | e786688 | 2015-05-06 17:15:03 -0700 | [diff] [blame] | 5 | |
| 6 | @jd:body |
| 7 | |
| 8 | <p> |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 9 | Welcome to the <strong>Android M Developer Preview</strong>, a program that gives you |
| 10 | everything you need to test and optimize your apps for the next version of |
| 11 | Android. It's free, and you can get started right away just by downloading |
| 12 | the M Developer Preview tools. |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 13 | </p> |
| 14 | |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 15 | <div style="background-color:#eceff1;padding:1em;"> |
| 16 | <div class="wrap"> |
| 17 | <div class="cols"> |
| 18 | <div class="col-4of12"> |
| 19 | <h5> |
| 20 | Hardware and emulator system images |
| 21 | </h5> |
| 22 | |
| 23 | <p> |
| 24 | Run and test your apps on Nexus 5, 6, 9, and Player (for TV), as well |
| 25 | as emulator. |
| 26 | </p> |
| 27 | </div> |
| 28 | |
| 29 | <div class="col-4of12"> |
| 30 | <h5> |
| 31 | Latest platform code |
| 32 | </h5> |
| 33 | |
| 34 | <p> |
| 35 | We’ll provide multiple updates during the Preview, so you’ll be testing |
| 36 | against the latest platform changes. |
| 37 | </p> |
| 38 | </div> |
| 39 | |
| 40 | <div class="col-4of12"> |
| 41 | <h5> |
| 42 | Updates delivered by OTA |
| 43 | </h5> |
| 44 | |
| 45 | <p> |
| 46 | You can get updates over the air, once you’ve flashed a |
| 47 | device to the initial preview. |
| 48 | </p> |
| 49 | </div> |
| 50 | </div> |
| 51 | |
| 52 | <div class="cols"> |
| 53 | |
| 54 | <!--<div class="col-4of12"> |
| 55 | <h5>Early access to new APIs</h5> |
| 56 | <p>Explore the new capabilities and APIs offered in the new platform and give us |
| 57 | feedback. Note that APIs and capabilities may change during the Preview |
| 58 | program.</p> |
| 59 | </div>--> |
| 60 | |
| 61 | <div class="col-4of12"> |
| 62 | <h5> |
| 63 | New behaviors and capabilities |
| 64 | </h5> |
| 65 | |
| 66 | <p> |
| 67 | Start work early to support new platform behaviors such as |
| 68 | the new runtime permissions model and power-saving features. |
| 69 | </p> |
| 70 | </div> |
| 71 | |
| 72 | <div class="col-4of12"> |
| 73 | <h5> |
| 74 | Priority window for developer-reported issues |
| 75 | </h5> |
| 76 | |
| 77 | <p> |
| 78 | During the first several weeks we’ll give priority to developer-reported |
| 79 | issues, so test and give feedback as soon as possible. |
| 80 | </p> |
| 81 | </div> |
| 82 | |
| 83 | <div class="col-4of12"> |
| 84 | <h5> |
| 85 | Feedback and support channels |
| 86 | </h5> |
| 87 | |
| 88 | <p> |
| 89 | Report issues and give us feedback using our <a href= |
| 90 | "https://code.google.com/p/android-developer-preview/">issue tracker</a>. |
| 91 | Connect with other developers in the <a |
| 92 | href="http://g.co/dev/AndroidMDevPreview">M Developer Community</a>. |
| 93 | </p> |
| 94 | </div> |
| 95 | </div> |
| 96 | </div> |
| 97 | </div> |
| 98 | |
| 99 | <!-- |
| 100 | <p> |
| 101 | With the M Developer Preview, you'll get an early start on testing your apps, |
| 102 | with enough time to make adjustments before the public platform release later |
| 103 | in the year. We'll provide several updates to the Preview tools in the weeks |
| 104 | ahead, so you can keep in sync with the latest changes as the platform moves |
| 105 | toward launch. |
| 106 | </p> |
| 107 | <img src="{@docRoot}preview/images/m-preview-timeline.png" alt= |
| 108 | "Preview program timeline" id="timeline"> |
| 109 | <p> |
| 110 | You can help us improve the platform by <a href= |
| 111 | "https://code.google.com/p/android-developer-preview/">reporting issues</a> |
| 112 | through our feedback channels. This is especially |
| 113 | critical in the first month of the preview, when we’ll be giving priority to |
| 114 | developer-reported issues and feedback. |
| 115 | </p> --> |
| 116 | |
| 117 | |
| 118 | <h2 id="timeline"> |
| 119 | Timeline and updates |
| 120 | </h2> |
| 121 | <img src="{@docRoot}preview/images/m-preview-timeline-crop.png" alt= |
| 122 | "Preview program timeline" id="timeline"> |
| 123 | <p> |
| 124 | The M Developer Preview runs from May 27 until the final Android M SDK, which |
| 125 | we’ll release shortly before the public release during Q3 |
| 126 | 2015. |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 127 | </p> |
| 128 | |
| 129 | <p> |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 130 | At key development milestones, we’ll deliver updates for your test devices. |
| 131 | The tentative milestones are |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 132 | </p> |
| 133 | |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 134 | <ul> |
| 135 | <li> |
| 136 | <strong>Preview 1</strong> (initial Preview release, late May), |
| 137 | </li> |
| 138 | |
| 139 | <li> |
| 140 | <strong>Preview 2</strong> (late June/early July), and |
| 141 | </li> |
| 142 | |
| 143 | <li> |
| 144 | <strong>Preview 3</strong> (near final, late July) |
| 145 | </li> |
| 146 | </ul> |
| 147 | |
| 148 | <p> |
| 149 | These updates culminate in the <strong>final SDK</strong> (later in Q3), |
| 150 | which delivers the official APIs for the new version of Android, as well |
| 151 | as the final system behaviors and features. |
| 152 | </p> |
| 153 | |
| 154 | <p> |
| 155 | As you test and develop on Android M, we strongly recommend <strong>keeping |
| 156 | your development environment up-to-date</strong> as Preview updates are released. |
| 157 | To make the process easier, we'll deliver <strong>updates over the air |
| 158 | (OTA)</strong> to devices already flashed to a Preview build, as well as |
| 159 | providing system images that you can download and flash manually. |
| 160 | </p> |
| 161 | <p class="note"> |
| 162 | <strong>Note:</strong> The final SDK and system images can not be delivered |
| 163 | by OTA, but will instead need to be <strong>flashed manually</strong> to |
| 164 | your test devices.</strong> |
| 165 | </p> |
| 166 | |
| 167 | <p> |
| 168 | We’ll notify you when Preview updates are available via the <a href= |
| 169 | "http://android-developers.blogspot.com/">Android Developers Blog</a>, as |
| 170 | well as this site and the |
| 171 | <a href="http://g.co/dev/AndroidMDevPreview">Android M Developer Community</a>. |
| 172 | </p> |
| 173 | |
| 174 | <h2 id="preview_tools"> |
| 175 | What’s in the Preview? |
| 176 | </h2> |
| 177 | |
| 178 | <p> |
| 179 | The M Developer Preview includes everything you need to test your existing |
| 180 | apps on a variety of screen sizes, network technologies, CPU/GPU chipsets, |
| 181 | and hardware architectures. |
| 182 | </p> |
| 183 | |
| 184 | <h4> |
| 185 | SDK tools |
| 186 | </h4> |
| 187 | |
| 188 | <p> |
| 189 | You can download these components through the SDK Manager in <a href= |
| 190 | "{@docRoot}sdk/installing/adding-packages.html">Android Studio</a>: |
| 191 | </p> |
| 192 | |
| 193 | <ul> |
| 194 | <li>M Developer Preview <strong>SDK tools</strong> |
| 195 | </li> |
| 196 | |
| 197 | <li>M Developer Preview <strong>emulator system image</strong> (32-bit & |
| 198 | 64-bit) |
| 199 | </li> |
| 200 | |
| 201 | <li>M Developer Preview <strong>emulator system Image for Android TV</strong> |
| 202 | (32-bit) |
| 203 | </li> |
| 204 | </ul> |
| 205 | |
| 206 | <h4> |
| 207 | Hardware system images |
| 208 | </h4> |
| 209 | |
| 210 | <p> |
| 211 | You can download these hardware system images for Nexus devices from the |
| 212 | <a href="downloads.html">Downloads page</a>: |
| 213 | </p> |
| 214 | |
| 215 | <ul> |
| 216 | <li> |
| 217 | <strong>Nexus 5</strong> (GSM/LTE) “hammerhead” device system image |
| 218 | </li> |
| 219 | |
| 220 | <li> |
| 221 | <strong>Nexus 6</strong> “shamu” device system image |
| 222 | </li> |
| 223 | |
| 224 | <li> |
| 225 | <strong>Nexus 9</strong> (Wi-Fi) “volantis” device system image |
| 226 | </li> |
| 227 | |
| 228 | <li> |
| 229 | <strong>Nexus Player</strong> (Android TV) “fugu” device system image |
| 230 | </li> |
| 231 | </ul> |
| 232 | |
| 233 | <h4> |
| 234 | Documentation and sample code |
| 235 | </h4> |
| 236 | |
| 237 | <p> |
| 238 | These documentation resources help you learn about the Preview: |
| 239 | </p> |
| 240 | |
| 241 | <ul> |
| 242 | <li> |
| 243 | <a href="setup-sdk.html">Set Up the SDK</a> has step-by-step instructions |
| 244 | for getting started. |
| 245 | </li> |
| 246 | |
| 247 | <li> |
| 248 | <a href="testing.html">Testing Guide</a> and <a href= |
| 249 | "api-changes.html">Behavior Changes</a> point you to key areas to test. |
| 250 | </li> |
| 251 | |
| 252 | <li>Documentation of new APIs, including an <a href="api-overview.html">API Overview</a>, |
| 253 | downloadable <a href="">API Reference</a>, and detailed developer guides on |
| 254 | key features such as <a href="">permissions</a>, <a href="">app backup</a>, |
| 255 | and others. |
| 256 | </li> |
| 257 | |
| 258 | <li> |
| 259 | <a href="">Sample code</a> that demonstrates how support |
| 260 | permissions and other new features. |
| 261 | </li> |
| 262 | |
| 263 | <li> |
| 264 | <a href="">Release notes</a> for the current version of the M Developer |
| 265 | Preview, including change notes and diff reports. |
| 266 | </li> |
| 267 | </ul> |
| 268 | |
| 269 | <h4> |
| 270 | Support resources |
| 271 | </h4> |
| 272 | |
| 273 | <p> |
| 274 | Use these support resources as you test and develop on the M |
| 275 | Developer Preview: |
| 276 | </p> |
| 277 | |
| 278 | <ul> |
| 279 | <li><a href="https://code.google.com/p/android-developer-preview/">M |
| 280 | Developer Preview Issue Tracker</a> is your <strong>primary feedback |
| 281 | channel.</strong> You can report bugs, performance issues, and general |
| 282 | feedback through the issue tracker. You can also check for known issues |
| 283 | and find workaround steps, if available. |
| 284 | </li> |
| 285 | |
| 286 | <li>The <a href="http://g.co/dev/AndroidMDevPreview">Android M Developer |
| 287 | Community</a> is a Google+ community where you can <strong>connect with |
| 288 | other developers</strong> working with Android M. You can share |
| 289 | observations or ideas or find answers to questions about Android M. |
| 290 | </li> |
| 291 | </ul> |
| 292 | |
| 293 | |
| 294 | <h2 id="preview_apis_and_publishing"> |
| 295 | Targeting, preview APIs, and publishing |
| 296 | </h2> |
| 297 | |
| 298 | <p> |
| 299 | The Android M Developer Preview is a development-only release and |
| 300 | <strong>does not have a standard API level</strong>. If you want to opt out |
| 301 | of compatibility behaviors to test your app (which is strongly recommended), |
| 302 | you can target the M Developer Preview by setting your app's <code><a href= |
| 303 | "/guide/topics/manifest/uses-sdk-element.html">targetSdkVersion</a></code> |
| 304 | to <code>“MNC”</code>. |
| 305 | </p> |
| 306 | |
| 307 | <p> |
| 308 | The Android M Developer Preview delivers <strong>preview APIs</strong> |
| 309 | — the APIs will not be official until the final SDK is released, |
| 310 | currently planned for the third quarter of 2015. This means that you can |
| 311 | <strong>expect minor API changes</strong> over time, especially during |
| 312 | initial weeks of the program. We’ll provide a summary of changes to you with |
| 313 | each update of the Android M Developer Preview. |
| 314 | </p> |
| 315 | |
| 316 | <p class="note"> |
| 317 | Note that although preview APIs may change, underlying system behaviors such |
| 318 | as runtime permissions and power-saving features are stable and ready for |
| 319 | testing right away. |
| 320 | </p> |
| 321 | |
| 322 | <p> |
| 323 | In terms of publishing, Google Play <strong>prevents publishing of apps |
| 324 | targeting the M Developer Preview</strong>. When the Android M final SDK is |
| 325 | available, you’ll be able to target the official Android M API level and |
| 326 | publish your app to Google Play. Meanwhile, if you want to distribute an app |
| 327 | targeting Android M to testers, you can do so via email or by direct download |
| 328 | from your site. |
| 329 | </p> |
| 330 | |
| 331 | <h2 id="get_started"> |
| 332 | How to get started? |
| 333 | </h2> |
| 334 | |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 335 | <p> |
| 336 | To get started testing your app: |
| 337 | </p> |
| 338 | |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 339 | <ol> |
| 340 | <li>Review the <a href="{@docRoot}preview/api-overview.html">API Overview</a> |
| 341 | and <a href="{@docRoot}preview/behavior.html">Behavior Changes</a> to get an |
| 342 | idea of what's new and how it affects your apps. |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 343 | </li> |
| 344 | |
Joe Fernandez | ee143ce | 2015-05-21 21:08:41 -0700 | [diff] [blame] | 345 | <li>Setup for testing and development by following the instructions for |
| 346 | <a href="{@docRoot}preview/setup-sdk.html">Setting up the Preview SDK</a> |
| 347 | and configuring test devices. |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 348 | </li> |
| 349 | |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 350 | <li>Follow the <a href="https://developers.google.com/android/nexus/images"> |
| 351 | flashing instructions</a> to flash the latest M developer preview system image |
| 352 | for Nexus 5, 6, 9, and Player. Once you've flashed your development device, |
| 353 | Preview updates will be delivered through over-the-air (OTA) updates.</a> |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 354 | </li> |
| 355 | |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 356 | <li>Download the <a href="{@docRoot}preview/reference.html">M Preview API |
| 357 | Reference</a> and <a href="{@docRoot}preview/samples.html">M Preview |
| 358 | samples</a> to gain more insight into new API features and how to use them in |
| 359 | your app. |
Joe Fernandez | ee143ce | 2015-05-21 21:08:41 -0700 | [diff] [blame] | 360 | </li> |
| 361 | |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 362 | <li>Join the <a href="http://g.co/dev/AndroidMDevPreview">Android M |
| 363 | Developer Community</a> to get the latest news and connect with other |
| 364 | developers working with the new platform. |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 365 | </li> |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 366 | </ol> |
Joe Fernandez | d575b1c | 2015-05-08 17:16:27 -0700 | [diff] [blame] | 367 | |
| 368 | <p> |
Dirk Dougherty | c85bf85 | 2015-05-24 19:56:35 -0700 | [diff] [blame^] | 369 | Thank you for your participation in the Android M Developer Preview program! |
| 370 | </p> |