Without your help I'd inadvertently skip some critical setup screens and potentially exit OOBE with a device that is not fully configured for use and that would be a huge disaster. You literally saved my device!
Is distribution the only problem? If Mozilla or Google were to make their code freely available on some git forge like GitHub and I cloned the repo and built it myself, would I be able to run it for seven days or something in the US?
Because these phones are cheaper.. I plan on using iOS in the future where I'm required to use government/banking apps, but I have to start saving money right now since iphones are considerably more expensive than low-end android phones.
Apple is working hard to make sure the answer is no (by not implementing advanced PWA APIs in WebKit and by not allowing other browser engines on iOS).
I have looked into developing a PWA. For starters:
1. Decent storage API. Last time I checked, there were serious limitations on the amount of storage you can use, especially in iOS
2. Mechanism for the user to save a certain . Analogous to saving and running a .exe and being able to compare the file hashes and run different versions of a file without the app developer's intent. This would include the ability to write and edit web apps from your device.
3. Some way of sending TCP/UDP packets directly, and doing port forwarding through UPnP.
4. Mechanism to run processes in the background, and for inter-app communication.
For example, you could not make a decent bittorrent app as a PWA. This is an example of an app which is prohibited on the app store despite having Apple having no legal basis for doing so.
I've often wondered if it would be possible to make some sort of "PWA Browser" that would give web apps hooks to some of this functionality, but it would probably get banned (There are no real rules on the app store, they can just ban you for whatever they want).
reply