http - Frontend-backend communication for a mobile app -
I am a lot new to the stuff related to server and backend services and I have to develop a mobile app with a backend part Want to I want this backend to serve an iOS app, an Android app as well as a website. Today I have worries about how the frontend part communicates with the backend part:
- Does this work the website in a way?
- Which is the general solution to my problem? Li> Is this an effective way to serve mobile websites along with mobile websites to this backend?
- Is Pars () a good starting point?
Thanks
Looking at your questions in return:
- Does this work only a website works? (HTTP request for server?)
There are several options, but perhaps the most common, or fashionable, is to use an interface at the moment:
First, a SOAP Web based web service may be the most common option:
Here are some discussions on why you can still use instead of SOAP:
- How does the dataset exchange between the frontend and the backend?
HTTPS is used to transport messages via MSAM and is usually included in XML or JSON form
- My problem is normal What is the solution?
I think this question / answer is included in other parts.
- Is there an effective way to find this backend to serve the website along with the mobile app?
Depending on your particular server application, especially its size and architecture, if the server is divided into application components or parts, and for generating a 'idea' or 'HTML' page for web applications The parts are different and your server is different from the 'backend' parts of the application, and your application is of a type that the methodology is largely identical or not that the end user is a web site. Using the mobile and this view is generated for different devices, then there will be an efficient design which will be in the form of backend as normal as possible backend and normal. If the use of the application is very different when used by the mobile client, that does not mean it can not be. More generally, an efficient design maintains as much functionality as possible between mobile and web applications.
This will certainly be familiar with the 'Model View Controller' architectural pattern because the server side frameworks, as well as the Javascript web client frameworks and even many iOS and (to a lesser extent) The Android Framework uses these concepts:
- View-Controller
An important consideration whether you need notifications like 'push' or functionality on your mobile app. If so, you can understand some common solutions to understand whether they meet your needs - perhaps it is easiest to start understanding Apple and Google's offerings, but there are many other solutions available in it:
<
- Is parse () a good starting point?
I am not familiar with this service but it may be that first of all, looking at a simple comfort-based approach and see if it meets your needs.
Comments
Post a Comment