Interpreting four mobile Web application Development Framework Truth

"51CTO" There is a lot of controversy about the new mobile web framework and mobile platform recently. In all fairness, the confusion and ambiguity of these tools in terms of content is one of the reasons for misunderstanding. I want to try to clean up the confusion on this level of understanding through a few brief comments.

Web mobile apps are not the same as on-premises mobile apps

Many people believe that titanium and phonegap and Sencha touch and jquery Mobile are competitors. In fact, they are not the same kind of thing. I'm sure someone will refute me when I throw my own opinion. But web mobile apps should be seen as a type of Web site, just like basecamphq.com or twitter.com. A web-based mobile application runs on top of the browser, and the resources it calls are almost always remote and stored on the server side. Of course, it's not ruled out that some information can also be stored locally, but ultimately, it's essentially a Web application.

The local application runs on our device and all of its resources are installed on our local device. The local application uses the platform, language, and special local APIs of the device to connect to the device. Let's say we can't run nsstring in a Web-page mobile app, because only local applications can access local resources, and the Web-mobile app doesn't.

"So what's the difference between them?" The difference is as follows: Sencha Touch and JQuery Mobile

They have a Web page movement framework. We can use these technologies to create web-based mobile applications. They cannot access any local APIs. Both of them operate on JavaScript. And although they deal with similar problems in a completely independent manner, they still have common ground, that is, they serve mobile pages.

You can use Sencha touch with jquery Mobile on PhoneGap and titanium. If we can accept html/js as our own local application, you can also embed PhoneGap or titanium in the browser and place it in the app's online store or market. I think this is probably the root of the misunderstanding. Localizing Sencha Touch or jquery Mobile does not make it a true on-premises application. The process simply makes it look like a local application. We may have some functionality from the API in PhoneGap or titanium, but this is still not necessarily known as a "local" application. They can only be viewed as Web applications running on local devices at best. This application of Web technology to localization is quite remarkable. There is not much resemblance between PhoneGap and Titanium PhoneGap and Titanium and Sencha touch and jquery Mobile. In fact, I can be blunt. Some--phonegap and titanium are not exactly alike. Of course they both allow you to freely assign local or class-native applications. Nor do they need to prepare additional "create support" for Sencha touch or jquery mobile. Why? Because the device they support comes with a browser. Keep in mind that Sencha touch and jquery Mobile are running on the browser. Because PhoneGap and titanium both allow us to run programs in a browser on a particular device, they actually support Sencha touch and jquery mobile in this way.

The biggest difference between phonegap and titanium is the functionality they provide. PhoneGap's service content is more like a browser-dependent shell, which behaves similar to a native application, but essentially a html/javascript application. Titanium does exactly the same thing with page previews, but it's a step further, providing a lot of local APIs outside the browser for Cocoa touch. According to my observations, 95% of the two apps in the online store are not run on a Web page.

On titanium we encode through JavaScript and take advantage of the unique APIs provided by titanium itself. The end result is that the application is running with native performance, local user interface, and so on. To summarize: We encode in JavaScript, and the actual operation is based on objective-c (this refers to the iOS class application). I am still skeptical of the praise for the "end of the local application". After making the application for the browser and the device, I think the combination of the two is the right choice and a great space for development. Understanding the differences between the various technologies, I think this should be helpful in figuring out the nature of all kinds of tools.

Interpreting four mobile Web application Development Framework Truth