On Thu, Jun 19, 2014 at 12:57 PM, Jim Porter <[email protected]> wrote: > On 06/18/2014 01:28 PM, Jonas Sicking wrote: >> However if we can enable developers to sign their own applications, >> rather than having to have them signed by the marketplace, then that >> would still mean that developers could roll out updates as quickly as >> web developers do today. I.e. no need to wait for review from a >> marketplace. > > I'd argue that for many (but certainly not all) apps, the existing state > of affairs regarding installation is a feature, not a bug. In many > cases, I expressly *want* the ability to control the version I'm on, and > the web model doesn't really allow for this.
Update scheduling is really orthogonal to packaged vs. hosted. At least in the case when a hosted is using any form of offline caching. We already give users the exact same control over updates of hosted apps that use appcache as for packaged apps. I expect that to remain true as we roll out Service Workers as well. However I do expect that the current update policies that we use will change from what they are today. Using a default policy of asking users for each app update is good for keeping data consumption low, but bad for almost everything else. And long term it might even be bad for data consumption if it causes developers to work around the update prompt by making more of the application's logic be runtime controlled rather than being embedded in the app package/appcache/serviceworker. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
