Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 1 | page.title=Location APIs |
Joe Fernandez | 33baa5a | 2013-11-14 11:41:19 -0800 | [diff] [blame] | 2 | page.tags=location,geofence,geofencing,gps |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 3 | header.hide=1 |
| 4 | @jd:body |
| 5 | |
| 6 | |
| 7 | <div class="landing-banner"> |
| 8 | |
| 9 | <div class="col-6"> |
| 10 | <img src="{@docRoot}images/google/gps-location.png" alt="Location APIs Logo"> |
| 11 | </div> |
| 12 | |
| 13 | <div class="col-6"> |
| 14 | |
| 15 | <h1 itemprop="name" style="margin-bottom:0;">Location APIs</h1> |
| 16 | <p itemprop="description"> |
| 17 | The location APIs make it easy for you to build location-aware applications, without needing to |
| 18 | focus on the details of the underlying location technology. They also let you minimize |
| 19 | power consumption by using all of the capabilities of the device hardware. |
| 20 | </p> |
| 21 | |
| 22 | <p> |
| 23 | To get started, first <a href="{@docRoot}google/play-services/setup.html">set up</a> |
| 24 | the Google Play services SDK. You can learn how to use the APIs in the training |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 25 | class <a href="{@docRoot}training/location/index.html">Making Your App Location Aware</a>, |
| 26 | and details are available in the <a href="{@docRoot}reference/com/google/android/gms/location/package-summary.html">Location API reference</a>. <!-- To look at a code example, <a href="">download the sample app</a>. --> |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 27 | </p> |
| 28 | </div> |
| 29 | </div> |
| 30 | <div class="landing-docs"> |
| 31 | <h3 style="clear:left">Key Developer Features</h3> |
| 32 | <div class="layout-content-row"> |
| 33 | <div class="layout-content-col span-6"> |
| 34 | |
| 35 | |
| 36 | |
| 37 | <h4 style="font-weight:bold">Fused location provider</h4> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 38 | |
| 39 | <p>The Fused Location Provider intelligently manages the underlying location technology and gives you the best location according to your needs. </p> |
| 40 | |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 41 | <ul> |
| 42 | <li> |
| 43 | <em>Simple APIs</em>: Lets you specify high-level needs like "high accuracy" or "low power", instead of |
| 44 | having to worry about location providers. |
| 45 | </li> |
| 46 | <li> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 47 | <em>Immediately available</em>: Gives your apps immediate access to the best, most recent location. |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 48 | </li> |
| 49 | <li> |
| 50 | <em>Power-efficiency</em>: Minimizes your app's use of power. Based on all incoming location requests and available sensors, fused location provider chooses the most efficient way to meet those needs. |
| 51 | </li> |
| 52 | <li> |
| 53 | <em>Versatility</em>: Meets a wide range of needs, from foreground uses that need highly accurate |
| 54 | location to background uses that need periodic location updates with negligible power impact. |
| 55 | </li> |
| 56 | |
| 57 | </ul> |
| 58 | |
| 59 | <h4 style="font-weight:bold">Geofencing APIs</h4> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 60 | |
| 61 | <p>Lets your app setup geographic boundaries around specific locations and then receive notifications when the user enters or leaves those areas. </p> |
| 62 | |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 63 | <ul> |
| 64 | <li> |
| 65 | <em>Simple but powerful APIs</em>: Allows batch addition and removal of geofences. Ability to manage |
| 66 | multiple geofences at the same time. Ability to filter alerts for both entry and exit or |
| 67 | entry only or exit only. |
| 68 | </li> |
| 69 | <li> |
| 70 | <em>Optimized for battery</em>: Adjusts location updates based on user’s proximity to the geofence |
| 71 | and user’s modality (still, walking, driving, and so on). |
| 72 | </li> |
| 73 | </ul> |
| 74 | </div> |
| 75 | |
| 76 | <div class="layout-content-col span-6"> |
| 77 | <h4 style="font-weight:bold">Activity recognition</h4> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 78 | |
| 79 | <p>With apps becoming increasingly contextual, understanding what the user is doing is critical to surfacing the right content. The Activity recognition API makes it easy to check the user’s current activity—still, walking, cycling, and in-vehicle—with very efficient use of the battery.</p> |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 80 | <ul> |
| 81 | <li> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 82 | <em>Optimized for battery</em>: Uses low-power sensors to recognize the user's current physical activity. |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 83 | </li> |
| 84 | <li> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 85 | <em>Enhances other services with context</em>: Great for adding movement awareness to location awareness. Apps can adjust the amount of |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 86 | location awareness they provide, based on the current user movement. For example, a |
| 87 | navigation app can request more frequent updates when the user is driving. |
| 88 | </li> |
| 89 | <li> |
Dirk Dougherty | d14295c | 2013-05-14 23:25:49 -0700 | [diff] [blame] | 90 | <em>Features for advanced applications</em>: For advanced applications that want to do their own |
Dirk Dougherty | c3a7ea4 | 2013-05-03 13:11:51 -0700 | [diff] [blame] | 91 | post-processing, this API also makes available confidence values for each of the activities. |
| 92 | It also includes two activities that indicate unreliable measurements: unknown and tilt. |
| 93 | </li> |
| 94 | </ul> |
| 95 | </div> |
Scott Main | 527b7623 | 2013-05-15 02:33:57 -0700 | [diff] [blame] | 96 | </div> |