Endpoints are an excellent choice for backend APIs. A very common paradigm is to have a front end (browser or mobile) deliver the UI and communicate to a back end API done with endpoints. This separates data manipulation from data presentation and is definitely a good practice. The Getting Started <https://cloud.google.com/appengine/docs/python/endpoints/getstarted/backend/> tutorial is a great example of this in practice.
On Thursday, June 9, 2016 at 10:15:43 AM UTC-4, Andrew James wrote: > > From the tutorials I have seen, you can package html/css within an > Endpoints app, effectively creating a dynamic web app. Is this good > practise, or is the recommended approach to create a separate app > (containing the front-end code) and host it in app engine? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2031dfbd-a077-438a-9ff2-39971ecf867c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
