What are the features of mobile app interfaces? After one and a half years of pc-end web service, I recently switched to a mobile app project to develop interfaces.
Unlike PCs, mobile phones need to consider traffic and power. In addition, the single-time data volume of interfaces is small, and the number of requests and concurrency are relatively high.
What are the features of app interfaces?
Is there any need for complex object-oriented encapsulation?
Is it necessary to use the framework? Which one is suitable?
Reply to discussion (solution)
There is no difference between interfaces and PCs. you can write the json output data of the object. The data selection problem on the mobile phone end is caused by traffic and power issues.
There is no difference between interfaces and PCs. you can write the json output data of the object. The data selection problem on the mobile phone end is caused by traffic and power issues.
In fact, I don't know about the traffic and power, and I don't know how to optimize it. I just want to extract the same string as much as possible.
The main question is still on the framework.
As long as there is data transfer, the traffic must exist. It is necessary to reduce redundant data to save traffic.
Data transmission requires more power than data reception. the fewer data transmission, the better.
It is better to use a framework than not, because at least you do not know much about mobile communication.
After you become familiar with it, you can decide the choice of the framework.
As long as there is data transfer, the traffic must exist. It is necessary to reduce redundant data to save traffic.
Data transmission requires more power than data reception. the fewer data transmission, the better.
It is better to use a framework than not, because at least you do not know much about mobile communication.
After you become familiar with it, you can decide the choice of the framework.
To compress redundant data, we need to look at the design of the data structure.
Currently, I am confused about the framework. in the code I just took over, ThinkPHP is the PC-Side Management backend, and the mobile phone API is native. Only one DBconnect is included. every database operation is mysql_query, however, after reading the previous author's code, the level of the code does have a big question mark in my mind.
The framework may be too redundant for mobile phone interfaces, but I also want to encapsulate some data filtering, communication verification encryption, caching, and Operation interfaces whose data models are objects, at present, I can't write a complete set of items horizontally, just because the product is just launched and does not need to consider load concurrency or anything. it may be appropriate to get started with the framework first.
At present, I am most familiar with TP. I heard that CI is very lightweight and has gone through some documents. can I recommend a framework suitable for app interfaces for Xueda or passers-?
Except for those directly related to mobile phones, there is no difference between the server and the server, isn't it just providing data?
As long as there is data transfer, the traffic must exist. It is necessary to reduce redundant data to save traffic.
Data transmission requires more power than data reception. the fewer data transmission, the better.
It is better to use a framework than not, because at least you do not know much about mobile communication.
After you become familiar with it, you can decide the choice of the framework.
To compress redundant data, we need to look at the design of the data structure.
Currently, I am confused about the framework. in the code I just took over, ThinkPHP is the PC-Side Management backend, and the mobile phone API is native. Only one DBconnect is included. every database operation is mysql_query, however, after reading the previous author's code, the level of the code does have a big question mark in my mind.
The framework may be too redundant for mobile phone interfaces, but I also want to encapsulate some data filtering, communication verification encryption, caching, and Operation interfaces whose data models are objects, at present, I can't write a complete set of items horizontally, just because the product is just launched and does not need to consider load concurrency or anything. it may be appropriate to get started with the framework first.
At present, I am most familiar with TP. I heard that CI is very lightweight and has gone through some documents. can I recommend a framework suitable for app interfaces for Xueda or passers-?
What's so tangled about this? Output the JSON data that the mobile phone wants to obtain, and then the mobile phone receives post-processing. The Cache mechanism used in processing is a problem on the mobile phone. the optimization of the interface is data query optimization and reasonable data allocation, if you do not want to delete the json data, the json data is usually very small and the maximum is a few K. In short, the interface is to make json output.
If you are writing a server-side interface, you do not need to consider the power issue, just like the web api.
Only return in json format.
The server does not need to consider the power of the mobile phone. you only need to pay attention to the traffic, and now basically all the data in json format is returned. Therefore, in terms of data returned, only necessary fields are provided, avoid unnecessary field redundancy. As for the framework, check your choice and understand the framework. we recommend that you use the framework in the early stage.
Thank you for using Thinkphp to develop the first version based on the PC web idea.
