Android Cloud to Device Messaging with the Google App Engine
13 likes4,958 views
The document discusses cloud-to-device messaging using Google App Engine, focusing on the C2DM framework for Android devices. It explains the benefits of push notifications over polling methods, highlights architecture details, and provides guidance for implementing C2DM in applications. Additionally, it outlines the advantages of Google App Engine for hosting web applications, including scalability and ease of deployment.
Android Cloud to Device Messaging with the Google App Engine
- 1. Cloud to Device Messaging(with Google App Engine)Lars VogelTwitter: @vogellahttp://www.vogella.de
- 2. About me – Lars Vogel Works as independent Eclipse and Android Consultant and TrainerAlso works for SAP AG as Product Owner in a Scrum teamMaintains http://www.vogella.de Java, Eclipse and Android related Tutorials with ~20 000 visitors per day
- 3. The challengeMobile PhoneData in the Cloud
- 4. Internet creates value for your application
- 5. Getting the dataPolling Pushing
- 6. Polling is easy1.) Ask the server if new data is available2.) If new data is available download it3.) Sleep / wait 4.) Repeat 1.)
- 8. Polling every 5 min can consume 10 % of your battery
- 9. PushingServer informs the phone once new data is availableInfo triggeres a download of data
- 10. Cloud to Device MessagingAvailable for Android 2.2 (Beta – Invite only)Requires the Market available on the deviceUse existing Google connectionsLight-weight data will be send to the deviceMessage is specific to your application (via permission)Use AlarmManager to keep the connection (Heartbeat)
- 11. C2DM – Building blocksGmail User for the application registrationAndroid ApplicationGoogles C2DM serverYour Application Server
- 12. C2DM ArchitectureGoogles C2DM ServerAndroid AppYour application server
- 13. C2DM ArchitectureRequest registration IDUnique registration IDGoogles C2DM ServerAndroid AppServer might send new registration ID
- 14. C2DM ArchitectureSends Registration ID to serverAndroid AppServer stores the registration ID
- 15. Sending messagesNew HTTP Post message with registration id and authentication token *200 – ok (with id==ok)404 – get no auth token503 – Retry with backoff
- 16. Return 200 with errorQuotaExceededInvalidRegistrationMessageTooBigMissingCollapseKey
- 17. C2DM ArchitectureSends notification message to deviceReads the real data from server
- 18. Building the app
- 19. Actually its relatively simpleGoogle provides some util classesTo register call: C2DMessaging.register(context, [email protected])Register the Google provided C2DM broadcast receiver in your „AndroidManifest.xml“.Google receiver will forward the information it receives to: context.getPackageName() + ".C2DMReceiver"
- 20. Your C2DMReceiverGets the registration ID and send it to your server
- 21. Permissions
- 23. Send registration ID to server
- 24. Further pointsBest effort delivery: Google will try to deliver all messages but some might get lost Push can send 1024 characters -> not suited for big data, just notification
- 25. Server can be anythingcurl, php, For testing build your server also on the phone....
- 26. Your Java application server
- 27. from Guillaume Laforge and Patrick Chanezon http://www.slideshare.net/glaforge/google-app-engine-java-groovy-baby
- 28. Writing Java Webs application is annoyingly hard...
- 29. Google App EngineGAE allows you to host webapplications on the Google infrastructure. Scalable Infrastructure
- 30. Google App EngineNo Server maintenanceSuper easy deployment
- 31. It automatically scales up and downComputing power over time
- 32. App Engine ArchitectureLoad BalancerApp Engine FrontEndApp Engine FrontEndApp Engine FrontEndAppServerAppServerAppServer
- 33. GAE Key pointsDeployment is super simpleSupports subset of JPA / JDO for persistenceScalable per definitionFree to get started (significant volume)
- 34. Receiving the registration ID
- 35. Send out message
- 36. Funny: Cloud vrs. MobileCloudNo Threads (Webworkers)No Access to file systemOnly Key / Value (+JPA, JDO)Time limited for requests 30 MobileThreadsAccess to file systemSQL DatebaseTime limited for Activity 5 secs
- 37. Summary C2DM powerful and relatively simple to useGoogle App Engine makes the server site easy
- 38. Picture CreditsAdd the prefix http://www.sxc.hu/photoElephant: http://www.sxc.hu/photo/103473Mouse http://www.sxc.hu/photo/1097314Liquid http://www.sxc.hu/photo/1109534Beta 853828Despair 150108Old Computer http://www.sxc.hu/photo/1028528Person with remote http://www.sxc.hu/photo/485640Victory fingers 906072Guy with a tie 877661
- 39. Futher informationC2DM Tutorialhttp://www.vogella.de/articles/AndroidCloudToDeviceMessaging/article.htmlGoogle App Engine Tutorialhttp://www.vogella.de/articles/GoogleAppEngineJava/article.htmlChrome to Phone Example http://code.google.com/p/chrometophone/
- 40. Thank youFor further questions:[email protected]://www.vogella.dehttp://www.twitter.com/vogella
- 41. License & AcknowledgementsThis work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Germany LicenseSee http://creativecommons.org/licenses/by-nc-nd/3.0/de/deed.en_US