On 25/05/12 20:16, Anant Narayanan wrote: > These two are contradictory statements. The user has no way of knowing > where the app comes from by clicking an install button on a third party > page.
Surely that's a problem with our implementation and/or the spec? Are you saying that we are coding up a system where users can install apps without knowing where they come from? >> BTW, I would - and thousands of sites do. Why would you stop them? > > Perhaps the Firefox analogy isn't the right one because the user > actually gets a file which is the point at which the install actually > happens and is in Mozilla's control (downloading from the website was > not "installing firefox"). To correct my earlier question, would you be > comfortable with any random website be able to control the *installer*, > and in general, the install experience for Firefox? I'm not sure that analogy holds either. If I am a store which wants to list "my favourite free task-tracking apps", then when the user clicks "install" and the install process (which is run by the UA) starts, the progress of that process is out of my hands. A better analogy (if you ignore the "payment" component which is necessary in the real world of physical objects) is a number of mail-order catalogues offering the same object from the same manufacturer. They will have different "user experiences" in the catalogues - different photos, different write-ups, etc. - but whoever you order from, you always get the same thing. And I think that's fine. Gerv _______________________________________________ dev-webapps mailing list dev-webapps@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-webapps
