The proposal is that the act of "installing" the app fetches all indicated resources and persists them. Apps that today are packaged wouldn't need to touch the network at all except for optional, periodic update pings. You could also preload apps like the dialer and other core/certified apps - so they are functional from the first run with no need to ever see a network. Nonetheless they are tied to an origin and could be updated using similar mechanims to any page with a serviceworker.
I know this presents difficulties today. I would like to understand them better as I think this stuff is *really* important. If an app doesnt have a meaningful URL its not really a web app in any real sense IMO. /Sam On Fri, Jan 30, 2015 at 10:54 AM, Naoki Hirata <nhir...@mozilla.com> wrote: > I have to agree with Kevin. My biggest concerns are for performance, > offline cases, and issues with caching with full hosted apps. > > An example is emergency calling. If the dialer was fully hosted without a > wifi connection, how do you make a call? This scenario would require you > to have a SIM w/ a data plan in order to access the app that is needed just > to go through the ril when it should just be able to access the ril > directly without having to have a SIM. > > Even having partial packaged apps could help in this case. > > Regards, > Naoki > > On Jan 30, 2015, at 10:40 AM, Kevin Grandon <kgran...@mozilla.com> wrote: > > Do we really want to fully deprecate packaged apps? I think making hosted > apps and packaged apps equals is a big win, but I'm not sure if fully > deprecating packaged apps is a good idea. > > There are many developers who like the ability to not run and maintain a > server. It's simply less work and overhead for them to throw their code up > on a marketplace, and not have to worry about a monthly server cost, or a > server going down. > > Best, > Kevin > > On Fri, Jan 30, 2015 at 10:28 AM, Benjamin Francis <bfran...@mozilla.com> > wrote: > >> On 30 January 2015 at 18:17, Andrew Overholt <overh...@mozilla.com> >> wrote: >> >> > >> > Most of the frequently used permissions do not require the use of a >> >> packaged app, but the second most used permission is systemXHR which >> does. >> >> Apparently most developers are only using this because they created a >> >> packaged app purely for its offline properties, then found they needed >> >> systemXHR to talk to their own server. Which is silly. I hope Service >> >> Workers will help with this situation. >> >> >> > >> > Can you elaborate on this a bit? Why do developers need to use >> systemXHR >> > with their packaged app? How do you envision Service Workers helping in >> > this case? >> > >> >> As I understand it... >> >> Developers create a packaged app because it's currently the most effective >> way to make their app work offline. A packaged app has a synthetic origin >> which will always be cross-origin from the developer's own web server. >> They >> use SystemXHR to allow their packaged app to use remote resources from >> their web server, rather than set up CORS because that's more difficult. >> >> If they instead used Service Workers to make their app work offline, they >> wouldn't have a weird synthetic origin and therefore wouldn't need to use >> systemXHR because their app would be same-origin with their web server. >> _______________________________________________ >> dev-webapps mailing list >> dev-webapps@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-webapps >> > > _______________________________________________ > dev-gaia mailing list > dev-g...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-gaia > > > > _______________________________________________ > dev-gaia mailing list > dev-g...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-gaia > > _______________________________________________ dev-webapps mailing list dev-webapps@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-webapps
