Mobile application implementation options for multiple platforms

Question

JavaScript

I need to create a program for remote users. The application will not have the Internet, + it should be less dependent on the infrastructure of the enterprise.

From here, the conditions were set:
* Downloading directories through a file
* Uploading to a file
* Storing intermediate typed data
* The application must be downloaded directly to the phone / tablet and work offline

I wanted to do everything in html5, I threw in the prototype pihel.jino.ru/local/index2. htm , but immediately a lot of minuses:
* no way to save the result to a file
* no way to load the reference file through the browser in chrome (without additional settings)
* long to do, there are no standard controls (grid, date) Or is extjs suitable here? (I checked it works on the tablet, I'm not sure on the phones)
* You can't upload files to the iphone? Or is it possible to make an application that will work offline, even if you reopen the browser?

Breeding a zoo for all platforms in the form of native applications is not much of a hunt.

Can anyone advise how to get around the above cons?

Answer 1

* it is not possible to save the result to a file
. Store data in the local storage.
* it is not possible to download the directory file through the browser in chrome (without additional settings)
If you refuse the file, then all data will be taken from the local storage.
jquerymobile.com/
There is also jquerymobile.com/

Answer 2

In my opinion, this would be more efficient than saving, downloading, sending the file, as I understand it.

Answer 3

As an implementation option (rather not for your case, just theoretical) - there are so-called. MEAP platforms.
They work like this: for each version of the mobile OS there is a universal interpreter program that compiles for each application and dynamically pulls up the given business logic and configuration. Of the benefits - centralized control over versions and updates (you can force updates when the device goes online). There are a lot of disadvantages:
- Proprietary, expensive
- Requires a middleware server to communicate with devices
- There are no open developer communities
- Limited standard functionality