What is the difference between breaking a phone and a mobile site?

Question

I am new to the phone break. I want to know what is the difference between breaking a phone and a mobile website. I thought about it, but I did not find a suitable solution. Can someone explain this or provide some kind of document.

Answer 1

@axis points to a viable third option. I am sure that you have already considered, and if you are capable, I would recommend writing your own applications in most situations. But; If you want to reach the maximum number of clients with your application using this approach, you need to know / learn different languages ​​for different devices. This makes HTML / CSS / Javascript very attractive, especially when these three are the most commonly used technologies on the Internet today.

So, back to the question:

Phone and mobile sites:

• Both use HTML / CSS / Javascript
• Both can be optimized for mobile devices with frameworks such as jQuery Mobile or Sencha.
• Both can use web services to integrate content.
• Both can use local data storage.

Phonegap:

• It can be placed on the Market for others to find and install the application on their device.
• It remains on the device and can use its hardware (camera / gps / boosters / etc.), as a native application.
• It can be expanded (via plugins) to work with the device’s own code, if necessary.

Mobile site:

• You control the deployment of the application through the web server. (for example, you can make changes and take effect immediately on all devices.)
• Less dependent on web services for including database content.
• You can use PHP / Python / ASP and other web design technologies that create HTML / CSS / Javascript for you.

And I'm sure this list is by no means a complete list of the differences between them, but I hope that I hit the main points ...

Is there any specific question you have?

Answer 2

Phonegap uses web technologies as a bridge between the native APIs of the target platform and the user’s business logic of the application.

The hooded phone book uses a large bold code base / library that translates your HTML / JS into native API calls.

Most users find HTML / JS to be a friendlier solution instead of C / C ++ / Java / ObjC / C # etc., and they don’t need to have a good resume and know how to encode HTML or JS; the disadvantage is that the performances are terrible, and you basically can not do anything about it. Typically, this framework is used by applications that are already dead before entering the market.