Google I/O 2011: Android + App Engine: A Developer's Dream Combination
Why Stack Overflow recommends it
Stack Overflow users link it as the canonical walkthrough for connecting an Android client to an App Engine backend and for setting up C2DM push notifications.
Recommended by 11 people across 8 different months, 2011 to 2013.
What it is
A Google I/O 2011 session by Xavier Ducrohet and Brad Abrams introducing App Engine tooling for Android, a set of Eclipse-based Java tools for building Android apps backed by App Engine. It walks through building a cloud-connected Android app, including C2DM push messaging and one-step deployment of the server side.
What people said
Strong rec spierce7 · 2011-06 · Stack Overflow · on “How to implement C2DM in android?”
You are currently implementing C2DM in an older way. The way you are doing offers a lot of customizability, but not many people need that kind of customizability. With the new Google Plugin 2.4 Beta they have actually started integrating it all in, and it's pretty nice. I'd highly recommend you watch the Google IO Android + AppEngine. They show how to integrate Android, AppEngine, and C2DM together really really simply. You can create something they call an "AppEngine Connected Android Project". So instead of making a ServerSimulator, you'd be actually working with a real server that can all be setup for free. [this video] If you wanted to move to another server, you'd have to re-write the server
Recommends Nic Strong · 2011-06 · Stack Overflow · on “Standard architecture for iOS/Android apps requiring server-side”
For Android, Google have started to produce tooling around integration with AppEngine using RPC. This Google IO video [this video] runs through the new tooling, or the highlights can be found on this blog post [LINK] .
Recommends Rajesh Sharma · 2011-06 · Stack Overflow · on “The roadmap to an Android development expert”
If u want to make a career in Android, first learn basics in JAVA. Read JAVA The Complete Reference book to improve your understanding. Then start learning Android. Using Google search will provide you a lot of video tutorials to learn android. check out Google I/O developer conference [LINK] and also this video [this video]
Recommends renam.antunes · 2011-08 · Stack Overflow · on “server for mobile applications”
Since you used the android tag, I would recommend Google AppEngine [LINK] . There was a session in Google I/O 2011 about that. Google I/O 2011: Android + App Engine: A Developer's Dream Combination [this video]
Recommends Rohan · 2012-01 · Stack Overflow · on “Client Communication over GAE”
How about: Android <-> App Engine : C2DM Here's a good video about it: [this video] C#/Java <-> App Engine : Http Post/Get, create a http servlet at the app engine side. And standard http request on c#/java. Here's a blog about the servlet side: [LINK]
Recommends ChrLipp · 2012-02 · Stack Overflow · on “Handle Google C2DM intents in a service?”
Quote from Google [LINK] : An application on an Android device doesn’t need to be running to receive messages. The system will wake up the application via Intent broadcast when the the message arrives, as long as the application is set up with the proper broadcast receiver and permissions. So, no. The only way to receive the messages is within a broadcast receiver. This is no big deal. Normally you receive the message and then you call a service. Google even provides you with an standard implementation. The Google IO session Android + App Engine: A Developer’s Dream Combination [this video] uses a wizard (see below for the installation) to generate the code. Search for C2DMBaseReceiver , C2DMBroa
Recommends Cuong Thai · 2012-03 · Stack Overflow · on “Can't connect Emulator to Google App Engine”
Hoang, have you seen this [LINK] session on Google I/O 2011? This is a very good demo with sample code. Please have a look and see if it helps:) [this video] [LINK]
Recommends Chris Hinshaw · 2012-08 · Stack Overflow · on “How to reuse entities, DTOs and client service interfaces from a GWT app to another”
What you might want to do is to use request factory instead of the rpc service mechanism which does not required serializable objects. This also has a native java jar that can be used inside android environment. Here is an excellent video for using ClientFactory go implement device type gwt ui's [LINK] Here is another video that was helpful for me that explains using the same request factory code for native android java and for gwt [this video]
Recommends Aerilys · 2012-08 · Stack Overflow · on “how to use free cloud database with android app?”
The Google IO session link is provided up there can help you. And this session too: [this video] You can also look at the code generated by Eclipse when you create a project "“App Engine Connected Android Project"
Recommends lenik · 2012-11 · Stack Overflow · on “Using App Engine to update a database in a app”
this should help: Google I/O 2011: Android + App Engine: A Developer's Dream Combination [this video] Google I/O 2012 - Building Mobile App Engine Backends for Android, iOS and the Web [LINK]