Google I/O 2012 - Building Mobile App Engine Backends for Android, iOS and the Web

Google for Developers · 69K views · 2012 · 48:38

Open on YouTube

Cloud, DevOps & reliabilityWeb developmenttalkdated

Why Stack Overflow recommends it

Stack Overflow users link it when answering or asking about building a Google App Engine backend for mobile apps, especially how Cloud Endpoints generates the API and client libraries.

Recommended by 7 people across 6 different months, 2012 to 2014.

What it is

A Google I/O 2012 session by Dan Holevoet and Christina Ilvento on using App Engine's new Cloud Endpoints feature to build backend APIs for Android, iOS and web clients. It shows annotating Java classes to generate REST endpoints, discovery documents and client libraries, and includes a demo of a tic tac toe app.

What people said

Recommends Aerilys · 2012-08 · Stack Overflow · on “how to use free cloud database with android app?”

As Wingman said, Google App Engine is a great solution for your scenario. You can get some information about GAE+Android here: [LINK] And from this Google IO 2012 session: [this video]

Recommends Cuong Thai · 2012-09 · Stack Overflow · on “RESTful API authentication/security”

You can use Google Service Account for User Authentication. However, people still can register an account and use your API and surely your app engine bill will go up. They've just introduce Google Cloud Endpoints at Google I/O 2012. You will have a Client ID which will only use on your client application(Android,iOS). Google I/O 2012 - Building Android Applications that Use Web APIs with Yaniv Inbar and Sriram Saroop [LINK] Google I/O 2012 - Building Mobile App Engine Backends for Android, iOS and the Web [this video] If you are interested in, you should try to sign up for trusted tester at [LINK]

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 [LINK] Google I/O 2012 - Building Mobile App Engine Backends for Android, iOS and the Web [this video]

Recommends lenik · 2012-11 · Stack Overflow · on “Sharing code between GAEJ and Android projects”

there was a nice talk about GAE & Android integration on the last GoogleIO 2012: Google I_O 2012 - Building Mobile App Engine Backends for Android, iOS and the Web [this video] they show how to use same data structures for data exchange between Android and GAE.

Recommends Carl · 2012-12 · Stack Overflow · on “RESTful application on Google App Engine Java?”

Since these valiant older solutions were patched together, Google has apparently supplied an Eclipse plugin to create a starter project that produces an App Engine app, an Android APK, and a Web app, all talking to one another over an interface defined by a single set of annotated object declarations. Haven't tried this yet myself, but do have a look before trying any of the more heterogeneous examples described in the earlier messages above: [LINK] This Google video is also quite informative: [this video]

Recommends tidalwave · 2012-12 · Stack Overflow · on “What are the servers and database available for communication with android?”

There are lots of options, but you can use Google App Engine with your android application. See this video from Google I/O: [this video]

Recommends Johannes Staehlin · 2013-05 · Stack Overflow · on “GWT and Google Cloud Endpoints”

A few days ago I've started developing a Backend for Mobile Applications using Google App Engine and Google Cloud Endpoints [LINK] . This tutorial [this video] shows how the endpoints are getting generated automatically, as well as the client library for Android. So we have our Entity: @Entity public class Person implements IsSerializable{ @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Key key; private String name; //... } And the endpoint for this class: @Api(name = "personendpoint") public class PersonEndpoint { @ApiMethod(name = "getPerson") public Person getPerson(@Named("id") Long id) { ... Besides, using the generated Android Endpoint Library (that uses the REST API) I woul

Recommends Mike Dee · 2014-04 · Stack Overflow · on “Google Cloud Endpoint Client Library Generation Not Working”

I have found no explanation and assume the problem is that the GPE has been updated and the documentation is old. What has worked for me is to follow this video which an Android client being build to use an endpoint: [this video] The video shows that one must build the endpoint client libraries (from GPE). That generates some source files in the endpoints-lib. Those source files are then copied to the client app. In my case I was building a Java client app. I followed the instructions for build and Android client app, which are here: [LINK] That shows how to call the service from an Android app. Specifically, it shows how to use the source classes that were copied to the client app from the endpo

Cites tesdal · 2012-07 · Stack Overflow · on “RabbitMQ vs GAE”

GAE is not comparable to RabbitMQ to the extent that your question barely makes sense. RabbitMQ is just messaging, and you'd most likely have to set up more infrastructure to support your use cases. GAE is a full infrastructure. That said, RabbitMQ can process an impressive amount of messages per second. Maybe you want to make an API for the mobile game to connect to, and some application logic to go with those messages. You won't let the game clients connect to your RabbitMQ server and talk directly to other clients. On GAE you normally have requests and immediate responses. If you need connections that last longer and allows you to push messages to game client (not using APN etc) you might

Cites Uri · 2012-11 · Stack Overflow · on “Is Google Cloud Endpoints going to replace the ProtoRPC API?”

Just watched the endpoints demo in google I/O 2012 ( [this video] and also [LINK] ). If I understood correctly this replaces the functionality offered by ProtoRPC API, as well as providing an automatic way to prepare the client side API endpoint. Since this can affect my decision of using ProtoRPC in a future project, does anybody knows whether Endpoints is going to replace ProtoRPC or not? Cheers