On 06/01/2012 08:18 AM, Benjamin Smedberg wrote:
On 5/31/2012 8:41 PM, Asa Dotzler wrote:
On 5/31/2012 4:48 AM, Gervase Markham wrote:
What is wrong with the analogy between this facility (requiring
permission to link to an app) and requiring permission to link to a
website?
Installing an app is not the same thing as visiting a website.
I have not yet seen a coherent description of how they are or should be
different. Technically they are exactly the same thing; when the store
"installs" an app, it is merely installing a URL link to where the app
is located. This is fundamentally different from the current android/iOS
stores, where the store actually delivers the app permanently to the
device. If the user perceives that they are getting their app from a
store when they actually are not (they are merely getting a *link* to an
app from the store!), there are going to be all sorts of disconnects
between perception and reality which could lead to unhappy users.
So I believe that we should be working to make it clear that installing
and linking an app are fundamentally the same thing, not trying to hide it.
We're drifting away from the installs_allow_from issue, but I want to
answer on the poing Benjamin is making there.
We are adding support to trigger the download of resources referenced in
an appcache manifest at install time when the app author adds the url to
the appcache in the webapp manifest. This means that the app will have a
status ("installed", "downloading") and a download progress. In this
situation, we can show a UI that let the user know when the app is ready
to be used offline.
This is done for b2g in bug 702369
Fabrice
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
