On 4 May 2015 at 22:06, Jonas Sicking <[email protected]> wrote: > The main thing that I think we should do is abandon the term "app". > The term "app" is often associated with things like "installing" and > "app store", both of which I'd like to move away from. > ...
> But I think we generally should just consider web content as web > content. I.e. as normal websites that you can browse to. Having a W3C > or a FirefoxOS manifest shouldn't really make a big difference in what > that content can do, what permission it gets or what UI it has. > ... > The second complexity is "pinning". I think we should allow users to > pin websites to the homescreen. This should be possible for *any* > website, whether it has a W3C manifest, a FirefoxOS manifest, the > Apple-invented <meta> tags, or none of the above. > We're now working on implementing this as part of Pinning the Web [1]. We're removing the distinction between web apps and web sites, between app windows and browser windows, and making it so that any web site can be pinned. We don't call it an "app" or a "site", we just refer to it by its name (e.g. "Pin Facebook"). We intend to put this through user testing. When the user pins a website I think we should grant it some > additional permissions automatically. Mainly we should grant it the > ability to store more data, run in the background using the > BackgroundSync and Alarm APIs and maybe create notifications. It might > also give that content special UX treatments, such as the ability to > show up in webactivity picker, or to run without a URL bar. > > But all those capabilities should come with getting pinned. It should > not be related to if the website has any types of manifests or not. > ... > Additionally, ideally the capabilities, like storage, BackgroundSync > API, Alarm API and notification API, is something that we make > available to all websites. However if the user hasn't pinned the > website the user would get prompted. So really the pinning is mainly > about UX. I.e. the prompting UX disappear, and the website can choose > to hide URL bar or appear in the webactivity picker. > In our implementation we're largely replacing the app registry with a pinned sites store (which replaces the bookmarks store) in Gaia. To begin with this is a DataStore but eventually I would like it if this could become part of a Places web service, working offline via cross-origin Service Workers. One part I'm not sure about is if we're saying we want to grant permissions based on pinning, how will Gecko know when a site is pinned? Currently an app is registered in the app registry when it's installed via the Apps API using its app manifest so that Gecko knows about it. What should be the equivalent in this new content model? Ben 1. https://wiki.mozilla.org/FirefoxOS/Pinning_the_Web
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
