2012-06-25 09:56:29 -07:00
|
|
|
page.title=Google Cloud Messaging for Android
|
2013-11-14 11:41:19 -08:00
|
|
|
page.tags=gcm
|
2012-11-30 16:50:00 -08:00
|
|
|
header.hide=1
|
2012-06-25 09:56:29 -07:00
|
|
|
@jd:body
|
|
|
|
|
|
|
|
|
2012-11-30 16:50:00 -08:00
|
|
|
<div class="landing-banner">
|
2013-05-14 16:10:58 -07:00
|
|
|
|
2012-11-30 16:50:00 -08:00
|
|
|
<div class="col-5" style="min-height:100px">
|
|
|
|
<img src="{@docRoot}images/gcm/gcm-logo.png" />
|
|
|
|
</div>
|
|
|
|
<div class="col-7">
|
|
|
|
|
|
|
|
<h1 itemprop="name" style="margin-bottom:0;">Google Cloud Messaging for Android</h1>
|
|
|
|
<p itemprop="description">
|
2014-10-14 15:34:21 -07:00
|
|
|
Google Cloud Messaging (GCM) for Android is a service that allows you to send data
|
2014-05-28 17:31:23 -07:00
|
|
|
from your server to your users' Android-powered device, and also to receive messages from
|
|
|
|
devices on the same connection. The GCM service handles all aspects of queueing of messages
|
2014-10-14 15:34:21 -07:00
|
|
|
and delivery to the target Android application running on the target device, and it is
|
|
|
|
completely free.
|
2012-11-30 16:50:00 -08:00
|
|
|
</p>
|
2013-05-14 16:10:58 -07:00
|
|
|
|
2012-11-30 16:50:00 -08:00
|
|
|
</div>
|
|
|
|
</div>
|
|
|
|
|
2013-04-18 10:57:59 -07:00
|
|
|
<div class="landing-docs">
|
|
|
|
<div class="col-6 normal-links">
|
|
|
|
<h3 style="clear:left">Key Developer Features</h3>
|
|
|
|
<h4>Send data from your server to users' Android-powered devices</h4>
|
|
|
|
<p>This could be a lightweight
|
|
|
|
message telling your app there is new data to be fetched from the
|
|
|
|
server (for instance, a movie uploaded by a friend), or it could be a message containing
|
2014-05-28 17:31:23 -07:00
|
|
|
up to 4kb of payload data (so apps like instant messaging can consume the message directly).
|
|
|
|
<a href="{@docRoot}google/gcm/gcm.html">GCM Architectural Overview.</a></p>
|
2013-05-14 16:10:58 -07:00
|
|
|
|
2013-04-18 10:57:59 -07:00
|
|
|
<h4>Send "send-to-sync" messages</h4>
|
2014-05-28 17:31:23 -07:00
|
|
|
<p>A send-to-sync (collapsible) message is often a "tickle" that tells a mobile
|
|
|
|
application to sync data from the server. For example, suppose you have an email
|
|
|
|
application. When a user receives new email on the server, the server pings the mobile
|
|
|
|
application with a "New mail" message. This tells the application to sync to the server
|
|
|
|
to pick up the new email.
|
|
|
|
<a href="{@docRoot}google/gcm/adv.html#s2s">Learn more »</a></p>
|
2013-05-14 16:10:58 -07:00
|
|
|
|
2013-04-18 10:57:59 -07:00
|
|
|
<h4>Send messages with payload</h4>
|
2014-05-28 17:31:23 -07:00
|
|
|
<p>Unlike a send-to-sync message, every "message with payload" (non-collapsible message)
|
|
|
|
is delivered. The payload the message contains can be up to 4kb.
|
|
|
|
<a href="{@docRoot}google/gcm/adv.html#payload">Learn more »</a></p>
|
2013-04-18 10:57:59 -07:00
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<div class="col-6 normal-links">
|
|
|
|
<h3 style="clear:left">New Features</h3>
|
2013-05-14 16:10:58 -07:00
|
|
|
|
2014-05-28 17:31:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
<h4>Return Receipts</h4>
|
|
|
|
<p>You can use upstream messaging to get receipt notifications, confirming that a given
|
|
|
|
message was sent to a device. Your 3rd-party app server receives the receipt notification
|
|
|
|
from CCS once the message has been sent to the device.
|
|
|
|
<a href="{@docRoot}google/gcm/ccs.html#receipts">Learn more »</a></p>
|
|
|
|
|
2013-05-30 19:06:41 -07:00
|
|
|
|
|
|
|
<h4>Get Started</h4>
|
2014-05-28 17:31:23 -07:00
|
|
|
<p>Get started with a tutorial that walks you through creating a GCM app.
|
|
|
|
<a href="{@docRoot}google/gcm/gs.html">Learn more »</a></p>
|
2013-04-18 10:57:59 -07:00
|
|
|
</div>
|
2012-06-25 09:56:29 -07:00
|
|
|
|
2013-04-18 10:57:59 -07:00
|
|
|
</div>
|
2012-06-25 09:56:29 -07:00
|
|
|
|
2012-07-03 14:36:05 -07:00
|
|
|
|