Where to start when creating a backend for a mobile application?

Question

PHP

Tell me which is better to use. There is a website and you need a client-application for the phone, how to organize the interaction of the site and the client. I'm looking for a solution in the direction of PHP

Answer 1

You need to implement a RESTful API.
Here the question is how and on what is better for a particular solution.
What PHP, and what is the site written on?
In the case of CMS / CMF - you need to look for or write plugins for them.
In the case of PHP5.2 and Yii-like sites, everything is rather mediocre , although there is a tutorial . In the case of PHP5.3
, people often use swagger with silex .
Well, you can look for bundles on symfony2, although usually people do it like this

Answer 2

You need to write, for example, a RESTful API through which the application will communicate with the site. With this and "need to start."
Well, how to write it is a separate issue. I would choose Symfony + FOSRestBundle, but this is, let's say, at least an average level of knowledge of PHP.

Answer 3

To contrast with other answers and broaden your horizons, the API may also not be RESTful at all.
For example, an RPC-style API based on SOAP, XML-RPC, or JSON-RPC.
Differences between RESTful and RPC-style:
- From the point of view of REST, an application is a set of resources accessible by URI and linked to each other. For clarity, this is a roughly analogue - WWW, hypertext pages, forms, etc. And the client is a browser. The browser knows little about the structure of each particular site, but understands the general principles of the network, so everything works.
- RPC-style, on the other hand, assumes the client's knowledge of the application's device. The application, in turn, is simply a set of functions available through a contract (documentation) and API.
What exactly to use is up to you. It is now fashionable to make RESTful services, as often this architecture fits well into the CRUD paradigm.